-
Notifications
You must be signed in to change notification settings - Fork 61
localization #2604
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
base: master
Are you sure you want to change the base?
localization #2604
Conversation
| { | ||
| trigger: "manual", | ||
| label: "@effect.name", | ||
| label: game.i18n.localize("WFRP4E.ConditionName.Bleeding"), |
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.
I'm not sure why this is necessary if the effect name itself is localized?
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.
i noticed in some cases, that the effect itself was just "@effect.name". I guess it doesn't matter that much, since those are mostly hidden but i thought about keeping it consistent.
If that's a problem, i will revert
| { | ||
| trigger: "dialog", | ||
| label: "Penalty to all Tests (@effect.name)", | ||
| label: game.i18n.format("WFRP4E.ConditionEffects.PenaltyToAllTests", {effect: game.i18n.localize("WFRP4E.ConditionName.Stunned")}), |
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.
I feel like localizing script labels is a but much, most of them are hardly seen, and if it's necessary could just be replaced by the translation module?
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.
this would require replacement of whole object in the config, which i wanted to avoid in this case. And since there weren't so many - I wanted to keep it simple. but again, its your call - i can remove it.
More localization strings, cleanup and order of en.json, for easier translations/change tracking.