-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Text entities: huge font files don't render properly #1134
Comments
can you give this another try with the latest commit from #1111? it appears to work for me there (although the font takes a little while to load) the characters are also seemingly offset by 1 (c renders as b, 1 renders as 0), not sure if that's expected? |
It indeed works on #1111.
That is not expected. I have no idea how the system works, so I don't know what could be causing this. It works fine with the default limited character set that you get without the |
so the way it works internally is that the artery font reader gives us a list of glyphs, and each one is identified by a "codepoint" which is a uint32. we take the text (a QString) and split it into QChars, which we use to look up Glyphs. so...it could be an actual problem with the original font, or a problem with the arfont |
The original font should be fine, since it works fine with a limited chatset and works fine outside of Overte. Everything else: no idea. I guess we should try the allglyphs option on some other fonts and see what happens. |
I assume I am hitting undocumented limits.
The file I generated is here: https://data.moto9000.moe/nishiki-teki_3.99zhb.arfont
The original font file is here: https://umihotaru.work/
It works fine without using the
-allglyphs
attribute.The text was updated successfully, but these errors were encountered: