Before Unicode became universal (roughly pre-2010), Sinhala computing was chaotic. Different font developers and operating systems used incompatible encoding systems. A document typed using "FMAbhaya" font on Windows 98 might appear as gibberish on a Mac using "Iskoola Pota."
Sinhala 265 emerged as a popular standard among local developers, particularly within the Fontera and Kaputa font families. These fonts allocated specific numeric values (code points) to 265 distinct Sinhala glyphs. When you pressed a key on the keyboard, the computer would look up that number and display the corresponding glyph.
No. Unless you are maintaining a legacy system from 2002, you should never create new documents in Sinhala 265. You are locking your data into a proprietary cage. Always use Unicode Sinhala.
If you have old data in Sinhala 265, convert it immediately. The longer you wait, the harder it will be to find functional conversion tools as operating systems drop support for legacy 8-bit encodings.
| Code | Focus | Level | |------|-------|-------| | Sinhala 150 | Sinhala grammar & composition | First-year | | Sinhala 220 | Classical Sinhala poetry (Sigiri Gee) | Second-year | | Sinhala 265 | Modern prose & criticism | Second/Third-year | | Sinhala 301 | Old Sinhala inscriptions | Third-year |
Since Sinhala 265 is not a standard encoding, you cannot simply "Save As" in Notepad. You need a mapping table.
Recommended Tools:
Despite Unicode’s advantages, legacy systems and documents kept Sinhala 265 relevant for years:
Before Unicode became universal (roughly pre-2010), Sinhala computing was chaotic. Different font developers and operating systems used incompatible encoding systems. A document typed using "FMAbhaya" font on Windows 98 might appear as gibberish on a Mac using "Iskoola Pota."
Sinhala 265 emerged as a popular standard among local developers, particularly within the Fontera and Kaputa font families. These fonts allocated specific numeric values (code points) to 265 distinct Sinhala glyphs. When you pressed a key on the keyboard, the computer would look up that number and display the corresponding glyph.
No. Unless you are maintaining a legacy system from 2002, you should never create new documents in Sinhala 265. You are locking your data into a proprietary cage. Always use Unicode Sinhala.
If you have old data in Sinhala 265, convert it immediately. The longer you wait, the harder it will be to find functional conversion tools as operating systems drop support for legacy 8-bit encodings.
| Code | Focus | Level | |------|-------|-------| | Sinhala 150 | Sinhala grammar & composition | First-year | | Sinhala 220 | Classical Sinhala poetry (Sigiri Gee) | Second-year | | Sinhala 265 | Modern prose & criticism | Second/Third-year | | Sinhala 301 | Old Sinhala inscriptions | Third-year |
Since Sinhala 265 is not a standard encoding, you cannot simply "Save As" in Notepad. You need a mapping table.
Recommended Tools:
Despite Unicode’s advantages, legacy systems and documents kept Sinhala 265 relevant for years: