i18n

[dotlambda]

I would help doing the i18n stuff, but I'm not quite sure how you wanted to do it and I never wrote a Chrome extension.
So, the Web Store Description is interazionalized by using a ton of chrome_web_store_description_xx_XX.txt files?
And for the rest, you intend to use message.json files? (cf. https://developer.chrome.com/extensions/i18n)
I can do French and German translations.
Or do you want to avoid i18n in order not to bloat the project?

[cprcrack]

Originally the extension itself had no text to be translated, so I planned to translate just the first part of the Chrome Web Store description. I chose 7 extra languages based on number of speakers and the probability of them knowing English, and I hired some translators on Freelancer.

However, it seems that even for setting different descriptions in Chrome Web Store (which is done manually in the Chrome Web Store Developer Dashboard), the messages.json files must exist for those languages, so I postponed using the translated descriptions. Also, I realized I couldn't translate just the first part of the description with right-to-left languages (Arabic), because it probably cannot be combined with a left-to-right language. And I wouldn't like to spend more money on translations at the moment, so the situation is kind of blocked in that sense.

Moreover, if I want to translate the extension's internal strings (such as the drop.js options menu texts), it's not clear for me what the best approach would be for choosing the language. Chrome will suggest (and maybe automatically select) one language, but if it doesn't match WhatsApp site's language, it could be strange for the user.

However, I would really like to see WAToolkit translated to those 7 extra languages in the future, so a pull request that makes use of the i18n API will definitely be merged, even if it initially contains untranslated texts.

With regards to French and German translations, I prefer not to include those languages because the majority of those speakers probably know English as well, and not to bloat the project, as you mention.