Forum: CAT Tools Technical Help
Topic: Converting TMs and glossaries between CATs
Poster: Lianne van de Ven
Post title: You translated a sdlxliff file
[quote]Louise TAYLOR wrote:
Thanks for your reply Samuel
Evidently I didn't explain myself well enough.
My client wants a TXML file - from wordfast. I produced the file in studio and imported the sdlxliff file into wordfast. Then downloaded a txml file. The file extension is fine.
It is an issue with the clients project management system which cannot upload my converted file, it is not in the right format even though it tells me that it is.
Best [/quote]
Assuming that with "I produced the file in Studio" you mean that you had a source file and created a sdlxliff out of that with Studio, then opened that sdlxliff in Wordfast, creating a txml (or rather: sdlxliff.txml), you effectively translated a sldxliff in Wordfast. Your client should be able to read this txml in wordfast, but when you use "save translated file", it saves it as a sdlxliff again, and it cannot be read without Studio. You would have to open that file in Studio and use "save target as" to get the output in original format. The question would be why you created a sdlxliff in the first place (I did not read the entire thread)?
As for converting sdltm to a tmx or sdltb to cvs/txt on any system, try TradosStudioResourceConverter (use the not so blaring download link): [url removed]
It is very easy to use. Clicking on the .jar file opens a dialog box from which you can select the file you want to convert. It will automatically be saved in that same location and be named converted.tmx or converted.cvs etc.
For viewing/editing tmx files, you can use Okapi Elephant (on windows): [url removed]
I have not found a good/easy tmx viewer for mac OS yet.
I hope some of this helps.
[Edited at 2017-02-06 16:33 GMT]
Topic: Converting TMs and glossaries between CATs
Poster: Lianne van de Ven
Post title: You translated a sdlxliff file
[quote]Louise TAYLOR wrote:
Thanks for your reply Samuel
Evidently I didn't explain myself well enough.
My client wants a TXML file - from wordfast. I produced the file in studio and imported the sdlxliff file into wordfast. Then downloaded a txml file. The file extension is fine.
It is an issue with the clients project management system which cannot upload my converted file, it is not in the right format even though it tells me that it is.
Best [/quote]
Assuming that with "I produced the file in Studio" you mean that you had a source file and created a sdlxliff out of that with Studio, then opened that sdlxliff in Wordfast, creating a txml (or rather: sdlxliff.txml), you effectively translated a sldxliff in Wordfast. Your client should be able to read this txml in wordfast, but when you use "save translated file", it saves it as a sdlxliff again, and it cannot be read without Studio. You would have to open that file in Studio and use "save target as" to get the output in original format. The question would be why you created a sdlxliff in the first place (I did not read the entire thread)?
As for converting sdltm to a tmx or sdltb to cvs/txt on any system, try TradosStudioResourceConverter (use the not so blaring download link): [url removed]
It is very easy to use. Clicking on the .jar file opens a dialog box from which you can select the file you want to convert. It will automatically be saved in that same location and be named converted.tmx or converted.cvs etc.
For viewing/editing tmx files, you can use Okapi Elephant (on windows): [url removed]
I have not found a good/easy tmx viewer for mac OS yet.
I hope some of this helps.
[Edited at 2017-02-06 16:33 GMT]