What is the process for adding additional locales?

[Pearce-Ropion]

What is the process for adding additional locales?
Is there a public localization platform that we can contribute to (like Crowdin)?

We are happy to go ahead an make a few PRs to add additional localizations but were wondering if there was an easy way to get a list of all the viable strings that need to be translated short of going through each package individually and extracting the strings manually?

[devongovett]

There is no public process right now. The Adobe Globalization team handles translations for us. What additional locales are you looking for?

[Pearce-Ropion]

The most important one that we would like to see that you are missing is th-TH (Thai). My company also has explicit support for en-GB, en-AU and fr-CA but we can easily add mappings to the their fully localized counterparts (en-US and fr-FR respectively) so those aren't as important.

[Pearce-Ropion]

Oh, I guess technically en-GB and fr-CA are already supported, there just aren't any specific translations for those locales.

I will make an issue to request th-TH support.

[maranomynet]

It's so unfortunate that you treat translations as a closed-box process, instead of allowing devs to provide their own translations manually. This design decision severly limits the access of this library to billions of people around the world.

[devongovett]

I'm not really sure how we could do that without making it a breaking change whenever we add/change a string. Do you have any ideas?