English > General Questions
Xliff Exports for Trados
Harald Leithner:
Yes I got your mail but didn't have the time to answer, but you didn't describe a real problem or?
The only thing I see is that the target-tag is not created by your software and so jdiction has nothing to import... is this common by such software?
jstead:
Yes, the problem was not having the <target> tag as its should be there from the initial export. The translation software doesn't add any structural content/tags to xliff/xml files, they are designed to only interact with the content needing translation.
By nature, a CAT(Computer-Assisted Translation) tool is creating an exact copy of the file that is fed into the system into another language. That means that these tools do not change the structure of the file, neither would they add tags that were not originally in the file. They purely extract the text that needs to be translated and through the process of translation, replace this text by the same text in another language.
Therefore, for the import to be working, we would need a target tag to be added to the export. That way we can tell the tool to ignore the source tag (we create a rule that tells the CAT tools that this text must not be translated) and only translate the target tag. We will end up with a file containing both the English and the translation, e.g:
Export file:
<source><![CDATA[This is some text to translate.]]></source> (will be hidden for translation in CAT tool)
<target><![CDATA[This is some text to translate.]]> </target> (will be translated by CAT tool)
Import file:
<source><![CDATA[This is some text to translate.]]></source>
<target><![CDATA[Ceci est le texte à traduire.]]></target>
We're happy to talk/provide any other information that may assist.
Harald Leithner:
could you please try the attached version?
jstead:
Hi Harald,
Sorry for the delayed response, we ran into a few problems in the process, but after a bit of testing, they all ended up being on our side and not jdiction.
The new Xliff structure is great, and imported into the CAT tool with no issues.
To have the CAT tool exports import back into Jdiction, we just had to convert the translated .xlf to UTF without BOM (as the CAT Tool exported it as ANSI) and find and replace state='needs-translation' to state='translated' which only takes a few seconds. So very quick process!
We are now looking to do a complete site export/translate/import as a final test and I just had an issue with exporting the following tables.
When exporting the below from jdiction, the xliffs are empty.
com_content -> articles
com_menus -> item
(empty as in just have the xliff tag)
<xliff version='1.2' xmlns='urn:oasis:names:tc:xliff:document:1.2'></xliff>
Is com_menus -> item the actual menus front end structure for each of my menus?
The other 2 tables I required are k2 -> item and modules -> module which both are exporting/re-importing with no issues.
Thank you very much again for the great support.
Harald Leithner:
funny 6 year no new version of xliff and now we have 2.0 ;-) http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html maybe I will support this in the future
Maybe your CAT tool doesn't support the features of xliff 1.2? Or I miss understood the specifications.
I added bom detection for xliff files, could you post the output xml of the CAT tool?
state='needs-translation' is interesting because the state after translation should be one of "final signed-off translated"...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version