Forum: Wordfast support
Topic: Is it possible to make a sdxliff from a MS word file by translating with WFP?
Poster: Samuel Murray
Post title: MateCat does produce SLXLIFF
[quote]FarkasAndras wrote:
I haven't delved into this at depth [i]and I don't plan to[/i], but I'm [u]pretty sure[/u] that MateCat generates XLIFF, not SDLXLIFF. [/quote]
Well, it requires only a little delving to get the answer: yes, MateCat does export SDLXLIFF files that Trados (2015) accepts as its own format and that Trados is happy to export again as a final file.
Simply load the file into MateCat and "start" the translation. Then, on the translator screen, select "Preview" and then "SDLXLIFF".
MateCat appears to segment the SDLXLIF the same way as Trados, too.
The only issue is that MateCat performs pre-translation against its own TM (even if you deselect machine translation), so the SDLXLIFF file is "pre-translated"... not with souce=target but with source=fuzzy-match. Hence [url= [url removed] ]my question this morning[/url] in the Trados forum about how to clear all target fields in Trados. This is not a problem in CAT tools that can read SDLXLIFF's segment statuses (such pre-translated segments are marked as unconfirmed), but it may be an issue for CAT tools that can't (e.g. OmegaT, with or without the Okapi filter).
There doesn't seem to be an option in MateCat to ensure that the exported SDLXLIFF file is pre-translated as source=target. Unknown segments are pre-translated source=target (and here is where MateCat blunders a bit -- if the source field contains a line feed, the target field doesn't (which is not a problem unless you're using a CAT tool that relies on the target field)).
[Edited at 2015-09-13 16:16 GMT]
Topic: Is it possible to make a sdxliff from a MS word file by translating with WFP?
Poster: Samuel Murray
Post title: MateCat does produce SLXLIFF
[quote]FarkasAndras wrote:
I haven't delved into this at depth [i]and I don't plan to[/i], but I'm [u]pretty sure[/u] that MateCat generates XLIFF, not SDLXLIFF. [/quote]
Well, it requires only a little delving to get the answer: yes, MateCat does export SDLXLIFF files that Trados (2015) accepts as its own format and that Trados is happy to export again as a final file.
Simply load the file into MateCat and "start" the translation. Then, on the translator screen, select "Preview" and then "SDLXLIFF".
MateCat appears to segment the SDLXLIF the same way as Trados, too.
The only issue is that MateCat performs pre-translation against its own TM (even if you deselect machine translation), so the SDLXLIFF file is "pre-translated"... not with souce=target but with source=fuzzy-match. Hence [url= [url removed] ]my question this morning[/url] in the Trados forum about how to clear all target fields in Trados. This is not a problem in CAT tools that can read SDLXLIFF's segment statuses (such pre-translated segments are marked as unconfirmed), but it may be an issue for CAT tools that can't (e.g. OmegaT, with or without the Okapi filter).
There doesn't seem to be an option in MateCat to ensure that the exported SDLXLIFF file is pre-translated as source=target. Unknown segments are pre-translated source=target (and here is where MateCat blunders a bit -- if the source field contains a line feed, the target field doesn't (which is not a problem unless you're using a CAT tool that relies on the target field)).
[Edited at 2015-09-13 16:16 GMT]