Ability to add custom Localization Language attributes

@lpicone , could you please provide a bit more detail on your use case? Is it that you need to use the locale “419” so that your translations do not default to “es”? 

We have worked with the localization features quite a bit and have found some workarounds. If your default version of Spanish is Latin American Spanish, you can load your XLIFF files into the “es” default and any locale should default to the parent language (in this case “es”).

Example: all xliff files are loaded with <target> equal to “es”. 

If you must differentiate between only two locales, Castellano Spanish and Latin American Spanish, you can try sending a specific locale code for all Latin American Spanish and a specific locale for all Castellano Spanish.

Example: Latin American Spanish = es-CR 

                   Castellano Spanish = es-ES

@JPKelliher 

Sorry! Just seeing this now. ‘es-419’ is the value used by the localisation team. I would like to go the other way, attempting to standardize using just the language value and not the country (except for specific cases).