Hi Dan,

You can change these values, it doesn't affect the re-importing of the job back into Translation Manager.

We don't currently have an option to specify which of the language identifiers are used in the file, (there is, for example, en, eng, en-US/en-gb) - but its something we could look at adding to the options for the Xliff provider.

Re-importing the extracted file won't work because it only contains the source values - when a translation company/translator processes the translations via their software it will generate the translated values.

so in the original file, you might see something like :

    <unit id="u1" name="677|Umbraco.Textbox">
      <segment>
        <source>Some sample content</source>
      </segment>
    </unit>

once it's been translated it becomes

    <unit id="u1" name="677|Umbraco.Textbox">
      <segment>
        <source>Child of Child Content</source>
        <target>Quelques exemples de contenu</target>
      </segment>
    </unit>

the error you are getting is because the target is missing, this is more explicit in later versions of Translation Manager so it might be worth updating?

Downloaded the latest version for Umbraco 8 - we are using variants.

Looking at my file though there is no

Hi Dan,

turns out the 3 letter lang thing was an oversight when we migrated to a v8 code base :(

A quick fix, however - so when NuGet has published it.

Install-Package Jumoo.TranslationManager.Connector.Xliff -Version 8.0.2

https://www.nuget.org/packages/Jumoo.TranslationManager.Connector.Xliff/8.0.2

Will stamp srcLang and trgLang with the same code as the languages you have picked in Umbraco

so for example french becomes fr while french (france) will be fr-fr

in terms of the missing target - are your translation company returning you a file where the has been translated in place (so the <source> is now in french?).

if so they appear to be treating the xliff file like an xml file and not a xliff one. ask if they can translate into the <target> value ?

we do have the ability to take the translated values from the source, but we don't offer it on the vanilla xliff provider at the moment - (we use it in direct connectors sometimes).

Thanks for this - I will pass onto translation company and see what they say. I'm new to XLIFF so appreciate your help as once it leaves Umbraco i'm not entirely sure what happens to it!

Translation company asking if it is definitely a bilingual file? i.e. i think they are confused as there is no

 <group id="g5" name="2|ogDescription">
    <unit id="u3" name="2|Umbraco.TextArea">
      <segment>
        <source>See how the TASER X2 helps police officers safely defuse situations with its audible warning arc, dual lasers and signal technology that activates nearby cameras when an incident occurs</source>
      </segment>
    </unit>
  </group>
</group>

is working on a reply...