India’s scripts are living design systems: elegant, expressive, and deeply shaped by how syllables work. This opener is written for general readers and for type designers who want practical guidance.
India is home to many living scripts used daily in education, publishing, signage, identity documents,
and user interfaces. Typography isn’t decoration—it directly affects readability, trust, and access.
2) The family story (without heavy linguistics)
Many scripts used in India share broad historical roots often described as “Brahmi-derived.”
This does not mean they look alike. It means they often share a similar logic for building syllables:
a base consonant plus vowel signs and other marks.
There are important neighbors and exceptions. Urdu uses the Arabic script tradition (right-to-left),
and modern scripts like Ol Chiki and Meitei Mayek have distinct design logic. This series treats each script
on its own terms while highlighting shared patterns.
3) The big idea: syllable-centric writing (“abugida”)
In many Indic scripts, a consonant letter often includes an “inherent vowel” unless changed.
Vowel signs may attach before/after/above/below the consonant. Additional marks can modify the sound or spelling.
For designers, this is the key shift from Latin: you aren’t just drawing isolated letters—you are building
a combining system that a shaping engine composes into syllable clusters.
4) What makes Indic typography different from Latin
Shaping & conjuncts: clusters may form half-forms, stacks, or ligatures (script-dependent).
Reordering: parts of a syllable may move visually around the base glyph.
Marks & anchors: mark placement is a quality signal; anchors must be stable and consistent.
Rendering engines: HarfBuzz/Uniscribe/CoreText interpret your font; testing across apps matters.
Shaping & conjuncts
Some scripts form conjuncts (cluster forms) that may involve half-forms, stacked shapes, or ligatures.
Reordering
Parts of a syllable can appear visually before/above/below the base even when encoded after it.
Marks & anchors
Mark positioning is a core quality marker: stable anchors, collision avoidance, and consistent zones.
Rendering engines
Your font is interpreted by shapers (e.g., HarfBuzz/Uniscribe/CoreText). Testing matters.
Design takeaway
A “complete” glyph set isn’t enough. If marks don’t anchor well or shaping rules aren’t covered,
readers will see broken text—even if your letterforms are beautiful.
5) A map of scripts used in India (series menu)
This series will begin with major living scripts (Devanagari, Bengali, Gujarati, Gurmukhi, Odia, Tamil, Telugu,
Kannada, Malayalam), then expand to Northeast scripts (Meitei Mayek, Ol Chiki, etc.) and optional historic scripts.
Devanagari
Core
Headline, rich conjunct system, major languages and classical texts.
Rounded systems with complex combining behavior and collisions to manage.
Emphasis: bowls, anchors, text-size robustness.
Series note
We’ll also cover Gujarati, Gurmukhi, Odia, key Northeast scripts (e.g., Meitei Mayek, Ol Chiki),
and optional historic/legacy scripts for scholarly and display use.
6) The designer’s lens
Separate these ideas: Unicode (encoded characters), glyphs (your drawings), and orthography
(language spelling conventions). In Indic, “coverage” is not enough—your font must shape reliably.
A font can “have the characters” but still fail in real text if marks don’t attach, conjuncts don’t form,
or language-specific forms aren’t handled. In Indic scripts, quality is often revealed by clusters,
not by isolated letters.
Most Indic fonts rely on these essentials:
ccmp (composition),
locl (language forms),
mark + mkmk (mark attachment).
Script-specific features come next—and each script article will name them explicitly.
Unicode vs glyphs: a font can contain characters but fail on real clusters.
Minimum OT toolkit:ccmp, locl, mark, mkmk.
7) Common cross-script pitfalls
Weak or inconsistent anchors (marks float/collide).
Missing common clusters/conjuncts (text breaks in real words).
Over-tight spacing (clusters become muddy at text sizes).
Not testing across platforms and apps (different shaping engines).
Weak anchors
Marks drift, collide, or stack unpredictably across sizes and weights.
Missing “hard” clusters
Some syllables look fine, but real text breaks on common conjunct/mark combinations.
Over-tight spacing
Cluster collisions increase; word shapes get muddy at text sizes.
Not testing widely
A font that works in one app can fail in another due to different shapers.
Practical rule
Don’t trust single-word tests. Always test clusters, mixed marks, and real phrases across platforms.
8) How to use this series
Read this introduction for shared concepts.
Pick a script article and follow the same headings.
Use the Designer Starter Kit to plan coverage, then validate with the Test Pack.
Read this article once to learn the shared concepts: syllables, marks, reordering, shaping engines.
Pick your target script article (e.g., Devanagari, Bengali, Tamil) and follow the same headings each time.
Use the Designer Starter Kit to plan coverage, then use the Test Pack to validate.
Iterate: expand test strings → fix clusters → retest across apps/OS → repeat.
Best first script
If you’re new: start with Devanagari
It teaches the core shaping concepts clearly (headline, conjunct strategy, dense marks) and builds instincts
that transfer to many other scripts.
9) Starter test pack (generic)
The script-specific articles will include a tailored test pack. For now, always test:
simple CV syllables, marks above/below, double-mark stacks, common conjunct patterns, numerals, and punctuation.
These are conceptual tests you can adapt to each script. In the script-specific articles, you’ll get a tailored pack.
Cluster patterns to include
Simple CV syllables (base + one vowel sign)
Base + top mark, base + bottom mark
Two marks stacking (mark + mark)
Virama/halant behavior (where relevant)
Common conjunct patterns (2-consonant and 3-consonant)
Numerals and punctuation mixed into text
Where to test
Web (Chromium / Firefox / Safari)
Office apps (Windows/macOS)
Adobe apps (InDesign/Illustrator) if relevant to your audience
Mobile (Android/iOS) for UI fonts
At multiple sizes and weights (text + headline)
Sample “generic” stringsReplace with script-specific syllables in each article.
Script-specific shaping features as needed (covered in each script article)
Quality checklist (universal)
No collisions in common clusters · predictable anchors · stable reordering · consistent spacing · tested across shapers.
10) What’s next
Continue with the first script articles. Each one follows the same structure and includes a Fast Facts box,
Designer Starter Kit, and a script-specific Test String Pack.