خالد حسني (Khaled Hosny)

Better track individual bugs. If people care enough and want to see them fixed here, they will open issues here.

There are several tools and websites that can give such reports, maintaining this manually gets often outdated. I used to run a tool at build time that generated Unicode charts-like...

If it can be done with no extra dependencies (or something that can be easily installed with `pip`), then I’m fine with it. I don’t like keeping out-of-sync stuff around,...

GNU Make, I never use any other make. FontTools will always be used, standard GNU utils are OK too, Python packages available on PyPI are fine as well (as long...

Pandoc is fine, but it feels like an overkill for such a simple task (I’m not happy for using XeTeX to generate the sample either).

So the original report is very short in details, and I still don’t know what is being requested here. I need simple points that can be easily understood by a...

OK, any samples from fonts doing this right? Is there a definitive list of languages that need this behavior?

Not doing anything here. People who needs this or know what exactly is needed here are free to send pull requests.

Feel free to send a pull request.

Other than meeting some arbitrary (and antiqued) glyph list, what is the use of adding these two legacy code points? They often mask bad input data, forcing fallback font or...