Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Firstly I would like to point out that if you remove your topic, I cannot read your reply and see what your problem was after all. Other people that might have a similar problem in future cannot either.

I can add warnings for ascent/descent/linegap not adding up to emSize and duplicate characters - the deal is that specification doesn’t explicitly define how the font should be rendered, and thus implementations can vary by a lot. Most of the existing information in field tooltips comes not from expert typographic knowledge, but from people having informed me that doing something causes specific software to not render the font correctly.

This was the real issue. I was not familiar enough with typography to catch my mistake, so I assumed it was a problem with the program. If it gave a notice for why it did not render the font, I would not report it as an error.

The tool itself doesn’t render anything - it generates a TTF file, converts it to base64, and hands it over to the browser to use. Browsers, unfortunately, do not commonly display any warnings about why the font cannot be loaded and may rely on something else for font loading/rendering as such.

So, there is not much you can do?

Aside of verifying that the inputs are hypothetically correct, not really - even just figuring out whether the browser is rendering the resulting font wrong (let alone why it’s doing that) is problematic.

I will leave this open for others to note.