Contact
Report a conversion error, suggest a correction, or ask a question about Kruti Dev and Unicode.
Send a message
Messages go directly to the person who maintains this site. A reply usually takes two to three working days, and it is sent to the email address you provide.
Reporting a conversion error
The fastest way to get an error fixed is to make it reproducible. Please include:
- the exact Kruti Dev string that failed (copy it as plain text, not as a screenshot of the rendered font);
- the Hindi text you expected to see;
- the output the converter actually produced;
- which direction you used — Kruti Dev to Unicode, or Unicode to Kruti Dev;
- whether the document was typed in Kruti Dev 010, 011, 016 or something else, if you know.
A small snippet of five to ten characters is usually enough. Longer samples are welcome if the error only appears inside a full sentence, for example when a reph or a conjunct is involved.
What this site cannot do
- Convert a document for you. There is no upload box and no mailbox for files. Open the converter and paste the text itself.
- Supply the Kruti Dev font. Font files are not distributed here; the font page explains where the font should come from and how to install it.
- Guarantee exam or court formatting. Converted text is plain Unicode; page layout, margins and numbering remain the responsibility of whoever prepares the document.
Questions we get most often
Several messages each week ask one of the following, so here are the short answers before you write:
- "My converted text shows boxes or English letters." Kruti Dev is a font, not an encoding. The output needs the font applied to display correctly, and a web page or portal without the font will always show the raw codes. The font page explains installation; the guide also explains why installation does not fix a website.
- "Can you convert my Word file?" No — there is no upload, by design. Select the text inside the document, copy it, paste it into the converter, and paste the result back. Layout, tables and images are untouched by the tool.
- "Do you have the Kruti Dev font for download?" No. The font is not hosted or mirrored here, because unverified copies have unclear licensing. Obtain it from your office, printer or the issuing institute.
- "Will this work with 011 or 016?" Usually, with the occasional wrong glyph. The table is the 010 table; the version page explains the exceptions.
- "Can you add Kruti Dev 055, Chanakya, DevLys or Preeti?" Those are different legacy tables. None of them is supported today, and a request alone does not schedule the work — but it is useful to know which one people actually need.
- "Is the site down?" The converter needs JavaScript and a normal browser. If the page loads but buttons do nothing, try a private window or disable extensions that block scripts; there is no server-side processing that can fail.
Corrections to the guide pages
If a page states something that is wrong about your version or your workflow, that is worth a message even when the converter itself works. Corrections are applied to the page text, dated at the top where relevant, and left visible rather than silently rewritten. Where a correction comes from someone who works with these files daily, credit is given only with permission — otherwise the fix is simply made.
What happens after you send
Messages are read in the order they arrive. A reproducible conversion error is usually the fastest thing to act on, because the fix can be tested against the exact string you send. Feature requests are collected but not promised; this is a one-person project, and the pages are maintained in the same spirit as the converter — a few things done carefully rather than a long list of half-finished tools.
Before you write
Many questions are already answered on the homepage FAQ, the version comparison page and the typing guide. If your question is "why does my file look like English letters", the answer is on the font page — the font is missing, not the text. For how messages and site data are handled, see the privacy policy; for the rules of use, see the terms of use.