• State Suggested Answer
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 138 subscribers
  • Views 9118 views
  • Users 0 members are here
Options
Related

Content Importer Throwing Unicode Error When Importing Translated XML.

Aheeka

While trying to bulk upload translated content (xml:lang = "FR"; EN being the default), Content Importer is throwing the following error: An unexpected failure occurred. There is no Unicode byte order mark. Cannot switch to Unicode.

We tried to then upload just one XML to the FR language version of the object and received the same message. Nothing in the tags have been changed from when we initiated the translation process from the system itself in Content Manager - Selecting the Released Publication at the language level, selecting the "Translation" button, and "Generating the Target Language" of FR for all the non-publication objects.

Screenshots from when we tried an individual upload as well via Content Manager; the same error message was displayed:

Trados Studio Content Importer error message window over Content Manager, displaying 'An unexpected failure occurred. There is no Unicode byte order mark. Cannot switch to Unicode.'

Trados Studio error dialog box on top of Content Manager interface showing the same Unicode byte order mark error during individual XML upload attempt.

Generated Image Alt-Text
[edited by: Trados AI at 6:29 AM (GMT 0) on 5 Mar 2024]
emoji
Rate translation
×
Suggest better translation
×
Parents Reply
  • 0 in reply to David Autry

    Hi David,

    Thank you for your response!

     

    I looked at the XML initially sent to the translators for translation, and it does have the encoding called out: <?xml version="1.0" encoding="UTF-16"?>

    When they sent back the translated file, it was still there, so I wasn't sure why I was getting an encoding issue when the tag wasn't touched. I removed the encoding="UTF-16" text and tried uploading just that individual file to the repository, and I had no issues, but I can't figure out why when outputting the zip file of all the XMLs to be translated, encoding is included, but not accepted when importing the XMLs back in - the GUIDs were not changed.
Children