Is there an existing issue for this?
Current Behavior
When a custom font resource is given an identifier containing digits in the font name (e.g. FONT_B612_24), the build fails during font generation with the following error:
Exception: Glyph too large! codepoint 9647: 19278 > 512
Renaming the resource identifier to one without digits in the font name (while keeping the same font file and settings) allows the project to build successfully.
Expected Behavior
The build should succeed regardless of whether the font resource identifier contains digits before the trailing font size, or the documentation should specify that such identifiers are unsupported.
Steps To Reproduce
- Add a custom font resource (e.g. B612-Regular.ttf).
- Use a resource identifier containing digits in the font name, for example FONT_B612_24.
- Build the project.
- Observe that the build fails with Glyph too large!.
- Rename the resource identifier to remove the digits from the font name (for example FONT_B_24) without changing any other settings.
- Build the project again.
- Observe that the build succeeds.
Version
cloudpebble
Host OS
N/A
Watch
Pebble Time (Snowy), Pebble 2 Duo (Asterix)
Anything else?
No response
Is there an existing issue for this?
Current Behavior
When a custom font resource is given an identifier containing digits in the font name (e.g. FONT_B612_24), the build fails during font generation with the following error:
Exception: Glyph too large! codepoint 9647: 19278 > 512
Renaming the resource identifier to one without digits in the font name (while keeping the same font file and settings) allows the project to build successfully.
Expected Behavior
The build should succeed regardless of whether the font resource identifier contains digits before the trailing font size, or the documentation should specify that such identifiers are unsupported.
Steps To Reproduce
Version
cloudpebble
Host OS
N/A
Watch
Pebble Time (Snowy), Pebble 2 Duo (Asterix)
Anything else?
No response