• State Verified Answer
  • Replies 4 replies
  • Subscribers 432 subscribers
  • Views 1708 views
  • Users 0 members are here
Options
Related

Studio changes segmentation in xlf target files

Burim Bektesi

Hi, I have an xlf-file which Studio processes with its xliff 2.0 definition file.

Everythings looks fine and is well segmented in Studio (except some bad segmentation in the original file), I have 2 problems with the generated target file though.

1) Some <segment> tags have IDs, but after generating the target file, the ID is gone and the tag changes to <segment state="translated">.
I didn'f find any settings to adjust in the file type definition.

Screenshot of Trados Studio showing original XLIFF file with segment tags and IDs before translation.

2) when I translate this, being one source entry:

<source>Palette in Position 0°. Tisch mittig unter die Arbeitsspindel stellen. Fühlhebelmessgerät mit Halter in </source>

I expected to get this:
<source>Pallet in position 0°. Place the table centrally under the work spindle. Fasten the lever gauge in </source>

But I get this instead:
Screenshot of Trados Studio showing translated XLIFF file with segment state changed to 'translated' and missing segment IDs.

The segmentation in Studio is passed on to the target file, creating new source and target lines. There is also an new tag <ignroables>.

Any idea?

Thnx, Burim.

Generated Image Alt-Text
[edited by: Trados AI at 6:18 AM (GMT 0) on 29 Feb 2024]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0 

    <?xml version="1.0" encoding="utf-8"?>
<xliff version="2.0" srcLang="de" trgLang="en" xmlns="urn:oasis:names:tc:xliff:document:2.0">
<file original="DMI ControlFile Translation" id="cfe24cd4-65b4-460f-9848-3ec89fefb89d">
<unit id="cfe24cd4-65b4-460f-9848-3ec89fefb89d">
<segment id="controlfile_title">
<source>Final Accuracy Test</source>
<target />
</segment>
</unit>
<unit id="9d5524b7-76ae-4ccf-a6a6-26a91d11d37a">
<segment id="controlfile_pos_title">
<source>Prüfen der Parallelität zwischen der Achse aus der zentralen Bohrung und der Tisch/Paletten Richtbohrung zur Bewegung entlang der Y-Achse.</source>
<target />
</segment>
</unit>
<group id="fcdf2b06-a2de-44c5-8b62-a4669c3068e3">
<notes>
<note>FAT_S3_G17_DM-PF_Portal</note>
</notes>
<unit id="415a7cf8-a4d1-4a23-ab93-2ad89ea46b36">
<segment>
<source>Messverfahren/Abbildung</source>
<target />
</segment>
</unit>
<unit id="de9926fe-1bc0-41f1-9f10-714d49e48744">
<segment>
<source>Palette in Position 0°. Tisch mittig unter die Arbeitsspindel stellen. Fühlhebelmessgerät mit Halter in </source>
<target />
</segment>
</unit>
<unit id="fbdc14a8-e882-46a4-9c6e-b77cd7e5a367">
<segment>
<source>der Arbeitsspindel befestigen. </source>
<target />
</segment>
</unit>
<unit id="58bcb5de-88ef-4caa-9f2b-97f62e163d7f">
<segment>
<source>Fühlhebelmessgerät in der zentralen Bohrung des Palette anstellen </source>
<target />
</segment>
</unit>
<unit id="68c7643b-4a59-4bda-ad1f-122e08b33a94">
<segment>
<source>und nullen. Durch Drehen der Arbeitsspindel Versatz prüfen, und diese durch Verfahren der </source>
<target />
</segment>
</unit>
<unit id="7862540f-466b-4256-aa30-d6325fdc9122">
<segment>
<source>Maschinenachsen zentrisch zur Arbeitsspindel positionieren. Achspositionswerte notieren. Mit der </source>
<target />
</segment>
</unit>
<unit id="0dfe0f47-26b0-42c3-a1f2-c1fd2de99eef">
<segment>
<source>Z- Achse nach oben fahren, bis die Messuhr frei wird. Mit der Arbeitsspindel zur Richtbohrung fahren, </source>
<target />
</segment>
</unit>
<unit id="69a49db6-4c0d-49c2-ae4a-1ba2d91ab6e5">
<segment>
<source>Vorgang wiederholen und Achspositionswerte der Richtbohrung notieren. Unterschied beider </source>
<target />
</segment>
</unit>
<unit id="c8f5d4fe-6350-4cf7-b5da-fb9b2d2bd964">
<segment>
<source>X-Positionswerte ermitteln und im Verhältnis auf die Messlänge umrechnen.</source>
<target />
</segment>
</unit>
</group>
</file>
</xliff>
    emoji
  • +1

    I think the problem is due to the default behaviour relating to the resegment attribute in XLIFF2.0.  This post explains:

    https://community.rws.com/product-groups/trados-portfolio/trados-studio/f/studio/39967/problem-with-xliff-2-0-filetype/130222#130222

    If this is a problem for your customer, and if they cannot recreate the XLIFF using the resegment attribute set to "no", then the multilingual XML filetype may be the way to go... also mentioned in the same post.

    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
  • 0 in reply to Paul

    Hi Paul, thnx a lot.

    We still haven't found out what causes problems at the customer, so I don't know if it's the resegmenting or the status change. I will try with the multilingual xml filetype, thank you.

    Burim
    emoji
  • 0 in reply to Paul

    Hi Paul,

    the file looks fine with Multilingual xml. Thnx a lot. Let's see if the import works at the customer.

    I got stuck first at the language root elements, as the document has several paths, like:

    /xliff/file/group/unit/segment
    /xliff/file/unit/segment

    But it works with //segment

    Trados Studio Language Mapping settings showing Languages Root: xlifffilegroupunitsegment with German and English language options.

    Thnx again
    Burim
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 6:18 AM (GMT 0) on 29 Feb 2024]