The error suggests your sdlxliff file is corrupt, and if you opened it in a text editor and couldn't see anything there then this would seem to be the case.  If you'd like me to validate this please email me your zipped up project - pfilkin@sdl.com

Presumably you were using a Translation Memory and can therefore recover your translations from there?

Hi

I sent the complete zipped project file.

I opened it in a text editor and I could see some strange texts there.

I was using a translation memory but opening it, I also face error and can't see anything.

I’m afraid these files have been badly corrupted and are not recoverable in full.  For this to happen it looks as though you have either got a problem with your computer, or you’re using an external drive that perhaps lost connection halfway through backing or synchronising perhaps… or even have some aggressive security software installed that interfered with a backup, or the operation of Studio.

I was only able to do two things:

1. Piece together some of the target sdlxliff and recover around 500 segments.  This is what your actual file looked like:
   
   I hid the source text in the image and just showed the point where the file is corrupt.  To fix it I used the content of the source SDLXLIFF which was the only file unaffected by whatever happened and replaced the corrupted parts with content of the source.
2. Repair the smaller TM and recover 17 Tus.  I used SDLTM Repair from the appstore to do this.

I’m afraid you will have to do this over again.  I would recommend a few actions for you:

1. Investigate the potential causes for this (security software, backup devices, where you’re storing your projects)
2. Implement a regular backup routine for your work so you only lose a days work at most if a catastrophic event like this occurs.

I’m afraid these files have been badly corrupted and are not recoverable in full.  For this to happen it looks as though you have either got a problem with your computer, or you’re using an external drive that perhaps lost connection halfway through backing or synchronising perhaps… or even have some aggressive security software installed that interfered with a backup, or the operation of Studio.

I was only able to do two things:

1. Piece together some of the target sdlxliff and recover around 500 segments.  This is what your actual file looked like:
   
   I hid the source text in the image and just showed the point where the file is corrupt.  To fix it I used the content of the source SDLXLIFF which was the only file unaffected by whatever happened and replaced the corrupted parts with content of the source.
2. Repair the smaller TM and recover 17 Tus.  I used SDLTM Repair from the appstore to do this.

I’m afraid you will have to do this over again.  I would recommend a few actions for you:

1. Investigate the potential causes for this (security software, backup devices, where you’re storing your projects)
2. Implement a regular backup routine for your work so you only lose a days work at most if a catastrophic event like this occurs.