Nickez/bb02 lvgl font#1973
Open
NickeZ wants to merge 5 commits into
Open
Conversation
NickeZ
force-pushed
the
nickez/bb02-lvgl-font
branch
from
de01420 to
5c0fd4a
Compare
Add the FreeType-based LVGL font conversion tool and document how BB02 fonts are generated from it.
Add the generated LVGL font data and small uGUI compatibility wrappers used by the BB02 UI migration.
NickeZ
force-pushed
the
nickez/bb02-lvgl-font
branch
2 times, most recently
from
894389d to
1d316e2
Compare
Wire the new LVGL font assets into the firmware, bootloader, simulator bindings, and Rust UI font types, then remove the old uGUI font files.
Use the BB02 default font coverage to decide whether signed messages can be shown as text, and add tests for UTF-8 display and hex fallback.
Pre-truncate displayable message signing text in Rust so the C label component receives a body that already fits within MAX_LABEL_SIZE. This keeps truncation on UTF-8 character boundaries and avoids relying on the label's byte-level fallback truncation for this path.
NickeZ
force-pushed
the
nickez/bb02-lvgl-font
branch
from
1d316e2 to
eab5042
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It should look exactly the same, I even applied our manual fixes to the 9px Arial. You can test unicode characters in message signing. For example, try signing
Zürich.I'm aware that we potentially are truncating utf-8 strings on invalid boundaries. Should an utf-8 aware boundary truncation method be added in this PR, or a followup PR?I'll add a fix scoped only to message signing.This PR adds 249 glyphs to the arial fonts, increases number of glyphs from 94 to 343. For that we pay about 10kB to the firmware size.
I propose that we fix the truncation issues by migrating the label component to rust: #1974