Skip to content

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

Open
CatSema wants to merge 2 commits into
amidaware:developfrom
CatSema:final/i18n-rollout
Open

CatSema wants to merge 2 commits into
amidaware:developfrom
CatSema:final/i18n-rollout

Conversation

@CatSema

@CatSema CatSema commented Apr 12, 2026

Copy link
Copy Markdown

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

CLAassistant commented Apr 12, 2026

Copy link
Copy Markdown

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

CatSema commented Apr 16, 2026

Copy link
Copy Markdown
Author

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?

@CatSema

CatSema commented Apr 28, 2026

Copy link
Copy Markdown
Author

Hi @wh1te909 !

Do you have any rough ETA for the frontend rework?

@CatSema

CatSema commented Jun 29, 2026

Copy link
Copy Markdown
Author

Hi @wh1te909 , just checking in on this PR.

Is the frontend rewrite still in progress, or should I start rebasing and adapting this PR to the current develop branch?

I’m happy to update it when the frontend changes are ready.

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