In WorldServer, there are 3 Languages associated with language/ISO code es-ES that can be added to the Locales under Management > Business Rule Linkage > Locales :
This means that the User needs to open the scroll-down menu, find the language and select it. This is the same behaviour you would encounter if you are trying to import a TMX file that contains a language that is not present at all in WorldServer and so you need to "tell" the system which language should be used. On the other hand, if an WorldServer environment contains language Spanish (Castillian) when importing a TMX file with content in es-ES Language ISO Code, Spanish (Castillian) will be automatically found and selected: |
Workaround: In the TMX file to be imported, replace <tuv xml.lang="es-ES"> Note: upon export from WorldServer, the language code will again become <tuv xml.lang="es-ES"> (the default lang code in WorldServer) which proves that the previous import was accepted by WorldServer. REMEMBER: The above instructions are for the TUV elements in the TMX file. If this language is the source language, then there is also a language code in the header of the TMX and in each element. So you need to replace srclang="es-ES" as well with srclang="Spanish (International Sort)". A simple solution is to replace all instances of lang="es-ES" with lang="Spanish (International Sort)" in one go. |
This issue has been filed as defect CRQ-17100. |