Two Sinhala sentences can look almost identical on screen yet behave very differently when copied, searched, or opened on another computer. One may be Unicode text. The other may depend on FM Abhaya or another legacy font. The right choice depends on what you need to do with the writing, not only which letter shapes you prefer.
For most new writing, choose Unicode. Keep legacy output for situations where a designer, printer, or older document specifically requires it. SinhalaEditor lets you prepare either format from the same Singlish source, so you do not need to guess before trying a short sample.
What Sinhala Unicode means
Unicode assigns characters standard identities. A Sinhala letter remains a Sinhala character when you change between fonts that support it. The font controls its appearance, while the underlying text still represents the same writing.
This is why Unicode is suitable for messages, website text, search, forms, email, and collaborative documents. It gives software a standard character sequence to work with. Good display still depends on the app, font, and shaping support, so Unicode does not mean every old device or every font can show the text correctly.
Unicode also provides a better foundation for accessibility than a custom legacy mapping. Actual pronunciation by a screen reader depends on its Sinhala language and voice support. Do not treat a Unicode label as a guarantee that every assistive tool will read a document well; structure and testing still matter.
What FM Abhaya legacy text means
FM Abhaya uses a different approach. Its Sinhala glyphs occupy character positions associated with Latin letters and symbols. Those characters look like Sinhala only when a matching legacy font displays them. Change the font to an ordinary Latin face and the underlying sequence becomes visible.
For a simple example, the converter's FM output for මම is uu. That is not the original Singlish spelling mama. It is the mapped character sequence the legacy font uses to display the Sinhala shapes.
Legacy text can be appropriate inside an established print workflow. A shop may have templates, older files, and approved font styles built around FM Abhaya. The important point is to keep the mapping and font paired. It is not a portable replacement for Unicode writing.
Choose by the destination
| Task | Practical starting choice | Reason |
|---|---|---|
| WhatsApp or Facebook text | Unicode | Readers should not need your design font. |
| Website article or online form | Unicode | The text needs standard Sinhala characters. |
| New Word or Google Docs document | Unicode | Easier editing and sharing across suitable apps. |
| Modern Photoshop or Illustrator project | Unicode first | Supported fonts and shaping can keep text reusable. |
| Existing FM Abhaya template | Matching legacy output | New text must match the template's mapping. |
| Printer explicitly requests FM Abhaya | Confirm the font, then legacy | Production requirements may depend on that exact setup. |
Do not decide that all design software needs legacy text. Recent Photoshop supports Sinhala through its Unified Text Engine. Illustrator also supports Sinhala with suitable composer settings. A specific old file may still require a legacy route, but that is a file requirement rather than a rule about the whole application.
How to select either format in SinhalaEditor
- Open the Sinhala Unicode and legacy typing tool and type your words in the Singlish box.
- Check the Sinhala spelling before preparing either output. For literal key-mapping tests, switch Suggestions off.
- Keep Unicode on for standard Sinhala characters. The font picker offers Unicode previews, with some system fonts shown only when detected on your device.
- For FM text, turn Unicode off and choose Default (FM Abhaya). For Isiwara, choose that separate option.
- Press Copy, paste into the destination, and apply a font that matches the chosen output.
Changing between Unicode preview fonts does not change the words. Changing from Unicode to a legacy mode does change the character sequence used for output. That is why the switch matters more than a visual resemblance between two font names.
Do not confuse Abhaya Libre with FM Abhaya
Abhaya Libre is a Unicode font. Default (FM Abhaya) is a legacy output option. You cannot copy FM output, apply Abhaya Libre, and expect that step to decode the mapped characters back into Sinhala Unicode.
The same caution applies to Isiwara. Selecting the Isiwara font in a design application does not convert FM Abhaya character sequences into Isiwara sequences. Produce the required output from the source first. The FM Abhaya typing workflow shows the exact sequence for that format.
Check an unfamiliar document without damaging it
Make a copy of the document before experimenting. Select a short Sinhala passage and temporarily change its font to a normal Latin font. If it becomes Latin-looking letters and symbols, it is likely legacy text. Undo the change immediately.
If the passage remains Sinhala through a Unicode-capable font, it is likely Unicode, although font fallback can hide which font is doing the rendering. For a more reliable check, inspect copied text in a plain-text editor with Sinhala support. A single document can also contain both encodings, so test more than one section.
Do not paste old legacy text into the Singlish input expecting a reliable reverse conversion. The verified tool workflow starts from Singlish and produces Unicode or legacy output. If you only have an old FM file, preserve it and arrange a separate, checked migration instead of overwriting the original.
Keep the format useful after delivery
For a new project, retain a Unicode master even if the final design needs FM Abhaya. Save the original Singlish source as well when useful. This gives you text for a future website caption, revised poster, or accessible document without recovering it from a flattened image.
PDF can help preserve appearance, but it does not automatically repair legacy encoding or guarantee searchable Sinhala. Test copying a line from the PDF into a plain text field. If the copied text is wrong, the visual page alone is not proof of reusable text. See the guide to Sinhala text appearing as English letters for diagnosis.
FAQ
Does Unicode mean I never need a Sinhala font?
No. The app still needs a font with Sinhala glyphs and suitable shaping. Many modern systems supply support, but an arbitrary font does not necessarily contain Sinhala.
Which format is better for a searchable website?
Unicode. A legacy font may make a page look Sinhala while leaving search engines and copied text with Latin character sequences.
Can I send both versions to a printer?
Yes, if you label them clearly and confirm which one they will use. Include a checked visual reference and retain the editable source so a later correction is straightforward.