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

System fields from TM - Amp character corrupts .sdlxliff

Torben Dahl Jensen

Hi

We are beginning to see some strange issues with .sdlxliff files getting corrupted after a Pre-translate batch task...

The reason is the use of the '&' in system fields of the TM.

Error message when opening the .sdlxliff after having completed the pretranslation task successfully:

XML error is here:

Everything is 'back to normal' if I change all occurences of '&' to 'AND'... :-)

These are old segments so I am wondering whether is all of a sudden is an issue in SP2? Don't remember seeing this error in SP1 and earlier versions...

Best regards,

Torben
amp_error.zip
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Yes, unfortunately this seems to be a bug. Thank you for posting, I have had the same problem some days ago, but no time to post. So I can confirm & and maybe some other signs (I think diacritics they were and maybe also =) do cause problems. And this is new since SP2.

    Best regards, Jerzy

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • 0 in reply to Jerzy Czopik

    What should we do? Ideas are welcome... :-) Our Project Managers simply don't have time to check if every .sdlxliff file in a big project will open correctly... In stead, we have to wait for vendors to get back to us when they open the packages and start working... Then I have to fix the xml issue in the .sdlxliff and create a new package for the vendor facing the problem...
  • 0 in reply to Torben Dahl Jensen

    Hi Torben,

    Perhaps you can check the SDLTMs beforehand and then export the TM as a TMX.  Then search replace the ampersands and  recreate the TM.  I know this is a pain, but at least it's something you could do to ensure things work when you do send the packages out.  So don't create packages with TMs that contain this problem.

    It has been handed to development who will work on a fix.

    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 in reply to Torben Dahl Jensen

    Hi Torben,

    Perhaps you can check the SDLTMs beforehand and then export the TM as a TMX.  Then search replace the ampersands and  recreate the TM.  I know this is a pain, but at least it's something you could do to ensure things work when you do send the packages out.  So don't create packages with TMs that contain this problem.

    It has been handed to development who will work on a fix.

    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
No Data