Conversation
skrashevich
force-pushed
the
ru-translation
branch
from
fdafb31 to
69e9fff
Compare
…istency in Russian language usage
…sistency in Russian language usage
|
@gotnull can you build testflight release and/or apk with the current state of this PR? It's not worth releasing them to the public releases yet |
|
Building a TestFlight + APK from your branch now (1.18.0+127) so you can test the translations on-device. This won't be a public release — just an internal build for you to verify everything looks right in the actual UI. The public 1.19.0+127 that's already live has IT/PT translations + English fallbacks for RU. Once you're happy with the proofreading and mark this ready, I'll merge and cut a proper release. |
|
I don't see a new build in TestFlight :( |
Translations are merged and in the next build. It's sitting in Apple's Beta App Review queue right now (TestFlight), so once they approve it the build will show up for you automatically. Nothing to do on your end, just waiting on Apple. Thanks for the patience! |
|
I'll be deploying a new build for you to test your translations. It will be 1.18.0+128. Apologies for the delay. I had to merge a lot of changes locally. |
…or consistency in Russian language usage
… "узел" with "нода" to maintain terminology consistency - correct various occurrences of "узел" to "нода" across multiple sections to reflect the terminology update
…n Russian language usage
…lations * l10n: Update MQTT & Global Layer translations * l10n: Update Public key, MQTT & 'this node' translations * l10n: Update Edge, SpreadFactor translations * l10n: Update translations of router, repeater, air util, dbm, spread factor, import * l10n: Add new terms related with Global Layer & MQTT
3 participants
In this PR, work is being done on the Russian translation. For now, this is a draft – under no circumstances should it be merged, as there may be factual errors. Once all strings have been proofread by at least two people, the PR will be moved to the ready-to-merge status.
For translators:
look at docs/GLOSSARY_RU.md so we don’t diverge in terminology
Review all lines. Fix errors, blunders, and other rubbish directly within this PR using code suggests
If you fix a term in the Glossary, you MUST write a separate comment in the PR about it to perform an check of the term changes
Resolve #30