Preeti, Kantipur & PCS Nepali: Why You Should Convert to Unicode

A look at why so many old Nepali documents look like scrambled English text, and why converting them to Unicode is worth doing.

If you've ever opened an old Nepali government Word document and seen what looks like random English letters and symbols instead of Devanagari script, you've run into a legacy Nepali font — most commonly Preeti, but also Kantipur and PCS Nepali. Understanding why this happens, and why it's worth fixing, saves a lot of confusion.

How legacy Nepali fonts actually work

Before Unicode support for Devanagari script matured, Nepali typists needed a way to produce Devanagari characters using an ordinary English (QWERTY) keyboard and the character encoding available at the time. The solution: fonts like Preeti simply remapped ordinary Latin letter codes (the same codes used for "a", "b", "c"...) to Devanagari glyphs instead. Typing the letter "d" wouldn't produce the letter d — it would render as a Devanagari character, but only if the Preeti font was applied to that text.

This worked fine as long as everyone involved had the same font installed. The moment that text was opened without the font, copied into an email, searched for online, or opened on a different computer, it reverted to displaying as the underlying (meaningless) Latin characters it was actually encoded as.

The problems this causes

  • It's not searchable. A Preeti-encoded document containing the word "काठमाडौं" doesn't actually contain that text as far as any search engine or Ctrl+F is concerned — it contains the Latin letters that happen to render as that word only with the right font.
  • It's not portable. Open the file on a computer without Preeti installed, or in a modern text field, PDF viewer, or website, and it becomes unreadable gibberish.
  • It breaks copy-paste. Copying Preeti text into WhatsApp, a website, or an email client usually shows scrambled Latin characters, because the receiving application has no reason to apply the Preeti font.
  • It's a dead end for archiving. Government offices with decades of Preeti-encoded documents are sitting on an archive that's effectively unreadable to any modern, font-independent system.

Why Unicode fixes this

Unicode assigns a permanent, universal code point to each Devanagari character, independent of any specific font. A Devanagari "क" typed in Unicode is the character "क" everywhere — searchable, copy-pasteable, readable on any device or browser, and archivable without worrying about font availability decades from now. Nearly every modern application, phone keyboard, and website supports Unicode Devanagari natively.

Converting is a one-way improvement, not a translation

Converting Preeti, Kantipur, or PCS Nepali text to Unicode isn't a translation or a guess — it's a direct decode. Each of these fonts has an exact, known mapping between its Latin character codes and the Devanagari glyphs they were designed to display, plus a set of reordering rules for vowel signs that get typed before the consonant they visually attach after. Applying that mapping in reverse recovers the original intended Devanagari text exactly, whether it's a single sentence or an entire Word document with tables and formatting intact.

Try it yourself

Convert text directly with the Preeti to Unicode converter, Kantipur to Unicode converter, or PCS Nepali to Unicode converter, or convert a whole Word document at once with the DOCX Preeti/Kantipur/PCS to Unicode converter, which preserves your original formatting, tables, and headers.