Provide i18n for multiple languages within emoji-mart itself

[rugk]

#20 added i18n support, but unfortunately this way by letting devs configure it poses two problems:

1. Each app that uses this module has to provide translations for the strings again and again. IMHO, it would be preferable to ship the translations with this component here, so this translation work is done once and not again and again.
2. The Emojis itself are not translated. So you cannot search for "Lachend" as a German user e.g. and get Emojis like 😆.
   E.g. check out Twitter: They do translate Emojis in their Emoji picker, which sometimes is annoying, but sometimes can be helpful. Especially for non-devs or users that hardly speak English. For them, the search is basically not usable.

Note that if 2. is solved, 1. may get an even bigger problem, as you'll have to translate each Emoji (or more, with alternatives etc.).

[nolanlawson]

Each app that uses this module has to provide translations for the strings again and again. IMHO, it would be preferable to ship the translations with this component here, so this translation work is done once and not again and again.

This is an interesting idea, but it potentially introduces a maintenance burden. Perhaps we could use something like weblate to lessen the burden, though.

The Emojis itself are not translated.

This may be a limitation of https://github.com/iamcal/emoji-data which is where the emoji data comes from.

[rugk]

Perhaps we could use something like weblate to lessen the burden, though.

Obviously, choose whatever translation platform you want/you are comfortable with. That's why these are there... 😄

This may be a limitation of https://github.com/iamcal/emoji-data which is where the emoji data comes from.

Oka,y opened iamcal/emoji-data#148 for that.

[Haraldson]

@rugk The tip about CLDR is a step on the way, but I’m always mega confused when arriving at their website. I’ve sifted through available cldr-*-modern repos on npmjs.com, but didn’t find which package includes the specified set of strings. Would you consider elaborating on this in the docs?

[rugk]

@Haraldson Do the following instructions from my downstream browser add-on using this lib here help?
See https://github.com/rugk/awesome-emoji-picker/blob/master/CONTRIBUTING.md#translating-emoji-terms-categories-skin-names-etc

[Haraldson]

@rugk I’m just as confused as before. What I’m specifically looking for, as a JavaScript developer, is a way to programmatically get my hands on the specified strings.

As an adjacent-ish example, I use this local script for fetching a list of localized country names.

I’ve had a look at cldr-annotations-modern, but was only able to find annotations for each emoji, and not for the categories they belong to – the same strings the documentation claims exist somewhere.

Also, the names available in main sometimes use other keys than what is specified in emoji-mart, and sometimes the same – and the category names are uncapitalized. :/

[rugk]

well… yeah… I totally feel your frustration, because I also never can see where there is anything on that site…
And when you want to scrape that programatically… uff… I don't know. IIRC you can download a ZIP and just do it locally, that might be easier.

Anyway, I guess the best place is to ask the Unicode people there… they can likely help you better than we can do that. 😅
Though if you'll find a solution, feel free to share it here, too.

[EtienneLem]

Multiple languages support is now built-it