-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Style all button names in text messages so they look like buttons #5271
Comments
This may be problematic for translations in some language because the correct form of some words can depend on the context. Placeholders are unavoidable when using e.g. the player's name or when there is too many possible options, but they have limitations. There are already tools available in the translation platform that allow conscientious translators to ensure consistency. |
Here are the strings with "press":
And more with "pressing"/"pressed"/"keypresses":
|
Can you give an example of a action like "Fire" not being called "Fire" where the user is told to push the button for that action? Which tools? |
Currently this is how an action/button name like 'Select' in the following string is being translated.
Since ' and ' is part of the string given to translators they are able to change the styling.
In one language <%s> is changed to «%s». The string "Press fire to start the tutorial" have no styling but some translators decide to make they own styling of the word fire like:
|
It would be nice if in all strings that contain button names (that the user is told to press) is styled like a keyboard key/game pad button and not just appear as the rest of the text or with quotation around it.
Here are some current examples:
The placeholder %s is turned into e.g. Backspace or Up and looks like the text around it. No special styling.
I suggest using placeholders like %s instead of "fire" and "Select" so the button names are consistent everywhere and only have to be translated one time removing the chance that the button name is translated differently in different strings.
And not use < and > around the placeholders. But rather have the placeholder contain all styling for the button.
If currently it is too difficult to make the button names styled so they look like buttons/keys at least make them bold so they appear different than the sorrounding text.
Since the new styling would make it clear to the user it's a button we are talking about the "the ... button" can be removed:
Currently:
The future maybe:
The text was updated successfully, but these errors were encountered: