support i18n
Hi there...Can I work on this issue ?
Hi, @vihar-s1
Of course, that's nice of you.
thank you!
can you brief me once on what you are expecting from the i18n support so I that can work on this accordingly.
I don't have a specific idea at the moment. It is worth considering this so that it makes sense in the final version
no worries...I see what I can do
So I did some research from my end and I will require some assistance here from your end as well. I need to clarify as to what text do you want to get translated before I begin. The i18n support heavily depends on the context of what is being translated. The best I could do right now is create a workflow, which when triggered would run some scripts to setup i18n files but i would still need to know what I am data I am going to map in the i18n files
I think we need easy to use API to translate all parts of command such as arguments (also depending on language of sender, (one exception, discord don't support dynamic command structure)) Unfortunately I don't know how API could look good...
Second idea: We can think about placeholder system to easy translate commands from plugin configuration
so, the thing is, or the multi-language support, i18n files need to be generated which are basically sort of map of language vs text. It would be easy to generate the english language mapping. What I am thinking is that I can use some translation API to generate the text in other languages from the english language mapping