Unexpected error when detecting file type for file [...] hexadecimal value 0x00 is an invalid character line 1 position 1: project sdlxliff won't open and only 15% (of 14000 words) of translation in TM!

Hello!

I know this topic already appears in other threads, but I think my situation is slightly different. I was working on a package sent my the client, and when I finished the translation (14000 words) with all the segments confirmed, when I clicked on "create bilingual review", my screen froze and I had to reboot.

When I opened Studio again, the Projects pane was empty and when I opened the package again there was no translation in the target segment. I tried opening the project's sdlxliff (with all the translation in it) but I got the error message above....

Then I opened an untranslated version of the sdlxiff as a single document and connected the TM I had used with the project, but only around 15% of the translation appeared as 100% matches (fairly randomly throughout the text).

Any ideas? It's a TM sent by the client, and I did a large file with it last week without any issues. The source file is RTF (would that make a difference?) and my version of Studio is 2017.

Thanks,

Neil

Translate

Rate translation

Suggest better translation

Moderator UI

Thread Subject & Description
Unexpected error when detecting file type for file [...] hexadecimal value 0x00 is an invalid character line 1 position 1: project sdlxliff won't open and only 15% (of 14000 words) of translation in TM! Hello! I know this topic already appears in other threads, but I think my situation is slightly different. I was working on a package sent my the client, and when I finished the translation (14000 words) with all the segments confirmed, when I clicked on "create bilingual review", my screen froze and I had to reboot. When I opened Studio again, the Projects pane was empty and when I opened the package again there was no translation in the target segment. I tried opening the project's sdlxliff (with all the translation in it) but I got the error message above.... Then I opened an untranslated version of the sdlxiff as a single document and connected the TM I had used with the project, but only around 15% of the translation appeared as 100% matches (fairly randomly throughout the text). Any ideas? It's a TM sent by the client, and I did a large file with it last week without any issues. The source file is RTF (would that make a difference?) and my version of Studio is 2017. Thanks, Neil
Get AI Suggestion

AI Reply

Accept answer Reject Answer

0 Neil Morrison over 4 years ago

Correction: the source file is a txt Notepad file...

Documentation Survey: help us offer you better documentation! Translate
0 Lydia Simplicio over 4 years ago in reply to Neil Morrison

Hi Neil Morrison

I suppose what is concerning you is that the data isn't saved in the TM either? Are you confirming segments as you translate with the appropriate settings in place to ensure TM's update on the fly?

The settings would be:

1. TM enabled for update
2. File - Options - Editor - Automation and enable: Update translation Memory

As you may have seen in other posts, I reckon you would need to follow the advice from here: https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0034155
If you want, you can share the file with in a manner you deem safe and secure and I can try look into it for you also.

The goal would be to fix your file - so your translated segments can be retained.

In the meantime, I wonder if you have any autosaved versions you can fall back on?
AutoSaved files can be seen here: C:\Users\[user name]\Documents\Studio 2021\AutoSave

Lyds

Lydia Simplicio | 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

Documentation Survey: help us offer you better documentation! Translate
0 Neil Morrison over 4 years ago in reply to Lydia Simplicio

Hi Lydia!

Thanks so much for your reply. Yes, all the segments were confirmed and AutoSave was on (although I'm not able to find any Autosaved files anywhere..?). I'm going to try to fix this now.

It's just so weird how 15% of the data was saved in the TM.

So do you reckon this is a fault with the source file (a txt file)?

Best,

Neil

Documentation Survey: help us offer you better documentation! Translate
0 Lydia Simplicio over 4 years ago in reply to Neil Morrison

Hey Neil Morrison

A few points.

When replying please use @ then my name so Im tagged and notified. Otherwise I may miss your update.

In all my experience with this software years +, source file has had no impact on TM's ability to save TU.

Corrupt sdlxliff is another story, but then the data was in the TM so a pre-translate was always an option.
Happy to take a look at your file if you are willing to share it with me.

Lyds

Lydia Simplicio | 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

Documentation Survey: help us offer you better documentation! Translate
0 Neil Morrison over 4 years ago in reply to Lydia Simplicio

Hey Lydia Simplicio

Thanks but I'm not able to share the file for confidentiality reasons. Everything seemed to be saving fine as I was going along, and then right at the end when I was finished, it crashed and I somehow lost 85% of the data in the TM.

So who knows, maybe it's actually a problem with my laptop or something....

So you think there's no way the data in the corrupted xliff file can be retrieved?

Best,

Neil

Documentation Survey: help us offer you better documentation! Translate
0 Lydia Simplicio over 4 years ago in reply to Neil Morrison

Neil Morrison have you tried looking at article https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0034155

Lydia Simplicio | 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

Documentation Survey: help us offer you better documentation! Translate
0 Neil Morrison over 4 years ago in reply to Lydia Simplicio

Hey Lydia Simplicio

I really appreciate your help and suggestions. Unfortunately, it turned out nothing could be done to open the corrupted xliff, and 11,000 words were irretrievably wiped from the TM. I ended up having to translate it again (which wasn't much fun). I guess it's just one of those inexplicable glitches...

Best,

Neil

Documentation Survey: help us offer you better documentation! Translate

Trados Studio > 1. Trados Studio

Unexpected error when detecting file type for file [...] hexadecimal value 0x00 is an invalid character line 1 position 1: project sdlxliff won't open and only 15% (of 14000 words) of translation in TM!