• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 432 subscribers
  • Views 618 views
  • Users 0 members are here
Options
Related

Translatin XLIFF file in Trados Studio 2019

Senni Mattila

Hello,

I have a problem when exporting translated XLIFF files from Studio (2019). It seems that the tag segment's id-property gets removed, when exporting. Below is a portion of the source XLIFF (opened in a Code Editor), which has a segment id, and below that is the target XLIFF file with the translation inserted, but the id is missing. The customer can't import the translated file into their system, because of the missing id property.

Screenshot of code editor showing source XLIFF file with segment id present and target XLIFF file missing the segment id.

Is there some setting in Trados Studio, that I am missing, or is this perhaps a bug?

In addition to the above, the XLIFF file is missing all the needed tags and blank spaces in the translatable view in Trados Studio 2019 (please see segments 2 - 3 for reference in screenshot below).  Are these two separate issues or linked together?

Screenshot of Trados Studio interface displaying a segment of text without tags or blank spaces in the translatable view.

 Thank you in advance for your help.

Best regards

Senni Mattila

Generated Image Alt-Text
[edited by: RWS Community AI at 1:10 PM (GMT 0) on 14 Nov 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

     

    What version are you using?  Latest is Trados Studio 2019 SR2 - 15.2.8.3007.

    I ran a quick test with this file:

    <?xml version="1.0"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:2.0" version="2.0" srcLang="en" trgLang="fr">
 <file id="someFile">
  <notes>
   <note id="n1">note for file.</note>
  </notes>
  <unit id="01_heading">
    <segment id="83D7681862266F4AA14B025CE493DC5F">
      <source>CAT tools in Europe</source>
      <target>CAT tools in Europe</target>
    </segment>				  
  </unit>
  <unit id="01_description">
    <segment id="81H7287561298D4NM16K127CE493YX1M">
      <source>The company began developing translation software in the late 1980s, and released the first Windows versions of two of the suite's major components in the early 1990s – MultiTerm in 1992, and Translator's Workbench in 1994.</source>
      <target>The company began developing translation software in the late 1980s, and released the first Windows versions of two of the suite's major components in the early 1990s – MultiTerm in 1992, and Translator's Workbench in 1994.</target>
    </segment>				  
  </unit>
 </file>
</xliff>

    Saved the target after confirming the targets and get this:

    <?xml version="1.0" encoding="utf-8"?>
<xliff srcLang="en" trgLang="fr-FR" version="2.0" xmlns="urn:oasis:names:tc:xliff:document:2.0">
  <file id="someFile">
    <notes>
      <note id="n1">note for file.</note>
    </notes>
    <unit id="01_heading">
      <segment state="translated" id="83D7681862266F4AA14B025CE493DC5F">
        <source>CAT tools in Europe</source>
        <target>CAT tools in Europe</target>
      </segment>
    </unit>
    <unit id="01_description">
      <segment state="translated" id="81H7287561298D4NM16K127CE493YX1M">
        <source>The company began developing translation software in the late 1980s, and released the first Windows versions of two of the suite's major components in the early 1990s – MultiTerm in 1992, and Translator's Workbench in 1994.</source>
        <target>The company began developing translation software in the late 1980s, and released the first Windows versions of two of the suite's major components in the early 1990s – MultiTerm in 1992, and Translator's Workbench in 1994.</target>
      </segment>
    </unit>
  </file>
</xliff>

    I just used default settings.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
Reply
  • 0

     

    What version are you using?  Latest is Trados Studio 2019 SR2 - 15.2.8.3007.

    I ran a quick test with this file:

    <?xml version="1.0"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:2.0" version="2.0" srcLang="en" trgLang="fr">
 <file id="someFile">
  <notes>
   <note id="n1">note for file.</note>
  </notes>
  <unit id="01_heading">
    <segment id="83D7681862266F4AA14B025CE493DC5F">
      <source>CAT tools in Europe</source>
      <target>CAT tools in Europe</target>
    </segment>				  
  </unit>
  <unit id="01_description">
    <segment id="81H7287561298D4NM16K127CE493YX1M">
      <source>The company began developing translation software in the late 1980s, and released the first Windows versions of two of the suite's major components in the early 1990s – MultiTerm in 1992, and Translator's Workbench in 1994.</source>
      <target>The company began developing translation software in the late 1980s, and released the first Windows versions of two of the suite's major components in the early 1990s – MultiTerm in 1992, and Translator's Workbench in 1994.</target>
    </segment>				  
  </unit>
 </file>
</xliff>

    Saved the target after confirming the targets and get this:

    <?xml version="1.0" encoding="utf-8"?>
<xliff srcLang="en" trgLang="fr-FR" version="2.0" xmlns="urn:oasis:names:tc:xliff:document:2.0">
  <file id="someFile">
    <notes>
      <note id="n1">note for file.</note>
    </notes>
    <unit id="01_heading">
      <segment state="translated" id="83D7681862266F4AA14B025CE493DC5F">
        <source>CAT tools in Europe</source>
        <target>CAT tools in Europe</target>
      </segment>
    </unit>
    <unit id="01_description">
      <segment state="translated" id="81H7287561298D4NM16K127CE493YX1M">
        <source>The company began developing translation software in the late 1980s, and released the first Windows versions of two of the suite's major components in the early 1990s – MultiTerm in 1992, and Translator's Workbench in 1994.</source>
        <target>The company began developing translation software in the late 1980s, and released the first Windows versions of two of the suite's major components in the early 1990s – MultiTerm in 1992, and Translator's Workbench in 1994.</target>
      </segment>
    </unit>
  </file>
</xliff>

    I just used default settings.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
Children
No Data