History • 8 min read
Open any modern Urdu website or ebook today and the text renders instantly, correctly shaped, properly justified, indistinguishable in convenience from reading English online. That convenience is recent. For most of the history of Urdu print, getting Nastaliq onto a page at all was a genuinely difficult technical problem, one that shaped how Urdu publishing developed quite differently from Latin-script printing for almost two centuries.
When European-style movable-type printing presses arrived in South Asia in the 18th century, printers immediately ran into a structural mismatch. Movable type works cleanly for scripts like Latin, where each letter has one fixed shape regardless of context. Nastaliq, as covered in our piece on the four forms of every letter, requires letters to change shape and even shift vertically depending on their neighbors, with extensive optical kerning and overlap between adjacent letters. Early attempts to print Urdu using cast movable type, treating each letterform as a fixed, separate piece of metal type the way English printing worked, produced text that was technically readable but looked nothing like proper handwritten Nastaliq: stiff, disconnected, and visually unlike anything readers associated with quality Urdu writing.
The solution that dominated Urdu publishing for well over a century wasn't a typesetting innovation at all, it was a workaround: lithographic printing. Rather than assembling individual letter pieces, a skilled calligrapher would handwrite the entire page exactly as it should appear, in full flowing Nastaliq, on a specially prepared stone or metal plate. That handwritten page was then reproduced photographically or chemically at scale, essentially printing a photocopy of beautiful handwriting rather than attempting to mechanically reconstruct it from component letters. This is why historical Urdu newspapers and books from the 19th and early-to-mid 20th centuries have a distinctly handwritten, calligraphic appearance, because they genuinely were handwritten, just reproduced at print volume rather than copied by hand for each copy. Major Urdu newspapers continued relying on calligraphers (katibs) to hand-letter entire pages well into the 20th century, long after Latin-script newspapers had moved to fully mechanized typesetting.
Phototypesetting systems in the mid-20th century made some progress by photographically combining pre-shaped letter segments, but truly satisfying digital Nastaliq remained elusive for decades. Early computer systems built primarily around Latin-script assumptions had no good mechanism for the contextual glyph substitution Nastaliq genuinely requires, and the software needed to do it well, what eventually became OpenType's complex contextual shaping rules, simply didn't exist yet. Throughout the 1980s and 1990s, many Urdu computing systems either fell back to a simplified, less authentic-looking Nastaliq rendering, or continued relying on scanned calligraphic images for any text requiring genuine visual quality, an awkward middle period where computers could process Urdu text but couldn't yet display it the way readers expected.
The real turning point came with the maturation of OpenType font technology and its contextual substitution and positioning features, which finally gave font designers the tools to encode Nastaliq's complex letter-joining and vertical-shift behavior directly into a font file, the way a katib's hand would naturally produce it. Projects like Nafees Nastaliq in the early 2000s, and later Noto Nastaliq Urdu (the font powering most of the tools on this site), represented genuine breakthroughs: fonts that could render authentic-looking Nastaliq directly from Unicode text input, without requiring a human calligrapher or a scanned image for every piece of text. This is a remarkably recent development. Many people working in Urdu digital publishing today are old enough to remember when this simply wasn't possible.
Understanding this history clarifies why certain things about Urdu digital typography still feel slightly behind equivalent Latin-script tooling, why font selection is more limited, why some software still mishandles Urdu shaping, why certain effects (like automatic kashida justification, covered in our article on kashida) remain inconsistently supported. The gap isn't due to any deficiency in the script itself; it's the residue of a much harder, much later-solved technical problem than the one Latin-script computing faced. Every tool on this site exists only because of that relatively recent OpenType breakthrough, and it's worth appreciating how genuinely difficult a problem this was for the better part of two centuries before it was solved well.