• Replies 4 replies
  • Subscribers 48 subscribers
  • Views 2533 views
  • Users 0 members are here
Options

Error when importing a client's TMX (worldserver) into our GS 2017 TM: Invalid Unicode code point found at index 0. Parameter name: strInput

Vincent Roy

Hello, one of our client has sent us their whole TM but we are unable to import it in GS 2017. We get the following error:

Trados Studio error message during TM import stating 'Invalid Unicode code point found at index 0. Parameter name: stringInput'.

We tried to create a local TM and import it but we get the same error. The TM seems to work on their side, they are using worldserver.

We would like to know if the problem is coming from them or if there is a specific way to import a TM coming from worldserver.

Our GS version is up to date.

Generated Image Alt-Text
[edited by: Trados AI at 6:37 AM (GMT 0) on 5 Mar 2024]
emoji
Rate translation
×
Suggest better translation
×
Parents

  • Hi ,

    Have you tried to import the TMX into a new file-based TM in Studio (2019 SR2 CU4 if possible)? If this works then try to export it again from the file-based TM and finally to import it again into your server-based TM.

    Kind regards,
    Nick
  • in reply to Nick Date

    Hello Nick!
    Yes we did try and unfortunately we get the same error. You can see it read/import the units but when it's done it shows this: 

    Trados Studio screenshot showing an error message after importing units. The message reads 'Object reference not set to an instance of an object.'
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 6:37 AM (GMT 0) on 5 Mar 2024]
  • in reply to Vincent Roy

    Hi Vincent,
    what I have done in similar cases:

    - tested the other 2 import options, especially "imported data will be primarily used with presegmenteded legacy SDL Trados ITD or TTX files" once solved such a problem although we did not intend to use legacy files for translation

    - checked the import option "Import translation units as plain text" - to verify if the issue comes from tags, or whether the whole TMX files is somehow corrupt. Using the plain text import would, of course, not be the preferred scenario because TM leverage would be negatively affected when you do not import the tags

    - verify the TMX file in an XML or TMX editor

    Good luck!

    Kind regards

    Christine
Reply
  • in reply to Vincent Roy

    Hi Vincent,
    what I have done in similar cases:

    - tested the other 2 import options, especially "imported data will be primarily used with presegmenteded legacy SDL Trados ITD or TTX files" once solved such a problem although we did not intend to use legacy files for translation

    - checked the import option "Import translation units as plain text" - to verify if the issue comes from tags, or whether the whole TMX files is somehow corrupt. Using the plain text import would, of course, not be the preferred scenario because TM leverage would be negatively affected when you do not import the tags

    - verify the TMX file in an XML or TMX editor

    Good luck!

    Kind regards

    Christine
Children
No Data