-
-
Notifications
You must be signed in to change notification settings - Fork 672
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
Unicode font uppercasing issues #3696
Conversation
All summary screens use that. Can it be changed back? |
39ac763
to
2bb40cd
Compare
2bb40cd
to
754b701
Compare
|
|
754b701
to
b9075a1
Compare
b9075a1
to
19a9533
Compare
acbfe3d
to
435babe
Compare
d647341
to
9e239d8
Compare
A lot of diff in fixtures due to many minor changes in languages as described in the previous comment. Also some previous changes were not incorporated into fixtures from #3617 Some UI fixtures were missing for TS3, e.g. some tests of wipe code. |
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.
A few things but otherwise looking very good. T3T1 fixtures are missing.
}, | ||
"T2T1": { | ||
"1_FONT_NORMAL": "font_tthoves_regular_21_cs.json", | ||
"2_FONT_BOLD": "font_tthoves_bold_17_cs.json", | ||
"2_FONT_BOLD": null, |
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 wonder if we should swap 2<->7 for the scenario where newer translation blob is used on old firmware that expects existing font under id 2. (edit: but that would break compatibility on T2B1, never mind)
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.
LGTM, feel free to rebase and merge if CI passes.
The new option allows generation of font glyph definition where both lowercase and uppercase letters are mapped to uppercase glyphs. [no changelog]
[no changelog]
[no changelog]
By default, buttons have uppercased font. The addition is necessary to customize font on info buttons where we need normal font. [no changelog]
[no changelog]
The title previously disappeared after going back and forth. Used in PIN setting and FIDO confirm. [no changelog]
[no changelog]
The change is necessary for future models where titles might not be uppercased. [no changelog]
Updating after UTF-8 uppercasing issue. Only changes for Model T are during language change where it actually fixes a problem. Model R has more changes - especially in show_warning invocation. See PR 3696 for more info. [no changelog]
Probably an omission after pull #3710. Update using ../tests/update_fixtures.py local -r [no changelog]
This commit changes translations strings of ES, FR, CS, DE langs so that they do not use UPPERCASED titles, button labels and other texts. [no changelog]
[no changelog]
[no changelog]
f53f8ab
to
cf5ac3f
Compare
QA OK tested on Czech translation
|
some_text.upper()
calls do not work correctly in languages other than english. This PR adds additionalFont
s which are UPPERCASE only. These fonts are used where appropriate, especially in Titles and Buttons.FONT_BOLD
toFONT_BOLD_UPPER
FONT_NORMAL_UPPER
andFONT_BOLD_UPPER
and use them where appropriateTODO:
_upper
fontses
de
fr
cs