Forum: CAT Tools Technical Help
Topic: Lionbridge PMs can "detect" the use of SDL over their proprietary CAT tool?
Poster: Samuel Murray
Post title: Yes, or...
[quote]Stepan Konev wrote:
Trados changes the file structure so that they clearly see that. [/quote]
Additionally, it's possible that Trados does NOT change the file structure, in places where TWS would be expected to change it.
Rebekah, most CAT tools are satisfied if they can produce an exported XLIFF file that is compliant with the XLIFF specification, even if it isn't 100% compatible with the original CAT tool's specific implementation of XLIFF. When you translate the Lionbridge XLIFF file in Trados, you don't tell Trados that it is a Lionbridge XLIFF file, so even if the Trados developers were clever enough to make Trados create an XLIFF export that is indistinguishable from Lionbridge's other XLIFF files, it wouldn't happen in your case.
The fact that Trados can't open Lionbridge XLZ files directly (i.e. the fact that you have to unzip it manually) leads me to suspect that Trados can't produce Lionbridge-specific XLIFF files. This means that certain tell-tale signs that TWS was used, would be absent from the files, and PMs at Lionbridge might be able to see that.
This does not answer the question why Lionbridge considers your XLIFF files to be corrupted, though. You're doing something else wrong. It's also possible that the PMs are using the word "corrupted" in a special way that doesn't mean what it usually means, and that they're actually referring to some other preference that you are failing to implement.
Your unzipping and re-zipping procedure assumes that TWS uses certain default ZIP settings when zipping the file. Do you open the final XLZ file in TWS to check if it recognizes the file? When I do a Trados job for a client, and I don't use Trados for the translation itself, then I always open the final file in Trados to check if Trados is happy with it. I would do the same with TWS. In fact, opening in TWS, making one small change, and then saving the file, might be sufficient to fix the entire file.
Stepan's procedure of re-translating against a TM is also a good idea, although doing that might alter the fuzzy match percentages in the file, so that PMs can see that you had re-translated the file against a TM.
[quote]Rebekah Olson wrote:
My 5 languages for my Trados are already claimed...[/quote]
Does the latest version of Trados still limit one to just 5 languages?
[Edited at 2022-12-24 11:50 GMT]
Topic: Lionbridge PMs can "detect" the use of SDL over their proprietary CAT tool?
Poster: Samuel Murray
Post title: Yes, or...
[quote]Stepan Konev wrote:
Trados changes the file structure so that they clearly see that. [/quote]
Additionally, it's possible that Trados does NOT change the file structure, in places where TWS would be expected to change it.
Rebekah, most CAT tools are satisfied if they can produce an exported XLIFF file that is compliant with the XLIFF specification, even if it isn't 100% compatible with the original CAT tool's specific implementation of XLIFF. When you translate the Lionbridge XLIFF file in Trados, you don't tell Trados that it is a Lionbridge XLIFF file, so even if the Trados developers were clever enough to make Trados create an XLIFF export that is indistinguishable from Lionbridge's other XLIFF files, it wouldn't happen in your case.
The fact that Trados can't open Lionbridge XLZ files directly (i.e. the fact that you have to unzip it manually) leads me to suspect that Trados can't produce Lionbridge-specific XLIFF files. This means that certain tell-tale signs that TWS was used, would be absent from the files, and PMs at Lionbridge might be able to see that.
This does not answer the question why Lionbridge considers your XLIFF files to be corrupted, though. You're doing something else wrong. It's also possible that the PMs are using the word "corrupted" in a special way that doesn't mean what it usually means, and that they're actually referring to some other preference that you are failing to implement.
Your unzipping and re-zipping procedure assumes that TWS uses certain default ZIP settings when zipping the file. Do you open the final XLZ file in TWS to check if it recognizes the file? When I do a Trados job for a client, and I don't use Trados for the translation itself, then I always open the final file in Trados to check if Trados is happy with it. I would do the same with TWS. In fact, opening in TWS, making one small change, and then saving the file, might be sufficient to fix the entire file.
Stepan's procedure of re-translating against a TM is also a good idea, although doing that might alter the fuzzy match percentages in the file, so that PMs can see that you had re-translated the file against a TM.
[quote]Rebekah Olson wrote:
My 5 languages for my Trados are already claimed...[/quote]
Does the latest version of Trados still limit one to just 5 languages?
[Edited at 2022-12-24 11:50 GMT]