Adding new client-specific translation strings workflow #30201
-
While recently working on the Skin Editor, I noticed that many of the strings used in its labels and context menus are using hard-coded English text. This is the case for many other client-specific text elements. An example from the Skin Editor interface (language is Italian): Browsing the issues and PRs, I found this comment from smoogipoo saying to use the Roslyn tool to create new translatable keys and the only other documentation I could find is here in osu!'s GitHub wiki, but there is no info on how to add NEW translation keys. I am unsure of the workflow to follow, if it is only the one specified in smoogi's comment of if there is some other procedure (which I know there is for strings shared with osu-web). |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Made an initial writing: https://github.com/ppy/osu/wiki/Localising-the-client#localising-hardcoded-strings |
Beta Was this translation helpful? Give feedback.
Made an initial writing: https://github.com/ppy/osu/wiki/Localising-the-client#localising-hardcoded-strings