← Blog

Unicode to Anufonts: How Telugu DTP Conversion Actually Works

If you work in Telugu desktop publishing — creating posters, newspapers, books, or marketing materials in Photoshop or CorelDRAW using Anufonts — you have almost certainly run into this problem: you type beautiful Telugu text in Unicode, try to paste it into Photoshop with the Anu7 font applied, and what appears on screen looks like random Latin characters and symbols. Nothing is readable.

This is not a bug in Photoshop. It is not a bug in your font installation. It is a fundamental difference in how Unicode and Anufonts represent Telugu characters — and once you understand it, the solution becomes clear.

The Two Worlds: Unicode and Legacy Encoding

Modern computers represent text using Unicode, a universal standard that assigns a unique number to every character in every writing system on Earth. The Telugu letter "క" is always Unicode code point U+0C15, regardless of what font you use or what operating system you are on. This is the foundation of how the internet and modern applications handle multilingual text.

Anufonts predate Unicode's widespread adoption. When they were designed, there was no universal Telugu encoding standard. Instead, the font creator mapped Telugu glyph shapes to positions in the standard ASCII and extended character range — the same byte positions that normally hold English letters, numbers, and punctuation. The byte value 0x6B (which represents the letter "k" in English) was repurposed to display the Telugu consonant "క" when the Anu7 font is active.

Why Copy-Paste From a Browser Fails

When you copy Telugu text from any modern website or application, your clipboard receives Unicode data. The word "నమస్కారం" is stored as a sequence of Unicode code points: U+0C28, U+0C2E, U+0C38, U+0C4D, U+0C15, U+0C3E, U+0C30, U+0C02.

When you paste this into Photoshop and set the font to Anu7, Photoshop renders each code point using the Anu7 font. But Anu7 has no glyph at position U+0C28 — it was designed for ASCII, not Unicode. Photoshop falls back to displaying whatever glyph happens to be mapped to that character position in the font's internal table, which could be anything from a box to a Latin character.

The result is garbled text that bears no resemblance to what you intended.

The Correct Workflow: cp1252 Encoding

The only reliable solution is to convert your Unicode Telugu text into the specific byte sequence that Anufonts expects — a Windows-1252 (cp1252) encoded file. This is the same encoding that Anufonts was designed to work with.

Here is what the conversion process does, step by step:

1. Parse the Unicode text into syllables — each consonant with its associated vowel sign (matra), halant conjuncts, and standalone vowels.
2. Map each syllable component to its corresponding cp1252 byte value using a glyph mapping table that matches the Anu7 (or Anu6) font file.
3. Handle pre-base matras — vowel signs like "ి" and "ె" that visually appear before the base consonant in Anufonts must be emitted in the byte stream before the base consonant byte.
4. Handle fused glyphs — the i-kara matra ("ి") fuses with most base consonants into a single pre-composed glyph in Anufonts. These require a lookup into a separate fused glyph table.
5. Write the result as a raw byte file with Windows-1252 encoding — not as UTF-8 or UTF-16.

The i-kara Problem: The Most Common Source of Errors

The short "i" vowel sign ("ి", Unicode U+0C3F) deserves special attention because it is the trickiest part of Telugu-to-Anufonts conversion. In Unicode, a Telugu syllable like "కి" (ka + i) is encoded as two separate code points: the consonant "క" (U+0C15) followed by the vowel sign "ి" (U+0C3F).

In Anufonts, this syllable is handled differently depending on whether the font has a fused glyph for that consonant-plus-i combination. Anu7 provides a dedicated single glyph for each consonant with i-kara fused together. "కి" in Anu7 is a single byte value 0xA9 — not the separate base consonant byte followed by the matra byte.

The difference between Anu7 and Anu6 is that Anu6 uses 0xA8 for the same fused ka-i glyph, with all fused forms shifted down by one position. This is why converting Anu7 text as if it were Anu6 (or vice versa) produces systematic errors in every syllable that contains an i-kara.

Split Matras: Another Complexity

Several Telugu vowel signs span both before and after the base consonant. The "o" vowel ("ొ") in Unicode is a single combining character (U+0C4A), but in Anufonts it is implemented as two separate byte values: a pre-base component (same as the "e" matra byte) placed before the consonant, and a post-base component (same as the "aa" matra byte) placed after it.

A converter that does not account for this will either produce incorrect output or miss these characters entirely.

Using AksharaTool's Converter

AksharaTool handles all of the above automatically. The converter:

• Tokenises your Unicode input into proper Telugu syllables using a state machine parser
• Applies the correct glyph mapping for Anu7 or Anu6 as selected
• Handles fused i-kara glyphs, split matras, vattu (below-base conjuncts), and special two-consonant clusters like "క్ష" and "జ్ఞ"
• Downloads the result as a genuine cp1252-encoded binary file — not a UTF-8 file with cp1252 content

Why Not Just Use Unicode Telugu Fonts?

If you are building a new workflow today, using a proper Unicode Telugu font — such as Noto Serif Telugu, Mandali, or Ramabhadra — is absolutely the right choice. Modern Unicode fonts work seamlessly with copy-paste across all applications and are the professional standard going forward.

However, Anufonts remain the dominant standard in print DTP across Andhra Pradesh and Telangana, particularly in newspaper production, advertising agencies, and traditional print shops. Enormous libraries of existing work are in Anufonts format. Many print service providers still require Anufonts-compatible files. Until the industry fully transitions to Unicode-native workflows, tools like AksharaTool's converter serve a real and ongoing need.

If you have found this article useful, try the converter directly — it handles all the complexity described above and produces clean, correctly-encoded output in seconds.