Sinhala typing guide
Unicode to FM Converter — FM Abhaya Sinhala Text
Convert the encoding of Sinhala text for an existing FM font workflow. Unicode stores Sinhala characters directly; FM legacy text depends on the matching font to display Sinhala. Changing the font alone does not convert the characters.
Unicode to FM converter
Unicode input and FM output are selected below. Use the swap button for FM to Unicode. Your text stays in the browser during keyboard conversion.
1. Start with the correct source
Paste real Sinhala Unicode into the Unicode input. If the source appears as Latin symbols until you apply a legacy font, choose FM input instead. Keep a copy of the original document and note which font it uses. This converter supports the site’s FM mapping; a different custom legacy font may require another mapping.
2. Copy the FM output
Choose FM as the destination, then copy or download the result. The encoded text can look like Latin characters in a plain-text editor or a Unicode font. That appearance alone is not evidence of a failed conversion: the matching FM font is needed to display its intended Sinhala shapes.
3. Check it in the destination application
Paste the result into the required application, apply the compatible legacy font, and compare it with the Unicode source. Check vowel marks, joined letters, spaces, punctuation, and numbers at the final text size. Do not mix Unicode and FM text in the same passage without keeping their encoding and font requirements clear.
FM Abhaya compatibility
FM Abhaya is a common reason for requesting Unicode-to-FM conversion. Use FM output only when your receiving workflow uses a compatible FM mapping. This page does not distribute FM Abhaya or grant a licence to that font. Follow the font owner’s terms and verify a short sample before converting a whole document.
Convert FM back to Unicode
Select FM input and Unicode output, or use the swap button after checking the result. Copy Unicode into modern web, email, and document workflows. Retain the original source because unusual glyph conventions and punctuation in a legacy document may need manual correction.
A verified encoding example
| Unicode source | FM-encoded result | Converted back to Unicode |
|---|---|---|
| මම අපි | uu wms | මම අපි |
This example was checked against MyFonts.lk’s conversion engine. It demonstrates the stored characters, not the appearance in every legacy font. A successful round trip for one sample does not guarantee that every archived document uses the same mapping.
Fix common conversion problems
- Latin characters after pasting: confirm that FM output was intended, then apply the matching legacy font in the receiving application.
- Wrong Sinhala letters: verify the source encoding and exact font. A Unicode font cannot interpret FM text simply by changing its name.
- Broken punctuation or joined letters: compare the source and converted text character by character; custom legacy fonts can use different conventions.
- Lost source text: preserve the original file and a visual reference before making bulk changes.
Unicode or FM for new work?
Choose Unicode for new websites, searchable documents, email, and editable text that must move between modern applications. Choose FM when an existing recipient or template explicitly requires it. Compare FM and Unicode workflows, prepare Sinhala for Word, or look up Singlish input rules.