• State Verified Answer
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 432 subscribers
  • Views 886 views
  • Users 0 members are here
Options
Related

Studio does not open strings in mxliff file which begin with <b>

Michael Bauer

Just moved from 2019 to 2022 and it's suddenly being difficult with mxliff files. 

Over the last few days I had a rash of mxliff files which if I open it with Phrase (formerly Memsource), show it as beginning with <b>  so for example 

<b>Blabla blabla</b>{7}

If I look at the xml, then the string looks like this:

<source>&lt;b&gt;Blabla blabla&lt;/b&gt;{7}</source>

But in Studio, these strings are just completely missing, there's no empty string or anything, that segment is just not there so it goes from (say) segment 10 to segment 12. Do I need to twiddle with some arcance settings or is this yet another bug?
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Paul

    I can't post it here, any way of sending it to you directly?
    emoji
  • 0 in reply to Michael Bauer

    Send it to pfilkin at SDL dotcom and make sure you clarify exactly where the problem is unless it’s a small file.

    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

     

    I don't know for sure, but it looks as though the XML encoding for the HTML-like tags in the source string (&lt;b&gt;***** **** ********:&lt;/b&gt;{7}) may cause issues with how the Translation Unit is interpreted by Trados Studio. 

    The easy workaround for now would be to either use the default XLIFF filetype which seems to handle this file really easily anyway, and extracts the content, or use the Multilingual XML filetype.  Both these filetypes will allow you to work with this file and extract the content you need.

    I'll create an anonymised file with something to mirror this problem and send it to you for approval (something you should do anyway)... if you're happy I'll share that with the support team so we can log a potential bug.

    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

    Thanks for looking at this.

    How do I make Studio treat mxliff as not-mxliff?
    emoji
  • +1 in reply to Michael Bauer

     

    Like this:

    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

    Many thanks, that seems to be doing the trick for now, fingers crossed no unexpected side effects. One thing - I don't know if that's of interest - I noticed is what when using mxliff in Studio 2022, all of a sudden after translation all units in Studio and on opening them in Phrase, all the translations would be there but the first one would be set to Unconfirmed and the rest to Confirmed. In 2019, using the same workflow, they would all be set to Unconfirmed. I don't need a fix for this, as it was easy enough to work around BUT I'm mentioning as it feels like 2022 is making a general hash of handling mxliff. 
    emoji