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

Markups-Tags in XLIFF files seen as text not as tags

Aubeline Brandamir

Creating a new thread

Hello Paul,

I have a similar issue and despite reading your advice carefully here (and here), I'm still unable to sort out my issue.

This is what I see in Phrase

Screenshot of a translation software interface showing a table with two columns. The left column, labeled 'Filter source text (en-gb),' displays text segments with the phrase '1 on-page 2'. The right column, labeled 'Filter target text (fr),' shows corresponding translated segments with formatting tags and the phrase '1 a la page 2'.

and this is what I get in Studio 

Screenshot of Trados Studio interface with source and target text columns, displaying text with tags and percentages indicating match quality, all at 100%.

I've used this rule you suggested, as it seemed to also make sense in my case. But maybe it does not! I must say I'm really not an export in Regex...

Screenshot of Trados Studio options dialog with embedded content rules, highlighting a rule with an opening tag '(1)' and a checkbox for case sensitivity.

Any clue how I can sort this out?

From Paul

  1. You showed Phrase... so I guess it's an *.mxliff file?
  2. If it's not then which XLIFF filetype are you using to handle the file?  You made the changes in the XLIFF presumably because that's what you saw in the other threads.  But perhaps this isn't correct for your file?
  3. What version of Trados Studio?

Hi  

1. Yes, it is a mxliff file

2. I made the changes in the Xliff filetype because the MS mxliff filetype plugin doesn't seem to be able to manage this issue and there are no editable setting in this one

3. I use Trados Studio 2024 
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

      

    Aubeline Brandamir said:
    1. Yes, it is a mxliff file

    So this means it will be opened using the memsource filetype by default unless you do something to prevent this.  I am surprised to see these placeholders being ignored in 2024 though... perhaps this is a bug... perhaps there is something odd about your file... perhaps you are actually not using the mxliff filetype to handle this.  Can you provide a screenshot of your filetype settings page so we can see which XLIFF filetype are activated and in what order?  If the memsource filetype is first and if it's activated have you added a mask for *.mxliff in the "File dialog wildcard expression" field to ensure the XLIFF filetype will even open it?

    Any chance we can see the file?  You can send it to pfilkin at sdl dotcom is this is acceptable?

    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

      

    Aubeline Brandamir said:
    1. Yes, it is a mxliff file

    So this means it will be opened using the memsource filetype by default unless you do something to prevent this.  I am surprised to see these placeholders being ignored in 2024 though... perhaps this is a bug... perhaps there is something odd about your file... perhaps you are actually not using the mxliff filetype to handle this.  Can you provide a screenshot of your filetype settings page so we can see which XLIFF filetype are activated and in what order?  If the memsource filetype is first and if it's activated have you added a mask for *.mxliff in the "File dialog wildcard expression" field to ensure the XLIFF filetype will even open it?

    Any chance we can see the file?  You can send it to pfilkin at sdl dotcom is this is acceptable?

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

    Thanks Paul!

    I've sent all via a pm

    I've tried a few things so maybe the "settings" pile up now
    emoji
  • 0 in reply to Aubeline Brandamir

     

    I am a bit confused about why you have this problem to be honest.

    Trados Studio Options dialog showing file types with 'XLIFF SDL' and 'Memsource MXLIFF' highlighted, indicating potential file type conflicts.

    I did wonder at first why you had two, but then I remembered Jesse Good developed one and the Trados AppStore Team took it over - https://appstore.rws.com/Plugin/29 - when he stopped supporting it.  I believe the first one in your list is the AppStore version, so this should be ok.  I tested it and it seems fine:

    Error message dialog with multiple entries, each containing a placeholder symbol and the text 'on page' followed by a number, indicating missing references or links.

    Then, I unchecked both of them and added the embedded content regex to the default XLIFF, added *.mxliff to the "File dialog wildcard expression" field and this also works fine... screenshot would be exactly the same, so I didn't bother ;-)

    So, you shouldn't have a problem.  But then I opened the SDLXLIFF you also sent me and this has been created using the default memsource filetype and not the AppStore version.  Based on the screenshot of your settings this would be impossible, so I can conclude you did not create your project with the settings you showed me.  Therefore you need to check what project template you used to create your projects with because it clearly isn't your File -> Options.

    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


    Generated Image Alt-Text
    [edited by: RWS Community AI at 9:09 PM (GMT 1) on 30 Sep 2024]
  • 0 in reply to Paul

    Thank you so much for your thorough explanation Paul!

    I've gone over your message a few times and did a few tests, and I finally managed to get those tags to appear as tags! And now I understand the problem. Yeaahh!!

    You're a lifesaver, as always!

     

    The issue may come from the fact I jump from 2022 to 2024 because of the fact Aspic Xbench and Antidote appear to still not work in Studio 2024, so I go to the older version for those. I admit I did not yet find the time to look into this really. So I may have used 2022 and forgot about it, honestly!

     

    Could this also explain why the segment status (draft, confirmed...) also do not appear properly in Phrase after the import?
    emoji