- changed status to open
Wrong target language in TMX output
Original issue 284 created by @ysavourel on 2012-10-17T22:17:17.000Z:
Possible bug in the File Format converter:
----------- original info:
I tried to use the Files format conversion utility in Rainbow to convert an xlf file into a tmx file.
Rainbow detects correctly the source and the target languages and generates the tmx file. The issue is that all the segments are identified as source language.
For example: this segment in my xlf
<trans-unit id="1">
<source xml:lang="EN-US"><![CDATA[Ask]]></source>
<target xml:lang="FR-FR" state="translated"><![CDATA[Demander]]></target>
</trans-unit>
will give that in the generated tmx
<tu tuid="autoID1">
<tuv xml:lang="en-us"><seg>Ask</seg></tuv>
</tu>
<tu tuid="autoID2">
<tuv xml:lang="en-us"><seg>Demander</seg></tuv>
</tu>
- could you look at it when you get time Fredrik?
thanks,
-yves
Comments (4)
-
Account Deleted -
Account Deleted Comment 2. originally posted by @ysavourel on 2012-10-17T23:18:30.000Z:
Then it may be a "user error" after all.
The original report is here:
http://tech.groups.yahoo.com/group/okapitools/message/3341
Maybe Eulalie can provide more info. -
Account Deleted Comment 3. originally posted by @fliden on 2012-10-18T00:06:37.000Z:
The output seems to match what you get if you use the plain xml filter. I sent an email to Eulalie to verify and make sure she's using the xliff filter.
-
Account Deleted - changed status to invalid
Comment 4. originally posted by @fliden on 2012-10-18T16:42:08.000Z:
- Log in to comment
Comment 1. originally posted by @fliden on 2012-10-17T23:10:30.000Z:
Hi Yves, I'm not able to replicate the error so far.
Xliff file I'm using:
<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:okp="okapi-framework:xliff-extensions">
<file original="[Content_Types].xml" source-language="en-us" target-language="fr-fr" datatype="x-undefined">
<body>
<trans-unit id="1">
<source xml:lang="EN-US"><![CDATA[Ask]]></source>
<target xml:lang="FR-FR" state="translated"><![CDATA[Demander]]></target>
</trans-unit>
</body>
</file>
</xliff>
That's using the latest snapshot + default xliff filter.
I'm getting the correct:
<?xml version="1.0" encoding="UTF-8"?>
<tmx version="1.4"><header creationtool="unknown" creationtoolversion="unknown" segtype="paragraph" o-tmf="unknown" adminlang="en" srclang="en-us" datatype="text"></header><body>
<tu tuid="autoID1">
<tuv xml:lang="en-us"><seg>Ask</seg></tuv>
<tuv xml:lang="fr-fr"><seg>Demander</seg>
<prop type="state">translated</prop>
</tuv>
</tu>
</body>
</tmx>
Do you have any more info about the pipleline\steps configuration? Are you using the regular xliff filter or another one?