Documenting OpenType shaping

Nathan Willis
Posts: 10
Hi everyone,
The past few months, I've been working on a set of
specification-like documents that describe how OpenType Layout works in practice,
specifically for shaping complex scripts. It's not quite complete yet,
but we'd appreciate any and all feedback that the community can provide.The repository is here: https://github.com/n8willis/ opentype-shaping-documents/
As the resident README says, the starting points that we'd currently suggest people look at are
- The Indic scripts, which you can get to from here: https://github.com/n8willis/ opentype-shaping-documents/ blob/master/opentype-shaping- indic-general.md
- The Arabic-and-related scripts (N'Ko, Syriac, Mongolian): https://github.com/n8willis/ opentype-shaping-documents/ blob/master/opentype-shaping- arabic-general.md
- Hangul: https://github.com/n8willis/ opentype-shaping-documents/ blob/master/opentype-shaping- hangul.md
A couple of the others are more-or-less ready for review, although I'm waiting on some question loops to close with people I've privately been pestering with questions. That includes Myanmar and Tibetan.
(I would definitely stay away from the Thai/Lao doc, which is in major churn, and Hebrew, which hopefully lands shortly.)
- The Indic scripts, which you can get to from here: https://github.com/n8willis/
- The Arabic-and-related scripts (N'Ko, Syriac, Mongolian): https://github.com/n8willis/
- Hangul: https://github.com/n8willis/
A couple of the others are more-or-less ready for review, although I'm waiting on some question loops to close with people I've privately been pestering with questions. That includes Myanmar and Tibetan.
(I would definitely stay away from the Thai/Lao doc, which is in major churn, and Hebrew, which hopefully lands shortly.)
This is intended to be useful for people working on software support for OpenType shaping, as a bit of a bridge between the OTF and Unicode official specs. Whereas, for instance, the Microsoft Script-development specs are (in general) targeted more towards designers. It pulls together info from HarfBuzz, some Uniscribe (often via test reports), and me dissecting a lot of font binaries for better or worse.
In any case, all eyes are welcome and, if you see anything wrong, missing, or unclear — in the text or in the images, for that matter — please open an issue, a pull request, or just reply directly.
Your feedback and help is appreciated!
2
Categories
- All Categories
- 46 Introductions
- 3.9K Typeface Design
- 485 Type Design Critiques
- 560 Type Design Software
- 1.1K Type Design Technique & Theory
- 653 Type Business
- 848 Font Technology
- 29 Punchcutting
- 519 Typography
- 119 Type Education
- 323 Type History
- 77 Type Resources
- 111 Lettering and Calligraphy
- 32 Lettering Critiques
- 79 Lettering Technique & Theory
- 548 Announcements
- 90 Events
- 114 Job Postings
- 170 Type Releases
- 173 Miscellaneous News
- 276 About TypeDrawers
- 54 TypeDrawers Announcements
- 120 Suggestions and Bug Reports