WIP: russian translation

[skrashevich]

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

[skrashevich]

@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

[gotnull]

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.

[skrashevich]

I don't see a new build in TestFlight :(

[gotnull]

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!

[gotnull]

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.

[gotnull]

Hey @skrashevich 👋 Just checking in - are you still planning to continue with the Russian translation? No rush at all, just want to make sure the PR doesn't go stale. The translations you've done so far are already in main and working great. Let me know if you need anything from my side (updated keys, test builds, etc.) or if you'd prefer I take it from here. Thanks for all the work so far!

[skrashevich]

Hello.
No, just yesterday I restored my Apple developer for more convenient on-site testing

[gotnull]

Hey @skrashevich — this PR has a merge conflict in lib/l10n/app_ru.arb due to keys added/renamed on main since you branched.

What changed on main (since your branch point):

• New keys added (with Russian translations): automationScreenClearLogTitle, automationScreenClearLogMessage, messagingFilterOnline, scannerTipNoOtherApps, scannerTipNoOtherDevices, plus ~60 more new keys across incidents, safety, help, widgets, etc.
• Renames: Active → Online, Inactive → Offline in several node/messaging filter keys
• Value changes: a handful of subtitle text updates

To resolve:

1. Rebase on main: git fetch origin && git rebase origin/main
2. When the conflict appears, keep your translations for keys that exist in both versions
3. Accept the new keys from main (they already have Russian values where we added them)
4. Force push: git push --force-with-lease

The new keys from main were added with English fallbacks or Russian where available — your pass should review/improve them. No rush since this is still draft.

[gotnull]

Hey @skrashevich - just saw the fresh commits come in, thanks for jumping on this!

I'll approve the pending workflows now so CI can run against the merged head, then queue up a TestFlight build with the latest translations for you to verify on-device. Will ping you back here when the build is available.

[skrashevich]

Hey @skrashevich - just saw the fresh commits come in, thanks for jumping on this!

I'll approve the pending workflows now so CI can run against the merged head, then queue up a TestFlight build with the latest translations for you to verify on-device. Will ping you back here when the build is available.

Please pay attention to #102 -- here, it seems, the problem is on your side. For my part, I brought the implementation as close as possible to the reference one.

We need to make friends with it somehow :)

(btw, in telegram @gotnull - is it you? )

[gotnull]

Please pay attention to #102 -- here, it seems, the problem is on your side. For my part, I brought the implementation as close as possible to the reference one.

Let's keep #102 on #102, happy to dig into the proxy-vs-client question there once I've run the TestFlight build against the current proxy head.

This PR thread should stay scoped to the translation changes so review stays clean.