Bobby de Vos

11 Followers
24 Following
56 Posts
Adobe InDesign seems to zero the width of a Mn character, even though it is not used in a lookup. This happens with the World Ready Composer, but not HarfBuzz (in or outside of InDesign). Why keep using the World Ready Composer? It seems to handle hyphenation differently than in HarfBuzz is enabled.
SIL uses ttfautohint for our staic Latin fonts, and it really helps with displaying small text on Windows. With a variable build of our Latin fonts, it seems to me that the display of small text is better in Windows, even without hinting the variable font.
Is there any thought of Python bindings for HarfRust, like uharfbuzz for HarfBuzz? If so, and if the Python API was the same, I could test our SIL fonts to see if they shape the same with HarfBuzz and HarfRust.
In particular I use this to see information on script extensions.
Many times when I am looking at Unicode character properties I wish to see information from multiple characters at one so I created a spreadsheet (now updated to Unicode 17 Beta) that allows me to do this https://github.com/silnrsi/unicode-resources/tree/main/ucd-spreadsheet
unicode-resources/ucd-spreadsheet at main · silnrsi/unicode-resources

This is a repository to manage the information related to the SIL use of Unicode - silnrsi/unicode-resources

GitHub
For non-roman fonts WSTech adds CP1252, MacRoman, and various dashes and different widths of spaces. I am intrigued at the various other Latin characters that are needed by some non-roman script such as U+02BC MODIFIER LETTER APOSTROPHE in Bengali and a colon in Tamil script for Saurashtra. I presume I would use U+A789 MODIFIER LETTER COLON
I am appreciating a Font Bakery check that uses a variable font to find issues with glyph interpolation, this has flagged issues in a number of our projects. https://github.com/fonttools/fontbakery/issues/3930
New check: Interpolation issues · Issue #3930 · fonttools/fontbakery

Short (one line) sentence describing what needs to be checked: We can (and therefore should) detect interpolation errors in variable fonts. Detailed description of the problem. It would likely be r...

GitHub
I maitain TECkit (originally written by Jonathan Kew) and was pleased to find that I did not need any code changes to handle the novel normalization in Unicode 16 https://www.unicode.org/review/pri497/pri497-background.html
Alpha Review Background