ElkArte Community Modern, Free, Powerful
Community building forum software

This ended up being a bit of a chore.  The upload is of-course easy, its standard push/pull commands.  The chore was that we changed the way lanaguage files are named and where they are storred in 2.0

In 1.1 it was /themes/languages/admin.lang1.php ... admin.langx.php
In 2.0 it is /sources/ElkArte/Languages/Admin/lang1.php ... langx.php

Renaming is not a big deal, but we had new strings, new area/files, changed strings, removed strings.  So I wrote a little best guess program that compared each area, like Admin 2.0 to 1.1. 

• If the string key existed in both and the values were they the same use it,
• If the string was missing drop it
• If the string was only different by capitalization/punctuation, use as is,
• If it they were close based on a levenshtein_ratio use as is, otherwise drop it as untranslated.
• If the translated string is just English strings, drop them. 

So what is now in Transifex under ElkArte-2.0 is cleaner than what we have had before and the % translated is more accurate.

Also for fun, I wrote a small program that pulls untranslated strings from Transifex, runs them through an OpenAI model and stuffs them back into Transifex.  You specify the area, like Admin, the language like German/de and the program does the rest.  Of course those models are not free to run so I did it as an experiment ... and it works!

Still have to write the program that pulls the language files from Transifex and creates the packages.

And I've created the package build automation and updated translations site so they can be downloaded.  Next to test to make sure the package build did its thing correctly.

Look at you working your Butt off   

Wish I had those moves 

Downloaded it (the Malay package) but not sure how to test it since 2.0 is not yet released. Also the content is English, not translated at all.