You are currently working on UAT
Greetings,
I have been working on a project translating from Mexican Spanish into US English. I am needing to add files from another translator to this project, which have been sent to me as .xml bilingual files and I get an error because the source text for these is Spain/International Spanish and Trados cannot import the files.
Is there any way for me to import the files?
Thanks,
Ryan
Sorry, they are .xlf files.
If you must import these into the same project... so the fact the project is Mexican Spanish doesn't matter... then change the language codes in the XLIFF.
Paul Filkin | RWS
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
Thank you, Paul! I used Notepad and was able to CTRL+F my way to where the source language was defined, and I made the change from es to es-MX. Trados seamlessly imported the file.
Paul, I have come across a new problem: when generating the target translation I get an .xml file and not a Word document file. Is there something else that I have to do?
Paul, I have come across a new problem: when generating the target translation I get an .xml file and not a Word document file. Is there something else that I have to do?
The source was XLIFF so your target should also be an XLIFF. Why would you expect a Word file?
Paul Filkin | RWS
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
I see; so if I understand correctly, I'll have to request the other translator to send me his Word documents in the source language and add the content of the .xlf file to the translation memory to then repopulate the source text Word document for .docx export?
Well... that certainly sounds like what you'll have to do. It's quite difficult to give you sensible answers to all your questions because you have not told us what you have really done.
I'm getting the picture now though and it sounds something like this:
1. The other translator was provided with a Word file
2. The other translator is not using Studio, so he exported an XLIFF from his preferred CAT
3. You opened this XLIFF in your Project (where you are using different variants to the other translator)
4. Now you want to generate the target Word file
Your choices are either send the XLIFF back to the other translator and ask him/her to generate the target Word file; or go through the process you described and update your TM to pretranslate the source Word file.
If this is what you did the process in future should be this:
1. You create the project
2. You send the SDLXLIFF from your target folder to the other translator
3. The other translator sends you the translated SDLXLIFF back
4. You replace the SDLXLIFF in your project wth this updated one and save the target
Paul Filkin | RWS
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
Understood. Thank you, Paul. This is my first foray in having to work with another unrelated translator for a client and that translator not working within Trados. I understand how to make the process smoother moving forward.
Translate
