-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Crowdin translations #3274
New Crowdin translations #3274
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very interesting! This is a nice complement to i18n script because it picks up some things that i18n is supposed to be doing for us but isn't.
Nice changes:
- Reordering of keys (not sure why it's happening though given i18n script is being run on all files and that should handle alphabetical ordering)
- JSON formatting/spaces (nice)
- Picked out at least two strings I noticed that were only partially deleted from app (@Duncan-Brain now what's the best way to make these changes to the English? Can those be directly edited in crowdin as well or is that ill-advised? I'm just thinking we don't want translations of these unnecessary strings from our translators)
Good catches that will be depressingly manual work:
- All the mis-formed or accidentally translated keys that delete the translated string 🥲 Surprised that i18n didn't catch and generate the proper keys here though
- Parent key being wrong and all child key strings being deleted
BAD changes:
I don't think we can stop escaping spaces in French.Edit: tested, never mind it's completely fine. It's i18n parser that is putting them in, not something that had been done out of necessity- I don't understand the basis for the deletions in
common.json
, they are legitimate keys, aren't they? - I thought we looked into it and
_many
is language dependent, English being a language that will never have it. I don't know how to fix it because I believe the result of our last investigation was that i18n generates it according to language and omits it (correctly) for English. Probably an issue others have faced though.
@@ -24,14 +24,14 @@ | |||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The i18n script is failing to reorder the keys alphabetically?
First ideas are:
Good
Bad
|
cab7057
to
f86f79e
Compare
@kathyavini Quick updates on the "will look intos" Nice
Bad |
f86f79e
to
365d719
Compare
ad30a21
to
66f8fca
Compare
66f8fca
to
2858676
Compare
New Crowdin pull request with translations