You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks, German would be great, and following #13 is the right approach. A few things that will help it go smoothly:
Android: a values-de/strings.xml next to values-zh-rCN. Lint fails the build on any string missing from a translation, so it needs every string in values/strings.xml. The next release adds about 30 new strings, so it's easiest to start once that's out.
Thanks. For the Windows app, the translations are Qt's .ts files, so Qt Linguist works well for them. #17 shows the setup: desktop/app/i18n/nectarlink_<locale>.ts, extracted with lupdate from the QML, and package.ps1 compiles them with lrelease at build time (that part is #16). Both land right after 0.1.4, so a German Windows translation can start from lupdate on top of them.
For Android it's a plain values-de/strings.xml, as in #13. Any editor that handles Android string resources works, and Android Studio's Translations Editor shows which strings are still missing.
#16 and #17 are merged, so main now has the Windows setup: lupdate desktop/app/qml -ts desktop/app/i18n/nectarlink_de.ts makes a German catalogue to start from, and package.ps1 picks it up by itself.
Activity
thtbee commentedon Oct 16, 2026
Thanks, German would be great, and following #13 is the right approach. A few things that will help it go smoothly:
values-de/strings.xmlnext tovalues-zh-rCN. Lint fails the build on any string missing from a translation, so it needs every string invalues/strings.xml. The next release adds about 30 new strings, so it's easiest to start once that's out.Please keep the PR to the strings, and sign off your commits as you did on #12.
jochenkirstaetter commentedon Oct 16, 2026
Hi @thtbee
Sure thing, the sign-off is now standard.
Are you using any tools like Qt Linguist for the translations? I'll keep an eye on the news.
And yes, German localization would be a PR on its own.
Cheers
thtbee commentedon Oct 17, 2026
Thanks. For the Windows app, the translations are Qt's
.tsfiles, so Qt Linguist works well for them. #17 shows the setup:desktop/app/i18n/nectarlink_<locale>.ts, extracted withlupdatefrom the QML, andpackage.ps1compiles them withlreleaseat build time (that part is #16). Both land right after 0.1.4, so a German Windows translation can start fromlupdateon top of them.For Android it's a plain
values-de/strings.xml, as in #13. Any editor that handles Android string resources works, and Android Studio's Translations Editor shows which strings are still missing.thtbee commentedon Oct 17, 2026
#16 and #17 are merged, so main now has the Windows setup:
lupdate desktop/app/qml -ts desktop/app/i18n/nectarlink_de.tsmakes a German catalogue to start from, andpackage.ps1picks it up by itself.jochenkirstaetter commentedon Oct 17, 2026
Hi @thtbee
Great stuff, was just reading through the other issues to get a solid understanding of the tools and workflows involved.
I'm going to branch from
mainand then work through the expressions.Cheers