Results 124 issues of Simon Cozens

Now we have draw_glyph_with_pen this library is no longer a plain wrapper around the Harfbuzz API. I suggest we move uharfbuzz unique functions to a separate Python file where they...

enhancement
help wanted

My harfbuzz is often not like your harfbuzz, so downloading and building a vendor harfbuzz isn't something I want uharfbuzz to do. Obviously it's a good idea for platforms where...

enhancement
help wanted

The attached file will segfault with the C++ compressor, at least on my machine. ``` $ uname -a Darwin upo.lan 18.5.0 Darwin Kernel Version 18.5.0: Mon Mar 11 20:40:32 PDT...

I have some code which serialises a font, and it returns `glyf: {}` because of this: https://github.com/googlefonts/fontations/blob/d4651c5e31e81dbddac66163de66ab7fdf84488c/read-fonts/generated/generated_glyf.rs#L40-L44

## What needs to be checked? fvar instances need to have PostScript name entries. ## Detailed description of the problem Notwithstanding the discussion at #3708 in which @miguelsousa says: >...

New check proposal

According to @verdy-p in https://github.com/notofonts/toto/issues/4#issuecomment-1883660619: > Note that Windows 11 now DOES uses and supports 'dlng' and 'slng' metata in its Settings>Fonts panel. Though there's a bug when it parses...

Check improvement proposal
Five minute fix

## Observed behaviour A font can pass all checks and have no warnings, and still have clipping on Windows. ## Expected behaviour If Windows is going to clip base glyphs...

New check proposal
Severity 5 (Highest)
GF's priority list

fontdiffenator is deliberately aimed at the semantic level - what are the user-facing differences between two font files? However, it's also a good basis for asking structural questions: how does...

I'm not sure what the "glyphs missing" message means. It doesn't seem to mean that the glyphs are missing... ``` $ fontdiffenator -td glyphs -- Nunito2-fontmake.ttf output/test.ttf ... ****glyphs missing:...

I think this is syntactically (but not semantically) valid feature code: ```fea feature foo { lookup bar; } foo; ``` I would expect a *parser* to be able to turn...