In-App Translation about autoplugin HOT 6 CLOSED

a table for each language!!!

from autoplugin.

spanish = {MENU_TITLE="Autoplugin" ....}
english = {MENU_TITLE="Autoplugin" ....}
...

and switch
language = spanish

then only show info with con language
language[MENU_TITLE]

from autoplugin.

For some reason I couldn't get it to work like that. With the code:
test = {TEST="My Test", TEST2="My Test 2"}
os.message(test[TEST])
os.message(test[TEST2])

It would crash stating that they were nil when os.message expects a string. There's not really a whole lot of reason to keep all of those tables in memory IMO. When the translate page loads, however, there will be a table for each language.

EDIT: Rereading what you wrote, that makes sense and I was thinking about it wrong. I will end up doing something very similar to what you suggested. Thanks!

from autoplugin.

test = {TEST="My Test", TEST2="My Test 2"} <- os.message(test[1]) for My Test

from autoplugin.

another way
test = {

test1 = "My Test", -- important the ,

}
os.mesage(test.test1)

from autoplugin.

I have completed the first iteration of this feature. It currently saves the translations you have made to ux0:data/AUTOPLUGIN/.lua so they can be sent to us here and we can add them to the files or the translator can add them.

The ones with no translation are listed first, then all the rest of the translations are dumped onto the page. I'm open to feedback.

from autoplugin.