Are Transit language pairs always in UTF-16 LE?
Thread poster: 2nl (X)
2nl (X)
2nl (X)  Identity Verified
Netherlands
Local time: 07:03
Jun 24, 2015

Are Transit language pairs always in UTF-16 Little Endian, or can they also be encoded in UTF-16?

Hans


 
Why? Jun 24, 2015

Why should they?

As far as I know, language pairs are used as a kind of internal file format. Two different variants (little / big endian) would just be trouble breeding without benefit... Or did I miss something?

Best regards,

O.N.


 
Peamur
Peamur
Local time: 07:03
for what Jun 24, 2015

For Transit? Or for some other application?
I guess, as long as they are utf-16 (doesn't matter which encoding), it's ok, but I would test it.


 
2nl (X)
2nl (X)  Identity Verified
Netherlands
Local time: 07:03
TOPIC STARTER
Interoperability Jun 25, 2015

Peamur wrote:

For Transit? Or for some other application?
I guess, as long as they are utf-16 (doesn't matter which encoding), it's ok, but I would test it.


My question is indeed related to interoperability. Since Transit doesn't support the creation of XLIFF files (by default), I had to use the language pair files in 'the other app'.

All is fine now, thanks!


 


To report site rules violations or get help, contact a site moderator:

Moderator(s) of this forum
Maya Gorgoshidze[Call to this topic]

You can also contact site staff by submitting a support request »

Are Transit language pairs always in UTF-16 LE?






Trados Business Manager Lite
Create customer quotes and invoices from within Trados Studio

Trados Business Manager Lite helps to simplify and speed up some of the daily tasks, such as invoicing and reporting, associated with running your freelance translation business.

More info »
Trados Studio 2022 Freelance
The leading translation software used by over 270,000 translators.

Designed with your feedback in mind, Trados Studio 2022 delivers an unrivalled, powerful desktop and cloud solution, empowering you to work in the most efficient and cost-effective way.

More info »