As you see the previous page, it's not a trivial task to keep languages aligned. To stand any chance, we need a pivot code. Every incoming code is converted into this internal code, and every output is based on it. The language you see when you change field settings shows this code list.


Until version 6.2, that pivot format was the MultiTerm code list. But after a lot of research, I found that I'm losing some languages, and had some inconsistent output. So from version 6.3, the Trados Studio list is used, or at least something closely based on it.


For example: 

  • You start with a spreadsheet containing the header Hmong
  • The Glossary Converter recognises it and sets the internal code to zh-x-hmn-sdl. 
  • When you convert the spreadsheet to a Termbase, it uses the internal code to look up the MultiTerm equivalent. I turns out it is ZH-HM-SDL
  • If you convert the same spreadsheet into a tbx file, TBX would accept the internal code, since it is is valid BP 47, but if possible, should use the equivalent ISO code. It is possible in this case, and the code written to the tbx output is hmn-CN
  • Finally, for a conversion to a translation memory, the internal code zh-x-hmn-sdl is kept, since it actually is based on Studio code.

Created with the Personal Edition of HelpNDoc: iPhone web sites made easy