Guide10 min readUpdated Jul 2026

KrutiDev, Chanakya, Preeti & Unicode — A Practical Guide

Why legacy Devanagari fonts still matter in 2026, how they actually differ under the hood, and when — and when not — to convert them. Written for office workers, DTP operators, exam candidates, and anyone who's ever pasted Hindi into WhatsApp only to see boxes.

Why This Still Matters

Every year I hear the same story from someone at a Jan Seva Kendra, a Nepali newspaper, or a small-town printing press: "I typed the whole document in KrutiDev, but when I sent it to my client on WhatsApp, they saw only English letters." The instinct is to blame the messenger — the app, the phone, the recipient's setup. But the real culprit is a decades-old design decision about how Devanagari script gets encoded into a font file.

Legacy fonts like KrutiDev, Chanakya, and Preeti solved a hard problem beautifully in the 1990s: how do you type Hindi on an ordinary English keyboard, without any software support? Their answer was elegant. Take a standard ASCII font, but replace each Latin glyph with a Devanagari one. Press d, get क. Press H, get भ. As long as the recipient has the same font installed, the illusion holds and Hindi appears where you typed Latin.

Unicode killed that illusion — and thank goodness it did. But the world didn't reset overnight. Millions of documents, government forms, and typing exams still assume the old system. Understanding which font does what, and when to convert, is what this guide is about.

The Four Fonts, Briefly

KrutiDev

The default of Indian government offices. Built on the Remington keyboard layout — the same layout typists learned on Hindi typewriters. KrutiDev 010 is the standard variant used across CPCT and SSC exams. 020 is a lighter-weight sibling used by some publishers. Both are ASCII-encoded — the KrutiDev to Unicode converter handles either.

Chanakya (Yogesh)

The default of Indian print shops that came of age with PageMaker. Same Remington-family layout, but the internal mapping differs enough from KrutiDev that copy-paste between them produces garbage. If you're inheriting an old PageMaker file, expect Chanakya — the Chanakya to Unicode converter is where legacy print-shop archives usually land first.

Preeti

The default of Nepali publishing. Same design pattern (ASCII glyphs replaced with Devanagari), Nepali-optimized layout. Standard across Kantipur, Himalaya, and Nepali government workflows for over two decades. For online publishing, run it through the Preeti to Unicode converter first.

Unicode (Mangal, Nirmala UI, Noto Sans Devanagari)

The modern approach. Unicode assigns each Devanagari character its own permanent code point in the Devanagari block (U+0900–U+097F). Any font that supports that block — Mangal on Windows, Kohinoor on Mac, Roboto on Android — will render your text correctly. No install ceremony. No email attachments explaining "install this font first."

The single most important fact: Mangal is not a different encoding from Unicode. Mangal is a Unicode font. When people say "convert to Mangal," they mean "convert to Unicode." Nothing changes if you pick a different Unicode font — the underlying characters are identical.

When to Convert (and When Not To)

Convert to Unicode when you're...

Keep the legacy font when you're...

How Conversion Actually Works

A legacy-to-Unicode converter is essentially a lookup table. It walks through each character of your input, finds the matching Unicode Devanagari character, and swaps it. The tricky parts are two-fold.

Multi-character glyphs. KrutiDev uses combinations like 'k for श and fd for कि — a "short-i matra" that's typed before the consonant in KrutiDev but stored after the consonant in Unicode. A naive character-by-character conversion produces broken text. Real converters (this one included) sort mappings by length and post-process the short-i reorder pattern.

Ambiguous mappings. Some legacy characters have context-dependent meanings. A conversion engine has to detect the context or accept a small error rate on edge cases. In practice this affects 1–2% of characters in unusual conjuncts. Manual review catches most.

Practical Workflow Recommendations

For office workers on KrutiDev

Keep typing in KrutiDev if that's your muscle memory — nothing wrong with it. Before sharing externally, run through the KrutiDev → Unicode converter and paste the Unicode version into email, WhatsApp, or the government portal. Keep the KrutiDev version as your working copy.

For DTP operators

If clients keep sending Unicode content but your PageMaker workflow assumes Chanakya, use Unicode → Chanakya. Alternatively, migrate to InDesign with Unicode fonts — the ecosystem finally supports Devanagari properly. Both are valid paths; the migration takes a week of setup and pays back in months of not having font-install headaches.

For Nepali publishers

Preeti still runs most editorial workflows. Convert to Unicode for the web edition and keep Preeti for print. Two masters isn't ideal, but until every operator retrains, it's realistic.

For exam candidates

Install KrutiDev 010, practice with our typing test, and don't worry about Unicode until after your exam. Speed on the required layout matters more than encoding purity.

Common Traps

The "font install" trap. A recipient sees garbled Latin when you send them KrutiDev text. Don't tell them to install a font — convert to Unicode and resend. Their device already has a Unicode Devanagari font.

The "OCR gave me KrutiDev" trap. When you OCR an old scanned page, the output is usually Latin characters that visually match KrutiDev glyphs. Treat the OCR output as KrutiDev and run it through the converter — you'll get Unicode Hindi in one paste.

The "print looks right, web looks wrong" trap. Print rendering uses the exact font you specify. Web rendering falls back to whatever the user's device has. That mismatch is why legacy fonts work on print but break on the web.

Closing

Legacy Devanagari fonts aren't going away — they're deeply embedded in how millions of people already work. The right move isn't to force everyone to Unicode. It's to know when each format applies, and to make the switch effortless when it does. That's what the tools on this site exist for.

Ready to try? Open the KrutiDev converter, or grab a legacy font from our downloads page.