Font Preview

Just a hunch, but could you confirm: If you rename the font name from “Tahu!” to just “Tahu”, does it load then?

BR
Johannes

You can try to overwrite the name of the Font in the Fontsampler Fontset used, but I suspect the non-ascii character in the name is invalid and might be causing this issue. I will try to test this a bit more with a custom font myself.

Yep, I can confirm that using a exclamation point in the PostScript font name will fail to render any woff files generated from it.

While fonts should not have characters like that in their official name I might be able to implement a fix for this when tacking another problem that has to do with invalid / duplicate post script font names and style names. That problem is rather high on my list of priorities, so I hope this will receive a fix within the next couple of weeks.

For your specific case I would hope you can either contact the creator of the font to address this, or, if your license or distribution agreement allows it, rename the actual font name to something comprised of valid characters. I know of other users that have used fonts with Persian name tables, but you still require a valid PostScript name for the font, and then you can overwrite the font display name in Fontsampler when adding the font.

I’ll post here once a fix for this issue is available.

Roger, good to hear. I will keep this issue open until there is a more universal solution to such problems.

Thanks for reporting this issue.