• State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 431 subscribers
  • Views 3252 views
  • Users 0 members are here
Options
Related

Client cannot open translated package

Aleyna Tusa

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!
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply
  • 0 in reply to Aleyna Tusa

    Aleyna

    Just a small hint that may help debug what is happening here.

    You can check what is inside your return package before you send it off by using the OX app  

    Package Reader

    or simply by making a copy of your .SDLRPX file, changing the file extension to .ZIP and having a look at what's inside.

    This will allow you to check whether your return package contains what you expect it to contain, which should basically be the bilingual SDLXLIFF files.

    As Darren mentioned, you should create the return package before you generate the target or finalise, because this may lead to the return package containing only the target file and no SDLXLIFF. This problem has however been corrected, I believe in 2014 SR2, but I am not sure. So, depending on which version of Studio you use, this may still happen.

    Walter
Children