David McDermit 

David McDermit said:

Why does Trados automatically pick zh-hant to the  SAR target language.

I think it's most likely because zh-hant is a code without a variant under the MS LCID codes:

So it takes the next one in the list which is what you're seeing.  If the fully qualified language isn't stated then we don't know which one to use.

 David McDermit 

David McDermit said:

Why does Trados automatically pick zh-hant to the  SAR target language.

I think it's most likely because zh-hant is a code without a variant under the MS LCID codes:

So it takes the next one in the list which is what you're seeing.  If the fully qualified language isn't stated then we don't know which one to use.

Paul Makes sense.  Is there a way to change this order?  I do not think there is a way in the Drupal program to add TW to the file.   This SAR seems to be causing this error: Object reference not set to an instance of an object

David McDermit 

David McDermit said:

Is there a way to change this order

No.  The answer is to use a fully qualified code, or don't use the XLIFF filetype. However, I guess you could automate correcting the code quite easily for all files before you create your projects.  Just run a script to make sure all the files contain the code you need.  Then put the old code back when you're finished with the translation.  All additional work I know, but if the files are not provided with a fully qualified language code to start with who are we to know which one to use? 

Having said that we don't use American Samoa if you only have English... so the principle I guessed at above isn't consistent.  Perhaps worth creating an idea for that one?  If the "norm" is to use zh-TW when there is no variant specified then perhaps it's a change the product team would see fit to deliver.