The experience of rendering Arabic typography and its technical debt(lr0.org)
273 points by bookofjoe 1 day ago | 76 comments
tl;dr: Arabic typography's manuscript tradition justifies text by elongating letter strokes (kashida) rather than stretching word spaces, a system codified by 10th-century calligrapher Ibn Muqla and refined over centuries—but no modern browser implements it, falling back to ugly inter-word spacing. The author walks through the technical debt this creates: broken bidi cursor behavior, three competing digit systems, presentation-form encoding bugs that break search, and OpenType's unused `jstf` table. The entire functional Arabic web rendering stack (HarfBuzz, Amiri font) was built largely by a handful of unpaid volunteers, while browser vendors have contributed essentially nothing to solving justification.
HN Discussion:
  • Empathy for Arabic speakers struggling with broken bidirectional text editing
  • Reflection that English/Latin text complexities are equally arbitrary and taken for granted
  • Appreciation for the article's depth and storytelling about Arabic rendering history
  • Shared frustration with poor RtL support across modern interfaces and devices
  • Pointing out a possible typo or technical clarification in the article