• State Suggested Answer
  • Replies 2 replies
  • Answers 2 answers
  • Subscribers 433 subscribers
  • Views 1290 views
  • Users 0 members are here
Options
Related

"Ignorable" element in xliff target file

Thibaut Vanspranghe

Hello, I've experienced a particular problem when translating an XLIFF file within Studio. A source came in with two sentences in one specific segment. Translation showed two different sentences in two different segments. After generating the target file and delivering it to the customer, the sentences are not re-joint/merged together in one segment(//source) as I would have expected, but remain split, with an <ignorable> element in between. Any idea how to avoid this? Is it a setting? I've never heard of this 'ignorable' element before, what is it exactly? Thanks.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    I created a file like this:

    <?xml version="1.0" encoding="utf-8"?>
<xliff version="1.2" >
  <file original='somefile.txt' source-language="en-GB" target-language="de-DE" datatype='plaintext' >
    <header>
      <note>simple xliff</note>
    </header>
    <body>
     <trans-unit id="1">
      <source>First sentence. Second sentence</source>
      <target></target>
     </trans-unit>
     <trans-unit id="2">
      <source>Third sentence</source>
      <target></target>
     </trans-unit>
    </body>
  </file>
</xliff>

    Opened in Studio and copied source to target like this:

    Screenshot of Trados Studio showing two translation units with source text copied to target text, no visible errors or warnings.

    Then saved the target file and get this:

    <?xml version="1.0" encoding="utf-8"?>
<xliff version="1.2">
  <file original="somefile.txt" source-language="en-GB" target-language="de-DE" datatype="plaintext">
    <header>
      <note>simple xliff</note>
    </header>
    <body>
     <trans-unit id="1">
      <source>First sentence. Second sentence</source>
      <target state="new">First sentence. Second sentence</target>
     </trans-unit>
     <trans-unit id="2">
      <source>Third sentence</source>
      <target state="new">Third sentence</target>
     </trans-unit>
    </body>
  </file>
</xliff>

    Which all looks correct to me.

    So, if you can provide a small sample XLIFF that behaves the way you have  described then we can try and investigate it.

    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



    Generated Image Alt-Text
    [edited by: Trados AI at 4:37 AM (GMT 0) on 29 Feb 2024]
Reply
  • 0

    I created a file like this:

    <?xml version="1.0" encoding="utf-8"?>
<xliff version="1.2" >
  <file original='somefile.txt' source-language="en-GB" target-language="de-DE" datatype='plaintext' >
    <header>
      <note>simple xliff</note>
    </header>
    <body>
     <trans-unit id="1">
      <source>First sentence. Second sentence</source>
      <target></target>
     </trans-unit>
     <trans-unit id="2">
      <source>Third sentence</source>
      <target></target>
     </trans-unit>
    </body>
  </file>
</xliff>

    Opened in Studio and copied source to target like this:

    Screenshot of Trados Studio showing two translation units with source text copied to target text, no visible errors or warnings.

    Then saved the target file and get this:

    <?xml version="1.0" encoding="utf-8"?>
<xliff version="1.2">
  <file original="somefile.txt" source-language="en-GB" target-language="de-DE" datatype="plaintext">
    <header>
      <note>simple xliff</note>
    </header>
    <body>
     <trans-unit id="1">
      <source>First sentence. Second sentence</source>
      <target state="new">First sentence. Second sentence</target>
     </trans-unit>
     <trans-unit id="2">
      <source>Third sentence</source>
      <target state="new">Third sentence</target>
     </trans-unit>
    </body>
  </file>
</xliff>

    Which all looks correct to me.

    So, if you can provide a small sample XLIFF that behaves the way you have  described then we can try and investigate it.

    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



    Generated Image Alt-Text
    [edited by: Trados AI at 4:37 AM (GMT 0) on 29 Feb 2024]
Children
No Data