Skip to content

feat(i18n): implement localization foundation (Russian) and phased rollout#49

Open
CatSema wants to merge 1 commit intoamidaware:developfrom
CatSema:final/i18n-rollout
Open

feat(i18n): implement localization foundation (Russian) and phased rollout#49
CatSema wants to merge 1 commit intoamidaware:developfrom
CatSema:final/i18n-rollout

Conversation

@CatSema
Copy link
Copy Markdown

@CatSema CatSema commented Apr 12, 2026

Add Vue I18n infrastructure with a locale registry, browser/system locale detection, user language override in preferences, Quasar language synchronization, modular locale domains, and UI localization across core and high-traffic functional areas.

Also add i18n documentation, validation/check tooling, and related cleanup needed for rollout readiness.

Some hardcoded user-facing strings may still remain in low-traffic paths, but this PR establishes the baseline architecture and workflow for incremental completion.

Screenshot Tactical RMM - 1 Screenshot Tactical RMM - 2 Screenshot Tactical RMM - 3

Notes

AI was used as an assistance tool while preparing this PR.

All proposed changes were reviewed manually and tested in a development/non-production environment before submission.

In addition, a modified internal build that includes this work has already been used on a regular basis within our organization, which helped validate the changes in real-world usage scenarios.

The final PR content was reviewed and adjusted manually before submission.

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Apr 12, 2026

CLA assistant check
All committers have signed the CLA.

@CatSema CatSema force-pushed the final/i18n-rollout branch 3 times, most recently from a0e8853 to 55dad8c Compare April 14, 2026 19:07
Add Vue I18n infrastructure with locale registry, browser/system locale detection, user language override in preferences, Quasar language synchronization, modular locale domains, and broad UI localization across critical and functional modules.

Also include i18n docs/check tooling and cleanup updates needed for rollout readiness. Note: some hardcoded user-facing strings may still remain in low-traffic paths; this establishes the baseline and process for incremental completion.
@wh1te909
Copy link
Copy Markdown
Member

hi, the frontend is undergoing a significant rewrite, so this needs to wait until it’s complete, then be rebased and any merge conflicts resolved.

@CatSema
Copy link
Copy Markdown
Author

CatSema commented Apr 16, 2026

hi, the frontend is undergoing a significant rewrite, so this needs to wait until it’s complete, then be rebased and any merge conflicts resolved.

Understood, thank you. I’ll wait for the frontend changes before adapting this PR further.
Do you have an approximate timeline for when those changes are expected?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants