Skip to content

Chore/improve locale framework - #14

Draft
chriscross12324 wants to merge 12 commits into
vrtmrz:mainfrom
chriscross12324:chore/improve-locale-framework
Draft

Chore/improve locale framework#14
chriscross12324 wants to merge 12 commits into
vrtmrz:mainfrom
chriscross12324:chore/improve-locale-framework

Conversation

@chriscross12324

Copy link
Copy Markdown

DRAFT
The focus of this PR will be migrating from a single JSON file per language to multiple files per language.

Rather than having a single JSON file hundreds of lines long, this PR will work on migrating to multiple JSON files. This change will improve readability, sorting messages by the settings page they are found in. As a result, this will also improve maintainability.

Current
common/
├─ messagesJson/
│ ├─ de.json
│ ├─ en.json
│ ├─ es.json
│ ├─ ja.json
│ ├─ ko.json
│ ├─ ru.json
│ ├─ zh-tw.json
│ ├─ zh.json

Proposed
common/
├─ locales/
│ ├─ template/
│ │ ├─ actions.json
│ │ ├─ page_getting_started.json
│ │ ├─ page_general.json
│ │ ├─ page_remote.json
│ │ ├─ page_sync.json
│ │ ├─ page_maintenance.json
│ │ ├─ page_about.json
│ ├─ en/
│ ├─ es/
│ ├─ [...]/

@vrtmrz

vrtmrz commented Jul 29, 2026

Copy link
Copy Markdown
Owner

Thank you very much for this contribution.

While preparing v1.0.0, we changed the project boundary: application translations and dialogues now live in the main Self-hosted LiveSync repository, while Commonlib keeps its canonical English service messages and translation-injection boundary. This should make future contributions easier to locate, understand, and merge.

I am sorry to ask for additional work after you prepared this PR. Would you be willing to open a new PR against Self-hosted LiveSync using the current structure? Thank you again for your contribution and patience.

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.

2 participants