Unicode to Chanakya: How to Convert Hindi for PageMaker, Newspapers, and DTP

When Hindi turns into gibberish

You copy a Hindi paragraph from a website, WhatsApp, or a Word file, paste it into a PageMaker or CorelDraw template, and it collapses into a string of random English letters and symbols. The text read perfectly a moment ago. Nothing is actually broken — the document uses a Chanakya font, while your text is Unicode (Mangal), and the two speak different languages at the byte level.

This is a daily headache in newspaper offices and DTP shops across North India. Decades of page layouts, advertisement templates, and press archives were built on Walkman Chanakya, and you cannot migrate them overnight just because the source text now arrives in Unicode.

The problem runs deeper than a character swap

The trouble goes well beyond swapping one letter for another. Devanagari has a short-i vowel sign, ि, that Unicode stores after its consonant but Chanakya types before it. There is also the रेफ — a half "र" that rides above a later consonant — which Chanakya places after the whole cluster, not before it.

A naive find-and-replace tool ignores both rules. It scatters vowel signs and reph marks into the wrong slots and produces broken conjuncts in the middle of otherwise readable words. The output looks almost right, which is more dangerous than looking obviously wrong, because the errors slip straight past a quick proof.

The reliable fix is a converter that maps every character and then repositions ि and the रेफ exactly the way the Chanakya keyboard expects. You can convert Unicode Hindi to Chanakya with correct ि and reph handling in your browser, then copy the result and paste it straight into your layout.

What Chanakya font actually is

Walkman Chanakya is a legacy 8-bit font. Instead of mapping Hindi to Unicode code points, it maps each Devanagari glyph onto an ordinary Roman keyboard key. The letter "क" lives on the same key that draws d, a matra sits on another key, and so on. Chanakya text is really ASCII wearing a Devanagari costume, which is why it shows as English until you apply the font.

Why Unicode text fails in PageMaker

PageMaker, CorelDraw, and similar tools draw whatever bytes you give them using the assigned font. When you paste Unicode (Mangal) text into a Chanakya text frame, the software renders the Chanakya glyph that happens to sit at each Unicode byte value. That mapping is meaningless, so you get noise. The encodings never line up — one is a modern standard, the other a 1990s keyboard layout frozen into a font.

The ि reposition problem, in plain terms

In written order, "कि" is consonant-then-vowel, and Unicode follows pronunciation: it stores क first, then ि. Chanakya follows the old typewriter habit and expects the ि key pressed first, sitting to the left of the consonant.

A correct converter detects the ि (it becomes f in Chanakya) and physically moves it in front of the consonant it belongs to. Skip this step and every short-i syllable lands backwards.

The रेफ reposition problem

A रेफ is a "र" carrying a virama that leans on the following consonant, as in "कर्म". Unicode writes र, then the virama, then the consonant. Chanakya instead types the base consonant and adds a reph mark (Z) after the whole cluster. The converter has to spot that र-plus-virama pattern, drop it from its original spot, and re-emit the reph after the consonant it covers.

901, 902, and 905

All three Walkman Chanakya builds share one keyboard layout, so the same converted text drops cleanly into any of them. The version numbers mark refinements to glyph styling, not new encodings, which is why you rarely need to worry about choosing the "wrong" one.

Who still relies on Chanakya

Major Hindi dailies such as Rajasthan Patrika and Dainik Bhaskar built their composing rooms around Chanakya, and countless district presses, wedding-card designers, and government Rajbhasha offices followed their lead. That huge installed base is exactly why Chanakya refuses to die even in a Unicode world.

It works for Marathi, Sanskrit, and Nepali too

Because Marathi, Sanskrit, and Nepali all use the same Devanagari script, the same mapping converts them without any special handling. Conjunct-heavy Sanskrit benefits the most, since conjunct-aware matching and reph repositioning are precisely where simpler tools fall apart.

Going the other way

The reverse trip matters just as much. When you need to lift old Chanakya press copy onto a website or send it over WhatsApp, you convert Chanakya back to Unicode so modern phones and browsers can read it. The same ि and रेफ rules simply run in reverse.

One closing note on the font itself: this kind of converter is an independent utility. It is not affiliated with or endorsed by the owners of Walkman Chanakya, and you must obtain the font through lawful means to view the converted output correctly.