Forum: CAT Tools Technical Help
Topic: Lionbridge PMs can "detect" the use of SDL over their proprietary CAT tool?
Poster: Rebekah Olson
Post title: Clunky af
[quote]Stepan Konev wrote:
[quote]Maurits Meulenbelt wrote:
I have also translated Lionbridge’s xlz files with Trados in the past, and that worked well, without having to unpack them and jumping through any hoops. Just add them to a Trados project as-is. Of course that means you can’t use their translation memories, so you might want to stick with XLIFF Editor. It’s not that bad. [/quote]When you save your translation from Trados, the output file structure is always different from the input file. That is why they can see that you used Trados and that is why they forbid using CAT tools other than their TWS XLIFF Editor.
Also I wonder what can be worse than TWS that fails to run simple commands like Ctrl+A, Ctrl+C/V, etc.
[/quote]
Seriously - the clunkiness of the command prompts is absurd. This thing looks like it was built in 1995 and never updated (though I know it has been). You can't do hardly anything with it and to manually have to click into every cell if your keyboard (like many laptops) doens't have a separate "end" key is ridiculous. It's taking me ages to translate in this program, but if I use Trados, I don' have access to their TMs.
Wondering if I could -
1. Open XLZ in XLIFF editor
2. Auto-populate all TMs matches (is this even possible?)
3. Save and then open saved XLZ in Trados
4. Work on file
5. Save and then open saved Trados file in XLIFF editor (the program seems to have a convertor?)
Do you think this ridiculously round-about process would work?
Topic: Lionbridge PMs can "detect" the use of SDL over their proprietary CAT tool?
Poster: Rebekah Olson
Post title: Clunky af
[quote]Stepan Konev wrote:
[quote]Maurits Meulenbelt wrote:
I have also translated Lionbridge’s xlz files with Trados in the past, and that worked well, without having to unpack them and jumping through any hoops. Just add them to a Trados project as-is. Of course that means you can’t use their translation memories, so you might want to stick with XLIFF Editor. It’s not that bad. [/quote]When you save your translation from Trados, the output file structure is always different from the input file. That is why they can see that you used Trados and that is why they forbid using CAT tools other than their TWS XLIFF Editor.
Also I wonder what can be worse than TWS that fails to run simple commands like Ctrl+A, Ctrl+C/V, etc.
[/quote]
Seriously - the clunkiness of the command prompts is absurd. This thing looks like it was built in 1995 and never updated (though I know it has been). You can't do hardly anything with it and to manually have to click into every cell if your keyboard (like many laptops) doens't have a separate "end" key is ridiculous. It's taking me ages to translate in this program, but if I use Trados, I don' have access to their TMs.
Wondering if I could -
1. Open XLZ in XLIFF editor
2. Auto-populate all TMs matches (is this even possible?)
3. Save and then open saved XLZ in Trados
4. Work on file
5. Save and then open saved Trados file in XLIFF editor (the program seems to have a convertor?)
Do you think this ridiculously round-about process would work?