Unicode to Kaputa Converter

Kaputa compatibility for older Sinhala workflows

Kaputa is another legacy Sinhala font mapping found in older web and document material. This converter creates legacy output for environments that still expect that mapping.

For websites, databases and new documents, keep using Sinhala Unicode whenever possible.

Why the output may look incorrect without the Kaputa font

Legacy output stores character codes that only display as intended when the matching font maps those positions to Sinhala glyphs. Seeing Latin-looking characters outside that environment does not necessarily mean the conversion failed.

Use round-trip checks for important text

For high-value content, convert a sample to Kaputa in the target software and then back to Unicode with a trusted mapping. Compare the result with the original before processing a large document.

Keep Kaputa output tied to its destination

Kaputa legacy text is most useful as a compatibility export for a known old system. Outside that context, the encoded string can be confusing because ordinary editors may show non-Sinhala characters. Label legacy files clearly so they are not mistaken for damaged Unicode documents.

Migration is easier when Unicode remains the master

If you maintain an old Kaputa-based archive, create and preserve a checked Unicode version before making further edits. Future web, mobile and database work should start from Unicode. Generate Kaputa only when an older template or application still requires it.

Check the target application before bulk conversion

A legacy font file, keyboard layout or publishing template can differ from another version with a similar name. Test several representative words in the exact software that will receive the output. A successful browser conversion is only one part of a reliable legacy workflow.

Kaputa is a character mapping, not simply a visual font choice

Changing a modern Unicode Sinhala font changes appearance while leaving the Unicode code points intact. Kaputa legacy text works differently. Its stored character positions are interpreted through the Kaputa font mapping, so copying the same encoded string into a modern Unicode environment can produce Latin letters, punctuation or unrelated symbols.

This distinction explains why a visual font change cannot reliably replace Unicode-to-Kaputa conversion. The destination system must genuinely require the legacy mapping before you use this output.

Punctuation and mixed-language text deserve separate checks

Legacy Sinhala documents often contain English names, numbers, punctuation and Sinhala text in the same paragraph. A converter can map the Sinhala sequences correctly while the surrounding punctuation or Latin text behaves differently in the old application. Test mixed-content samples before converting a full document.

If an old file uses several fonts in one paragraph, split the source by encoding or font run when possible. One conversion rule cannot safely infer every mixed legacy segment from appearance alone.

A practical migration workflow for old Kaputa material

For a long-term archive, keep a reviewed Unicode master and record which legacy mapping was used for any compatibility export. That makes future migration easier because editors can work from searchable Unicode instead of repeatedly editing opaque Kaputa codes.

When an old template must remain in service, generate the Kaputa copy only at the final compatibility step. This keeps most of the workflow in a portable format and limits the chance of legacy codes being accidentally normalized, re-encoded or pasted into the wrong application.