Daphne Preston-Kendal

A while ago in the CommonMark forum someone suggested `"" … ""` for ``, which I still like. I know there’s a policy against double delimiters, but the problem seems...

`` is not italics and `` is not bold. > The <i> [HTML](https://developer.mozilla.org/en-US/docs/Web/HTML) element represents a range of text that is set off from the normal text for some reason,...

This does not implement the continuation marks feature of SRFI 226, if I understand correctly? Is this an inherent limitation of this approach or could they also be added (perhaps...

> What i have found is that using the precomposed glyph ṁ it "just works" in HTML, so presumably the browser is clever enough to compose the glyph. However in...

It would be very cool to have this feature! Especially since Georg already designed the 8pt masters, and intended to make versions up to 40pt, it would be excellent (and...

Perhaps @davelab6 or someone else from @googlefonts could tell us if Google would be willing to fund such work … since OpenType variable fonts were developed on Google's initiative, it...

Looking forward to hearing more, and hoping that this will happen! 🤞

The embedding information is apparently from the [FSType](https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype) metadata. Set to 0 for an open-source font.

Ooookay, adding the `-r` release flag brings up a *lot* of these: - [ ] Characters aren’t hinted (it complains about every one individually) - [ ] "Glyph renaming was...

Oh. It’s actually like that in the original PostScript fonts. Single guillemets are also clobbered and replaced by other ligatures. We don’t appear to have these characters at all in...