Client cannot open translated package

Hello,

I'm hoping someone can help with the following (I didn't see anything similar on the forum). One of my regular clients has suddenly started to experience  problems with the translated packages I return to them. This has happened for several consecutive projects. It happens as follows:

1. I receive package.

2. I open package and create project on my computer. I receive an error message that the path name is too long, so I create I shorter path.

3. I translate and complete the project. No errors are encountered.

4. Create return package and email it back to client.

The client has been kind enough to give me some details as to what they see on their end as we work together regularly. They said that the following happens:

1. They open the package and a target file is generated automatically in the project folder on their hard drive, without specifically generating one.
2. When they prepare to import the package it firstly shows up as 100% translated and appears to import without any problems. However, the project then shows up as 0% translated and when they open the bilingual file the translation isn’t there.

I've been sending them an exported .tmx, bilingual and clean file as a workaround for now, but it would be nice to have a resolution for this.

A few relevant additional side notes:
1. This had happened once around three months ago, but then never again. Two weeks ago, the motherboard on my work PC died and I was fortunate enough to not encounter problems with my Trados license by just removing the hard drive and putting it in a new computer. I don't know if this is the cause.
2. I'm running Studio 2011 on Windows 7. My client is running Studio 2014. Compatibility issue?

Thanks!

Parents Reply Children
No Data