Sign in Register
Go to solution
Copied to clipboard

Flag this post as spam?

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


  • Filipe Sousa 43 posts 205 karma points
    Jun 17, 2021 @ 09:33
    Filipe Sousa
    0

    Can we create a translation job for items that haven't been translated yet?

    Translation Manager Feedback
    Umbraco 8

    As the title says.

    We have a EN website node and an AR website node in our Umbraco 8 installation. The AR website has been partially translated from EN. Is it possible to send out for translation, only the items that are blank?

    Many thanks

    Copy Link
  • Kevin Jump 2310 posts 14695 karma points MVP 7x c-trib
    Jun 17, 2021 @ 11:11
    Kevin Jump
    100

    Hi Filipe,

    Yes in the latest version - you there is a "Include Target Values" option when you pick the "xliff 2.1 (Experimental)" format in the Xliff File provider options.

    enter image description here

    this will include the existing values in the "target" nodes of any translation.

    Copy Link
  • Filipe Sousa 43 posts 205 karma points
    Jun 30, 2021 @ 08:38
    Filipe Sousa
    0

    Hi Kevin, thanks so much for your reply.

    The translation company is still having an issue with the file we're sending them:

    We are not able to extract the EN content only since we don’t have a pattern in the file to exclude EN from Arabic, the TUs have different ID numbers.

    The source file is a xlf version 2.0, for this we extract the target elements from the source and create the xlf format that can be sent to our system. In this case extracting the target will create a file with the pre-populated content and the content that needs to be translated. Sadly there is no way to separate the ones pre-populated with the new content.

    I think we have two options;

    1. Can an attribute be added to the TU's that have been translated? pre-translated="yes" for example and then a new export sent over?

    or

    1. A new and amended export that contains only the new text that needs to be translated.

    Could you advise? Many thanks in advance.

    Copy Link
  • Kevin Jump 2310 posts 14695 karma points MVP 7x c-trib
    Jun 30, 2021 @ 09:15
    Kevin Jump
    0

    Hi Filipe,

    I "think" I understand what they are saying,

    For xliff 2. I think the option would be to add the state attribute to each segment of the file to say it's translated e.g 

    <segment state="translated">
  <source>Content Title</source>
  <target>Titre du contenu</target>
</segment>

    or the parent unit can be marked not for translation e.g 

    <unit id="u2" name="5357|Umbraco.TextBox" translate="no">
  <segment>
    <source>Content Title</source>
    <target>Titre du contenu</target>
  </segment>
</unit>

    I would think the segment version makes more sense ? but i would check with the translation company ?

    I would then say the quickest thing is probably for you to make this change on the produced file and let the translation company have that.

    We could add stuff like this to the core of the product but then you will be waiting on us and we would need to build the options test it and put it in the the release cycle of translation manager before you can send the file

    *the state and translate attributes are part of the xliff 2 spec, and we validate against that so we would have to use a valid attribute at this point.

    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft