Closed videosmith closed 9 months ago
Hi @videosmith,
The reason that won't work with any of the following fonts:
is because these fonts are embedded into and loaded from QPrompt's binary executable, instead of loaded from the operating systems' fonts. This was done this way on purpose because embedding fonts into the binary is the only way one can provide access to a consistent set of fonts across all platforms, including platforms which provide no access to system fonts, such as: Android, iOS, and WASM.
While it should be possible to modify the CMakeLists.txt build scripts to use the embedded fonts for Android, iOS, WASM, and Haiku, but not on Windows, Mac, Linux, and FreeBSD, this is something I'd rather avoid because if I allow system fonts to be used for these fonts, I'd be opening the doors to the possibility of inconsistent prompting experiences from one operating system to the next, because of the differences present in variations of the fonts, or when a font that is expected cannot be found.
What I'm trying to say is that it’s not a bug, it’s a feature.
Re-opening. I just realized the fonts are showing under a different name, meaning they should load despite the original still being impossible to override without recompilation. I need to look into why the caps did not display despite the variation having a different name.
Could be some changes I neglected to make when editing copies of the font files. At any rate, I've worked around the issue for myself by repeating the above process with another in my system fonts instead of your embedded ones, then changing the Qprompt script to the other one.
Appears to display as expected.
Bug Description Edited TTF fonts do not display correctly in Qprompt
Steps to Reproduce
Expected behavior Operation should perform the same in Qprompt as Writer.
Screenshots (optional)
![screen](https://github.com/Cuperino/QPrompt/assets/88691671/50490d6c-78eb-42f3-983c-9b07234987a3)
Device information
fonts.zip