Why Trados picks Chinese SAR over Traditional when starting Project

When a Drupal XLF file is brought into Trados for translation it picks the target language for Hong Kong SAR instead of Traditional, Taiwan.

Trados Studio language selection showing Source Language as English (United States) and Target Language as Chinese (Traditional, Hong Kong SAR).

This is the header information in the XLF file:

<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:xsi="">www.w3.org/.../XMLSchema-instance" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2-strict.xsd">
 <file original="xliff-core-1.2-strict.xsd" source-language="en" target-language="zh-hant" datatype="plaintext" date="2024-03-26T08:03:41Z">
  <header>
   <phase-group>
    <phase tool-id="tmgmt" phase-name="extraction" process-name="extraction" job-id="18726"/>
   </phase-group>
   <tool tool-id="tmgmt" tool-name="Drupal Translation Management Tools"/>

When in Trados this can be easily fixed when Chinese is the only language picked, but if we use the Default setting for several languages do not have the option to change language back to Traditional.   This also becomes an issue when we use the Groupshare API within Plunet to run file Analysis and get an Object not set an instance of an object error and Plunet states it is because missing the SAR target setting.  Our Trados template is for Traditional Taiwan.

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



Generated Image Alt-Text
[edited by: Trados AI at 3:19 PM (GMT 0) on 26 Mar 2024]
emoji
Parents Reply
  •  

    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.

    emoji
Children
No Data