localization/internationalization (l10n/i18n)

[andreruffert]

I was wondering if you already thought about localization/internationalization.
There is already a PR (#6) for that. What do you think about this approach?

I think it might be complicated to maintain. If you want to add/change an emoji you have to do it in n files.
My idea would be a format e.g.

emojis.json

[
  {
    "char": "🍍",
    "name": {
      "en": "emoji_name",
      …
    },
    "keywords": {
      "en": ["keyword1", "keyword2"],
      …
    },
    "category": {
      "en": "emoji_category",
      …
    }
  },
  {
    …
  }
]

Here you could maintain one file and parse it in a build process etc. to create the different files for each language (emojis_en.json …) in the format like it is now.

What do you think? 😊:v:

[muan]

Hi! This has been previous discussed in muan/emoji#37 and muan/emoji#67. All in all I'd prefer a separate file, especially when maintainers for each language is likely going to be different. 👀

[andreruffert]

Alrighty! ✌️