translation xlf not importing

Press Ctrl / CMD + C to copy this to your clipboard.

Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

Topic author was deleted

Nov 26, 2020 @ 08:07

Hey,

I've used this tool on a number of projects... great job!

Now on a new site I've also created a translation job, got the xlif file and that has been translated by a third party...

But when I now import the file on the job it doesn't error but just doesn't show the translations

structure looks like this:

<?xml version="1.0" encoding="utf-8"?>
<xliff srcLang="en-GB" trgLang="de-DE" version="2.0" xmlns="urn:oasis:names:tc:xliff:document:2.0">
<file id="f1" original="438|Dictionary Item: Close">
<group id="g1" name="close">
  <group id="g2" name="1304|Close">
    <unit id="u1" name="ed4e4389-b140-4c8f-a26f-0046b853872b">
      <segment state="translated">
        <source>Close</source>
        <target>Schliessen</target>
      </segment>
    </unit>
  </group>
</group>

So seems ok ... but not working

Copy Link

Kevin Jump 2343 posts 14890 karma points MVP 8x c-trib

Nov 26, 2020 @ 08:15
0
yeah that looks ok 😕
- does it import into the translation dashboard OK ? (so can you see the translations in the properties of the job?)
- or is it when you come to approve that the translations are not coming across
Couple of quick things to check : - if you have the file you sent to them, just confirm the id & name values haven't changed. - check the dictionary items haven't been updated or maybe removed/recreated (that would change their guid value*) .

*We use guid here, but i am not super happy about it - we might switch to key name.
Copy Link

Comment author was deleted

Nov 26, 2020 @ 08:41

we have an other job with the content nodes... that also doesn't work

file looks like

<?xml version="1.0" encoding="utf-8"?>
<xliff xmlns:mda="urn:oasis:names:tc:xliff:metadata:2.0" srcLang="en-GB" trgLang="de-DE" version="2.0" xmlns="urn:oasis:names:tc:xliff:document:2.0">
<file id="f1" original="231|Home Page - EN">
<group id="g1" name="nodeprops">
  <group id="g2" name="664|nodeName">
    <unit id="u1" name="664|Umbraco.Textbox">
      <segment state="translated">
        <source>Home Page - EN</source>
        <target>Homepage - DE</target>
      </segment>
    </unit>
  </group>
</group>

Copy Link

Comment author was deleted

Nov 26, 2020 @ 08:39

Yeah checked that... when we review/preview it shows up as (blank)

Copy Link

Comment author was deleted

Nov 26, 2020 @ 09:35

This is the downloaded orig file

<?xml version="1.0" encoding="utf-8"?>
<xliff srcLang="en-GB" trgLang="de-DE" version="2.0" xmlns="urn:oasis:names:tc:xliff:document:2.0">
 <file id="f1" original="211|Dictionary Item: Close">
<group id="g1" name="close">
  <group id="g2" name="682|Close">
    <unit id="u1" name="ed4e4389-b140-4c8f-a26f-0046b853872b">
      <segment>
        <source>Close</source>
      </segment>
    </unit>
  </group>
</group>
</file>

Copy Link

Comment author was deleted

Nov 26, 2020 @ 09:37

this is how the review looks

Copy Link
Kevin Jump 2343 posts 14890 karma points MVP 8x c-trib

Nov 26, 2020 @ 10:02

0

Yeah the names are different?

e.g. 438|Dictionary Item: Close vs 211|Dictionary Item: Close

The first bit of this is what is used to match to the translation values.

I suspect the retuned file is for a previous job?

The jobs are transactions, so they have to match (you can't put a returned file on a later job because things might have changed/moved around since translation)

Copy Link
Comment author was deleted

Nov 26, 2020 @ 10:08

ok makes sense, thanks for the info...

Copy Link
is working on a reply...

Please Sign in or register to post replies