What to include in a conversion report
Most messages we get are about a Telugu character that came out wrong. Those are the useful ones, and they are much faster to fix when the message contains four things.
- The Telugu you typed in, pasted as text rather than described. A screenshot cannot be run back through the converter.
- What came out, again as pasted text. The Anu bytes matter even when they look like nonsense — that string is what identifies the wrong mapping.
- What you expected instead, if you know.
- Which version you had selected, Anu 6 or Anu 7, and which font is applied in your layout.
Roughly 13% of the mapping table is compiled from sources that disagreed with each other, and those forms are the ones most likely to be wrong. A single input and output pair is usually enough for us to correct the table. See how the mapping data was built for what we checked and what we could not.
Answers you may not need to write in for
- Text shows as boxes or Latin letters — the five common conversion problems covers the cause of each.
- Unsure which Anu version a file uses — Anu 6 vs Anu 7 has a checker that identifies it from a pasted sample.
- Looking up one character's byte value — the full mapping table is searchable across all 684 forms.
- Legacy Telugu software showing wrong characters on Windows — the system locale guide walks through the setting.
What we do with your message
Messages reach us by email and nothing else. We do not add you to a mailing list, and the text you convert in the converter is never sent anywhere — it is processed entirely in your browser, as described in our privacy policy.