Hi! I’m wondering how to go about requesting a new language for translation on Weblate. I would like to add a Hungarian translation if the devs & community are interested. After looking through the guidelines on github I got a decent picture of how the process works for continuing an existing translation but not for starting a new one, if it is at all possible.
Could someone point me in the right direction of who to contact / where regarding this topic? Also, a section on the process of requesting languages might be a useful addition to the Weblate translation guidelines page (I assume I could reach out to the project maintainers directly, but asking this publicly might be helpful for forum users with the same question in the future)
Various sections of the code have to be updated and lupdate has to be run to create the new ts files. It’s a bit tricky. I will be glad to add Hungarian. I can use Google translate to do initial translations… and once they are merged you can then edit on Weblate to fix any inaccuracies. Which there are sure to be some.
Since we now use Weblate, anyone can create a Weblate account and edit the translations. PR’s are automatically generated on Githuub which we can then review before merging.
I have added Hungarian (magyar) to the translations. I translated Seamly2D and Measurements with Google docs. and fixed any beginning or trailing chars. No need to translate QtBase as it’s already comes translated with the Qt install. I ran the translations test and there were no errors… for a change.
I just want to check a few more things to make sure the math functions and variable names are not broken. So sometime Thursday afternoon I’ll push the changes and make a PR. Not sure how fast the translations propagate to Weblate once they are merged? I’ll try and report back if I see the magyar translations on Weblate.
Perfect. I made a PR so now it’s just a matter of waiting a bit.
Just a note for translations to be aware of… variable and measurement names. They can’t have any spaces in them. … which Google likes to stick in. Google also has a hard time translating many of them as they often contain abbreviations that can’t be translated without context. For ex: SplPath… short for Spline Path. Also some of the measurements contain abbreviations like “circ” for “circumference” or “f” for “front” that Google just can’t handle with no context. Also while you can use anything for a translation, keep in mind the measurements are an abstract naming system, not exact terms.
Oh good! I saw that csett & Sue were the only ones listed on Weblate, but I ignored that at the very least there were probably parts of the process which were right up your alley.
I haven’t created a Weblate account yet. Weblate is only the part that allows anyone to edit the translations via the web, and automates the PR process. To actually add a language requires editing the codebase… specifically additions in the project & project include files that are needed to generate the ts files from the code when lupdate is run, and automating the process to generate the binary qm files at build time that are actually used to load the translations. There’s also the flag icon to add, and another bit of code to add the languages to a list that is used by the (dreaded) translationstest.
Then there’s a multistep process I do using an app called ts_tool that takes a ts file, keys the ts translations & generates a keyed text file list of sources which needs to be converted to a docx cus that’s what Google translate wants… upload docx, translate, download translated docx convert back to text file run ts_tool again that now takes the keyed translated text file and replaces the keyed translations in the ts file with the matching keyed translations in the text file. Whew. Actually took me longer to write than to actually translate a ts file.
Fun starts when cleaning up the errors Google Translate produces.
Oh.. BTW… the PR to add the Hungarian translations has been merged and it’s already been added to Weblate.
(I assume I could reach out to the project maintainers directly, but asking this publicly might be helpful for forum users with the same question in the future)
Weblate is only the part that allows anyone to edit the translations via the web, and automates the PR process. To actually add a language requires editing the codebase… specifically additions in the project & project include files that are needed to generate the ts files from the code when lupdate is run, and automating the process to generate the binary qm files at build time that are actually used to load the translations. There’s also the flag icon to add, and another bit of code to add the languages to a list that is used by the (dreaded) translationstest.
