Internationalization of messages and commands [i18n] about telegram-bot HOT 3 OPEN

I have never used .potfile but I think the best way is writing lua tables just like:

pt_br = {
  ["Sending message"] = "Enviando mensagem"
}

Then, in the code, call to a function like __("Sending message") that will check if there is a translated
phrase for this one. Language could be configured inside data/config.lua

from telegram-bot.

I believe a more elaborated approach would be better, to handle cases where non positional arguments must be inserted on the string. An option would be i18n.lua, which can be added to our LuaRocks dependencies.

My suggestion is to load the translation files recursively from a folder, on load_config. The path structure would be translations/<two-letter-language-code>/<scope>.lua, where scope is common or the plugin name (this would make it easy to manage the strings). Once loaded, we can set the locale from a config and expose (it's not necessary, I believe) a method so a plugin could change it on the fly.

The project could be divided in phases: implementing i18n on the core (loading it, applying the config and the common strings); extracting the strings from plugins; translating the files.

from telegram-bot.

Nice way @JulioC but I dont have time now... 😢

from telegram-bot.