-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
"pike" is ambiguous #34263
Comments
Just add context to both json files: "name": { "ctxt": "item", "str": "pike" } "name": { "ctxt": "monster", "str": "pike" } |
It needs first updating the c++ code of |
Is it not using |
Yes, and also because they have plural forms so I'll have to add plural support to the translation class. |
Is explicit context declaration instead of it being inferred from the |
It was necessary in #26402 where the same string in the same type of json object needed different translations in different contexts, so I'm doing it this way for consistency. Furthermore, there are thousands of item names. If the context was changed to be inferred from the type, translators would have to re-confirm every translations of these strings. |
Describe the bug
There is a monster named "pike", and there is also a weapon named "pike".
And there is no context to distinguish them, which makes it impossible to create a correct translation for both in most language at the same time.
Steps To Reproduce
Expected behavior
They should have different translation. So they should have different name, or in different context.
Screenshots
N/A
Versions and configuration
Additional context
The weapon "pike" was previously called "awl pike", see #30591
The text was updated successfully, but these errors were encountered: