Mangal to Kruti Dev Converter

Convert Mangal or Unicode Hindi to Kruti Dev 010 for Word, DTP, and typing tests.

Mangal text (paste/type)
Kruti Dev output

Mangal to Kruti Dev keyboard

Mangal keyboard usually means ordinary Hindi Unicode typing in Word; convert that readable Hindi into Kruti Dev output above for the press.

Mangal
keyboard

Mangal keyboard usually means ordinary Hindi Unicode typing in Word; convert that readable Hindi into Kruti Dev output above for the press. This rehearsal pad is independent of the converter you feed manuscripts into.

Devanagari glyph ASCII keystroke
Rehearsal pad Independent of the converter
q
w
k
h
w
c
g
x
n
t
M
ks
s
~
िf
q
i
j
d
r
p
V
a
e
u
o
y
l
;
'k
Shift

Maintained by and the Unicode2KrutiDev team. The Kruti Dev 010 byte mapping is checked against live PageMaker and CorelDraw frames before it ships.

What mangal to kruti dev means for a press job

In a prepress shop, this conversion means lifting the readable Unicode Hindi a client typed in Word and re-laying it into Kruti Dev 010, the legacy DTP font that decades-old PageMaker, CorelDraw, and government press templates were built around. Mangal is not a separate "format" you paste straight into those frames; it is plain Unicode Devanagari that displays everywhere on its own.

The press frame, however, was set up before Unicode existed, so it reads only the old ASCII byte positions Kruti Dev uses. This page is for the operator at the layout machine: the job is to bridge that gap so a modern manuscript drops cleanly into an old design without re-keying a line. To convert mangal to kruti dev cleanly, the tool rewrites each Unicode code point back to the ASCII byte the press face expects, so the copy slots into the frame on the first try.

Production guide

The prepress pipeline, manuscript to press-ready frame

A client sends Hindi typed in Mangal in Word or Google Docs; the press wants Kruti Dev 010 in an old PageMaker or CorelDraw file. This is the order to follow so the copy lands in the layout without reflowing the page.

Here is the fact that trips up most operators: Mangal is Unicode Hindi. It shipped with Windows as a Unicode Devanagari font and stores every letter as a standard code point in the U+0900–U+097F block, so the consonant "क" lives at U+0915 and renders on any modern machine without a font. Kruti Dev 010 predates that standard; it is a legacy DTP face that puts Devanagari glyphs onto ASCII byte positions, so the same "क" is physically stored as the Latin byte "d".

Swap the font menu in a Mangal document to Kruti Dev and nothing converts: the bytes still say Unicode, the legacy face paints whatever glyph sits at those positions, and you get a frame full of garbage. That is why a font change is never a conversion, and why the press frame needs the bytes rewritten first.

On the floor

Five production stages, in order

  1. Receive the Unicode copy. Take the Mangal or Unicode Hindi exactly as the client sent it, from Word, Google Docs, or an email body, where it already reads correctly without any font applied.
  2. Produce the Kruti Dev 010 output. Paste that copy into the left panel above; the Kruti Dev 010 text appears on the right, ready to lift. Use Copy for MS Word for a layout handoff, or plain Copy for a text frame.
  3. Place it in the layout. In PageMaker, CorelDraw, or your press template, paste into the existing Kruti Dev text frame and apply the exact face the frame already uses, not just any Kruti Dev face.
  4. Proof glyphs and conjuncts. Read the live frame against the client copy: half-letters, the i-matra (कि), reph (र्), and stacked conjuncts like क्ष and ज्ञ are where legacy faces drift.
  5. Export to press. Once the frame proofs clean, export to the PDF or plate file the printer expects, with fonts embedded or outlined so the Kruti Dev face cannot substitute at the RIP.

Because the pass only rewrites the byte mapping and leaves your words alone, you can pour a fresh Unicode manuscript into a layout set in the 1990s without re-keying a single line. The toggle above also exposes Remington and Inscript, the two keystroke layouts most Hindi typing tests and older offices still grade against. A mangal to kruti dev pass is therefore a print-stage step, run once the proofing in Unicode is already signed off.

Mangal Unicode Hindi manuscript on the left and the same copy as Kruti Dev 010 output on the right, ready to place in a legacy press layout
Left: the client's readable Mangal Unicode manuscript. Right: the same copy as Kruti Dev 010, ready to drop into the press frame before you apply the legacy face.

Problems inside layout software, and the fix

Six print-floor failures that appear once converted copy meets an old frame, each with the cause and the fix.

Missing-glyph boxes in PageMaker

Empty tofu boxes in a PageMaker frame mean the converted output is correct but the frame is set to a face that lacks those byte positions, often a plain Latin face left on the frame. Select the pasted run and apply the actual Kruti Dev 010 face the template was built with; the glyphs fill in immediately.

Conjuncts and ligatures split wrong in CorelDraw

CorelDraw can break a stacked conjunct like क्ष, त्र, or ज्ञ across a line or render it as loose half-forms when the legacy face handles ligatures differently from the proof. After placing the text, walk every conjunct in the live frame against the client copy and nudge the affected runs rather than retyping.

Kruti Dev 010 vs 016 mismatch in the template

If the whole frame reads as scrambled Latin even after you applied "a" Kruti Dev face, the byte mapping of 010 does not line up with the variant the template expects, commonly 016. Confirm the exact variant on the printer's spec sheet and apply that precise face name.

Kerning and tracking shift after paste

Legacy faces carry their own metrics, so pasted Kruti Dev copy can sit looser or tighter than the surrounding frame. Reset the run's tracking to the template default and re-apply the paragraph style instead of letting the paste keep its own spacing.

Excel and Word handoff fails to keep the mapping

When copy travels from an Excel sheet or a Word table into the layout, smart-paste can re-encode or auto-correct it. Paste as unformatted text (Ctrl+Shift+V), then apply the Kruti Dev face, so the byte positions reach the frame untouched.

Danda and numerals fall in the wrong slot

The Hindi danda, double danda, and Devanagari digits sit at different byte positions in legacy faces than in Unicode. Proof every sentence end and every number in the frame, because a misplaced danda is easy to miss until the plate is already made.

Encoding references behind this guide

The standards and history checked against when documenting this conversion for print.

Unicode Devanagari code chart

The Unicode Consortium's Devanagari chart (U+0900–U+097F) lists every code point Mangal and other Unicode Hindi faces use, which is the editable side of any mangal to kruti dev job.

Unicode Devanagari chart (unicode.org)

Legacy DTP and the Kruti Dev family

Desktop publishing in the 1980s and 1990s relied on proprietary glyph-on-ASCII font encodings before Unicode. India's press and government work standardised on the Kruti Dev family in that era, which is why those templates still demand a legacy face today.

Desktop publishing on Wikipedia

Mangal and Nirmala UI as Unicode faces

Mangal, and its successor Nirmala UI, are the Unicode Devanagari faces Windows ships, which is why "Mangal text" almost always means ordinary Unicode Hindi rather than a distinct file type.

Devanagari script reference (Wikipedia)

About this mangal to kruti dev converter

Built for the moment a Unicode manuscript has to become press-ready legacy copy.

Main converter hub

The job it solves

This pass takes the Mangal or Unicode Hindi a client typed and produces Kruti Dev 010, the deliverable a print shop, an old PageMaker or CorelDraw template, or a typing-test system grades. The words are untouched; only the byte mapping the legacy frame reads is rebuilt.

Proof before you plate

  • Apply the exact Kruti Dev variant the template uses
  • Walk every conjunct and matra in the live frame
  • Confirm dandas, numerals, and punctuation slots
  • Keep the Unicode master as your editable source

Companion tools for a press job

Most people who land here type "Mangal" but mean ordinary Unicode Hindi from Word or a phone; these pages cover the directions a press job swings between.

Unicode to Krutidev Converter The main hub when the source is any Unicode Hindi, not just Mangal, headed for a Kruti Dev frame. Krutidev to Mangal Converter Pull old Kruti Dev press copy back into readable Unicode Hindi when a client needs an editable Word file.

When the direction reverses mid-job

A press job rarely runs one way. You convert mangal to kruti dev to feed the layout, then often need the legacy copy back as a Unicode master for reprints, archiving, or a web version of the same notice.

Prepress questions on Mangal and Kruti Dev

The questions clients and junior operators ask most on the floor, answered plainly.

Why does the press insist on Kruti Dev when my Word file already looks fine?

Your file looks fine because it is Unicode Hindi, which any modern screen renders on its own. The press template, though, was laid out years ago around Kruti Dev, a legacy face that reads ASCII byte positions, not Unicode code points. The frame literally cannot interpret your bytes, so it shows nothing usable. To convert mangal to kruti dev is to rewrite those bytes into the form the old frame expects, which is why the printer asks for it even though your copy reads perfectly on your own machine.

Is Mangal a kind of Kruti Dev font?

No, they are opposites. Mangal is a Unicode Devanagari face Windows ships, storing each letter as a standard code point, so "Mangal text" is just ordinary Unicode Hindi. Kruti Dev is a pre-Unicode DTP face that parks Devanagari glyphs on ASCII bytes. There is no shared format between them, which is exactly why a font swap fails and a real mapping conversion is needed.

Which Kruti Dev variant should I apply to match my template?

Match the variant the template was originally set in, not whichever Kruti Dev face happens to be installed. This page targets 010, the most common variant, but press and government templates also use 016 and other family members whose byte mappings differ. If the frame reads as scrambled Latin after you apply a Kruti Dev face, you have the wrong variant; check the printer's spec sheet and apply that exact face name.

Will the page reflow after I drop the converted copy into the layout?

It can, because legacy faces carry their own metrics and line breaks differently from a Unicode face. The conversion keeps the text correct, but tracking, line endings, and frame fit may move. Paste into the existing Kruti Dev frame, re-apply the paragraph style so the run takes the template's spacing, and proof the fit before you commit; do not let the paste keep its own formatting.

Why do my stacked conjuncts and matras look wrong in CorelDraw?

Conjuncts like क्ष, त्र, and ज्ञ, plus the i-matra and reph, are where legacy faces drift most, and CorelDraw can split them across a line or render loose half-forms. After placing the text, read each conjunct and matra in the live frame against the client's Unicode copy and adjust only the affected runs. This proofing pass matters more on official copy, names, and addresses than anywhere else.

Can I send the client a website version from the same Kruti Dev file?

Not from the Kruti Dev file. The press file holds glyphs on ASCII bytes, so the web would show Latin junk. Hand the client the Unicode master instead, which already works on sites, email, and phones, or run the legacy copy back through a Kruti Dev to Unicode pass if the master is lost. Always keep the Unicode version as the editable source and treat the Kruti Dev file as a print-only deliverable.

Is the Hindi I paste here kept private?

There is no sign-up and no account, and nothing you paste is stored or shared, so confidential press copy, government drafts, and legal notices stay yours. You convert mangal to kruti dev, copy the result, and leave with no history left behind. Keep your own Unicode master on file for reprints and records, and treat each new job as a clean session.

Should I embed or outline the Kruti Dev font before sending the PDF to the printer?

Outline it for plate output. After a mangal to kruti dev pass, the Kruti Dev face you applied is one of more than a dozen variants in the family, and it must be physically present at the printer's RIP, so a PDF that only references the font risks substitution to a default face that scrambles the glyphs. Embedding the subset works for proofs, but converting the text frames to curves, or outlines, is the safest handoff for a press job, because the glyph shapes then travel inside the file and no font lookup happens at output. Always run one final proof against your Unicode master after outlining, since text becomes uneditable once it is curves.