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

Struggling with Xliff source structure in SDL Studio 2017

Jean-Christophe Bailbe

This has been logged as a case (Case No. 00620076) but I think might have an idea, sorry for the potential duplication, but we're struggling. Thanks in advance. Kind regards. JCB

We are trying to process a file with Studio in which some segments have segmentation information (<mrk> tags) and some others don't, and we want the target file to have the exactly the same structure. However, the option "Do not store segmentation information in the translated file" does not seem to work for that purpose. We end up having a target file either with no <mrk> tags at all for all segments (by ticking that option), either with <mrk> tags for all segments, including those segments not having segmentation information in the source (by leaving that option unticked). Is there any option in Studio to maintain the segmentation information in the target file simply as it is in the source?
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    It looks as though the support team responded already and confirmed we don't have an option to do this.  You either don't include this segmentation information or you do.  Give your XLIFF source already contained some I'm wondering why it's a problem for you if the target files do all contain this segmentation information?

    I can suggest a workaround though after seeing your screenshots in the support case just now.  The file seems to come with the source language populated in the target element.  So it doesn't come partially translated.  This means you could handle this with a simple custom XML filetype and then all the content you want to remain as is will be maintained as is.  Perhaps that will work for you?

    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

Reply
  • 0

    It looks as though the support team responded already and confirmed we don't have an option to do this.  You either don't include this segmentation information or you do.  Give your XLIFF source already contained some I'm wondering why it's a problem for you if the target files do all contain this segmentation information?

    I can suggest a workaround though after seeing your screenshots in the support case just now.  The file seems to come with the source language populated in the target element.  So it doesn't come partially translated.  This means you could handle this with a simple custom XML filetype and then all the content you want to remain as is will be maintained as is.  Perhaps that will work for you?

    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

Children