Worldserver incorrectly maps Spanish (International Sort) as LCID 21514.

But LCID 21514 stands for Spanish (United States) as stated on this Microsoft page.

Moreover, Spanish (United States) also has an incorrect LCID assigned, and based on the above documentation Spanish (Traditional Sort) is missing entirely from WorldServer.

The workaround involves updating the languages table in the database and setting the corresponding names to the LCIDs.

Since LCID 21514 is incorrectly mapped to Spanish (International sort) then you would update this value and map it as Spanish (United States).
Same for LCID 1034 which is incorrectly mapped to Spanish (Castilian) you would update the value of the name to point to Spanish - Spain (Traditional Sort) and so on.

Note: only update the values of the name column from the languages table.
In the end, you should have the Spanish (International Sort) locale mapped to the Spanish (Spain, Traditional Sort) language name which in the database would have the 1034 LCID.



After you are happy with the results in the table and the UI there is a matter of updating your TMs as well.
Depending on how many TMs you use for Spanish, you would have to export them and re-import them under the new language name Spanish - Spain (Traditional Sort).

To fix the LCID mismatch in WorldServer, we logged defect CRQ-33315 which is still under investigation by our development team.

CRQ-33315