梁海 Liang Hai

I also believe the current patched wording correctly reflects both shapers’ ability and fonts’ usage/expectation of this OTL feature in reality. Shaping stuff other than Bangla vowel signs with automatically...

(Still trying to grasp your attitude towards this issue. I find myself often have difficulty to switch from a font developer’s point of view to a shaper developer’s…) > (a)...

I don’t mind splitting the procedural discussion at https://github.com/w3c/font-text-cg/issues/11 from this. But yeah, if possible, it may be easier for others to keep an eye on if we concentrate on...

> Btw. does anyone in this thread know where the rotated baseline should be for the rotated characters, relative to the vertical center line? It’s a whole pile of hot...

Instead of https://github.com/typemytype/drawbot/issues/440#issuecomment-946148489, simply doing— ```python from .drawBotDrawingTools import _drawBotDrawingTool rect = _drawBotDrawingTool.rect ``` —should be good enough. But why is `from drawBot import _drawBotDrawingTool as db` a problem at...

I’m also affected by this, but have been procrastinating about the bug report… Thanks, OP!

Any progress on this?

Upstream updated: https://github.com/LettError/ufoProcessor/pull/41

Some ideas— For _reph_, as in र्ट: - Systematic name: `deva:rasignabove` (or `deva:rasignabovebaseleading`, depending on how far you want it to be explicit… As above- and pre-base signs seem to...

Because [Hangul Compatibility Jamo block](http://www.unicode.org/charts/PDF/U3130.pdf) (3130..318F) characters (despite the “LETTER” names) are encoding-level special cases of the [Hangul Jamo](https://www.unicode.org/charts/PDF/U1100.pdf) (1100..11FF) characters, they should be named after the corresponding (`unicodedata.normalize("NFKD", character)`)...