Use legacy output only when a workflow requires it

Unicode is the better storage format for modern Sinhala text. DL-Manel conversion exists for compatibility with older publishing, document or template systems that still expect legacy character codes.

Keep the Unicode original. A legacy copy should be treated as an export for a specific compatibility need rather than the authoritative version of the text.

Display depends on the matching legacy font

DL-Manel encoded output can look like Latin letters or symbols when the DL-Manel font is not applied. That is expected because the output intentionally uses legacy character positions.

Check complex Sinhala sequences

Legacy encodings have their own rules for conjuncts, vowel signs and special sequences. Review names and complex clusters in the destination application before final production.

A compatibility export, not a replacement for Unicode

Converting Unicode to DL-Manel intentionally gives up some of the portability benefits of Unicode. The result is useful only when a legacy template, print workflow or archive process expects DL-Manel character positions. Keep the reviewed Unicode text beside the export.

If the destination system is being modernized, prefer changing that system to accept Unicode rather than repeatedly converting new content back into a legacy encoding.

How to use the DL-Manel output safely

Paste the output into the specific legacy application and apply the expected DL-Manel font. Compare the rendered text with the Unicode source. Test punctuation, numerals, conjuncts and words that use less common vowel combinations before exporting a final file.

If the output will pass through another program, verify that program does not normalize, smart-replace or reinterpret the legacy characters. Those transformations can damage a legacy encoding even though they are harmless for ordinary Latin text.

Round-trip checking can reveal mapping problems

A practical QA method is to convert a short Unicode sample to DL-Manel, then convert the resulting legacy text back to Unicode. The round-tripped text should match the intended source for the sequences supported by the mapping. Any difference deserves manual review before bulk conversion.

Mixed Unicode and legacy text needs manual separation

Some old documents contain Sinhala legacy text beside genuine English, numbers or newer Unicode passages. A converter cannot always infer those boundaries from the copied characters alone. If the source mixes encodings, identify the DL-Manel segments first and convert only those segments.

This matters especially when a document has been edited over many years. A paragraph may look visually consistent because fonts hide the underlying encoding differences, while copy and paste reveals several incompatible character systems.

Technical references

Standards and references

For deeper technical context, these external references explain the Unicode standard or the legacy-conversion background used by this workflow.

Quick answers

Frequently asked questions

Why would I convert Unicode back to a legacy font?

Some older templates and publishing systems still require legacy encoded text. For modern storage and web use, Unicode should normally remain the master format.

Why does the output look like English characters?

Legacy font encodings reuse non-Sinhala character positions. Apply the matching DL-Manel font in the target legacy application to display the intended glyphs.

Should I delete the Unicode original?

No. Keep the Unicode text as the portable master copy and use the legacy output only where required.