Forum: CAT Tools Technical Help
Topic: XLIFF mixed language -- any tool/process to input into a translation workflow?
Poster: SoerenB
Sorry if this has been discussed in the past (would have thougth so, but find none).
The normal process for XLIFFs is to get:
either a delta-only file - with untranlated translation units with the new/changed source
or a full, untranslated file - with all units in the source language (and then use a memory to 'translate' the unchanged stuff).
But if you get from a customer a bunch of XLIFF files with a mix of translated units (translations in the target element of the translation unit), and untranslated units (in this case English - which is populated to the target element).
In the CAT tools I know of this could never work. Because the already translated values would be considered (unknown) source. Unless there is some attribute info for those units of unchanged content.
Is it just me not knowing of a trick in this or that CAT tool for allowing such mixed language XLIFFs and still getting to easily learn of exactly what units are new/changed and have source to translate?
So far I told the customer, that this is a no-go, and requested either delta-only or full source and memory. But am I ignorant of a way to handle mixed language XLIFFs?
Topic: XLIFF mixed language -- any tool/process to input into a translation workflow?
Poster: SoerenB
Sorry if this has been discussed in the past (would have thougth so, but find none).
The normal process for XLIFFs is to get:
either a delta-only file - with untranlated translation units with the new/changed source
or a full, untranslated file - with all units in the source language (and then use a memory to 'translate' the unchanged stuff).
But if you get from a customer a bunch of XLIFF files with a mix of translated units (translations in the target element of the translation unit), and untranslated units (in this case English - which is populated to the target element).
In the CAT tools I know of this could never work. Because the already translated values would be considered (unknown) source. Unless there is some attribute info for those units of unchanged content.
Is it just me not knowing of a trick in this or that CAT tool for allowing such mixed language XLIFFs and still getting to easily learn of exactly what units are new/changed and have source to translate?
So far I told the customer, that this is a no-go, and requested either delta-only or full source and memory. But am I ignorant of a way to handle mixed language XLIFFs?