Use fluent format for translations #414
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ImUrX
force-pushed
the
fluent-translation
branch
from
89fe317
to
4c8bee3
Compare
|
By the way, this PR will only include the conversion to |
|
The JSONs should get removed when it's merged or right before merging so translators don't get mixed up |
ImUrX
added
Area: GUI
TheDevMinerTV
approved these changes
Dec 21, 2022
Eirenliel
approved these changes
Dec 21, 2022
|
Please work with other translators to move to the new format :firBless: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some languages have to make worse translations because of the current limitation that we use JSONs, I propose using fluent will make translation a lot easier for these languages that have a limitation for such a thing.
The actual issue is that we reuse terms in different sentences and just remaking the key 60 times wont be nice for translators either. There is more info on cases like locative in here.
Namings were changed from
prop.prop-nametoprop-prop_nameas.means an attribute in fluent