KrutiDev Showing English Letters Instead of Hindi

You open a document you typed months ago and instead of Hindi you see something like Hkkjr ljdkj ds fu;eksa. It reads like keyboard noise. Before you retype anything: your text is completely intact, every character is exactly where you left it, and this is the legacy font working as designed rather than a file that has gone bad. What follows is why it happens, how to confirm it, and the two ways out.

What you are actually looking at

KrutiDev was built in the 1990s to solve a hard problem. Computers of that era had no reliable way to store Hindi, and keyboards had no Hindi keys. The workaround was clever: leave the storage alone and change only the drawing.

When you press H in KrutiDev, the file stores the ordinary Latin letter H, the same byte a plain English document would store. The font then draws भ in that position instead of the Latin shape. Every letter works this way. The document holds English characters throughout, and the font makes them look like Hindi.

That arrangement holds together as long as the font is present. Remove it, open the file on a machine that never had it, or paste the text somewhere fonts cannot follow, and the disguise drops. You see what was genuinely stored all along.

This is why the text looks like readable Latin rather than empty rectangles. Rectangles mean the characters have no font to draw them. Latin letters mean the characters are Latin, and always were.

Here is the same sentence in both states:

Confirming it is legacy font text

Three checks, any one of which settles it.

Check the font name

Select the affected text and look at the font dropdown in your application. Names like KrutiDev 010, DevLys 010, Chanakya, Shusha, Walkman-Chanakya, or AkrutiDev all indicate legacy encoding. If the name is Mangal, Nirmala UI, Noto Sans Devanagari or Arial Unicode, you have a different problem.

Look at the punctuation density

Legacy Hindi text carries an unusual amount of punctuation mixed into words: semicolons, apostrophes and slashes appear mid-word because those key positions were reassigned to matras and conjunct forms. Ordinary English never clusters punctuation that way.

Change the font temporarily

Select the text and apply KrutiDev 010 from the font list. If the Latin turns into readable Hindi, the match is confirmed. This is a display test only and does not alter what the file stores, so you can undo it safely.

The two ways out

Install the font

Installing KrutiDev makes the document display correctly on that computer. It takes a minute and preserves the file exactly as it is, which matters if you are handing work to a print shop or an office that already runs on KrutiDev.

The limitation is that it fixes one machine. Every recipient needs the same install, and none of it survives a paste into WhatsApp, Gmail, a web form, or a government portal, because those places cannot load a font on your behalf.

Convert to Unicode

Conversion rewrites the underlying characters. Instead of storing the Latin letter H with a font trick on top, the file stores the actual Devanagari character भ, which carries its own permanent code point in the Unicode Devanagari block and which every modern device already knows how to draw. Nothing needs installing, on your machine or anyone else's.

Copy the affected text and run it through the KrutiDev to Unicode converter. Paste the result back and it will hold its shape in email, on the web, in a government portal, and on a phone that has never heard of KrutiDev.

The trade-off is that converted text no longer matches a KrutiDev workflow. If your office or printer expects legacy files, keep the original alongside the converted copy rather than replacing it.

Which font is it, exactly?

KrutiDev is the most common but not the only one, and the distinction matters because each font maps keys differently. Text typed in Chanakya, opened with KrutiDev applied, produces Hindi-looking output that is subtly wrong throughout.

• KrutiDev dominates government offices and typing exams across North India.
• DevLys shares the same Remington key layout and is close enough that files are often mislabelled between the two.
• Chanakya came up through PageMaker and the print trade. Its internal mapping differs enough that copy-paste between it and KrutiDev garbles the result.
• Preeti is the Nepali equivalent, standard across Nepali publishing.

The font name recorded in the document is the reliable answer. Guessing from appearance alone is unreliable, because several of these fonts render similar shapes from different underlying keys.

A related confusion is worth separating out here: people often describe this problem as needing to "translate KrutiDev into English", when what they actually see is English letters already. Those are two different tasks with two different answers, covered on the page about Kruti Dev to English and what conversion versus translation really means.

Edge cases

The document is fine on one PC and Latin on another

The first machine has the font installed and the second does not. Nothing about the file differs between them. Converting to Unicode removes the dependency entirely.

Correct in Word, Latin in the PDF

The PDF was exported without embedding the font. Re-export with font embedding enabled, or convert to Unicode before exporting so embedding stops mattering.

Latin letters in WhatsApp and email

Messaging apps and mail clients cannot install a font for one message. This is the case where conversion is the only real option, and it accounts for most of the traffic to converters.

A website shows Latin instead of Hindi

The page references a legacy font that visitors do not have and the site does not serve as a web font. Storing the content as Unicode is the durable fix and also makes the text searchable, which legacy font content never is.

Some words look right, others do not

A mixed document, typically one where content was pasted in from more than one source. Convert the legacy portions and leave the Unicode ones alone.

If it is not Latin letters

Everything above assumes readable Latin characters. If you are seeing empty rectangles, question marks, or scattered symbols instead, the cause is different and so is the fix. The guide on Hindi text showing boxes or question marks covers how to tell those cases apart, and matters most for question marks, which usually mean the characters were lost rather than merely undrawn.

The rest of the legacy font troubleshooting, including conversion output that comes back malformed, sits in the Hindi font resources index.