Hello Alvin,

A good place to ask this question is the Translation Productivity Community as this group has users across our language space.

Generally care needs to be taken with specifics, so we would not use English for example.  We would use English (US), English (GB), English (AU) for example.  This is really only important for us when the bilingual file we handle for translation is produced.  So if you are creating XLIFF files for example then it would make good sense to ensure consistent language codes are used.  If you used en-US and the translator was used to working with en-GB then potentially this can be difficult for the translator to manage as all their resources will be based on different language variations.  There are ways to workaround this but consistency is better.

But please ask in the Translation Productivity Community as I'm sure there are people dealing with your end of the supply chain who can elaborate more on this topic.

Hello Alvin,

A good place to ask this question is the Translation Productivity Community as this group has users across our language space.

Generally care needs to be taken with specifics, so we would not use English for example.  We would use English (US), English (GB), English (AU) for example.  This is really only important for us when the bilingual file we handle for translation is produced.  So if you are creating XLIFF files for example then it would make good sense to ensure consistent language codes are used.  If you used en-US and the translator was used to working with en-GB then potentially this can be difficult for the translator to manage as all their resources will be based on different language variations.  There are ways to workaround this but consistency is better.

But please ask in the Translation Productivity Community as I'm sure there are people dealing with your end of the supply chain who can elaborate more on this topic.