Overall Language of romanized Sinhala pages

I have this message due to a mistaken identity:

    Warning: This document appears to be written in Oromo but the HTML
    start tag has lang="si". Consider using lang="om" (or variant) instead.


The rest here is a harangue that you, looking down at me, might laugh 
out loud. Besides, you cannot help it. But then, who knows, you might 
see my misery and tell others that IT rulers might have compassion for 
the downtrodden in the faraway lands, not even pleasant to look at. I 
apologize for showing my frustration also having to bear the recent sad 
events in my Lanka.

The pages I created at ahangama.com and few other websites mostly in 
2005-6 are in Romanized Sinhala. Therefore, I marked the language as 
"si". The defining set of letters is close to Icelandic. A web font, an 
orthographic smartfont, shows them in the Sinhala native script WITHOUT 
COMPROMISE, unlike Unicode Sinhala that violates Sanskrit orthography. 
(Modern Sinhala is an admixture of pure Sinhala and Sanskrit each having 
its own orthography). Besides, you'll notice that the pages at 
ahangama.com use PHP and Javascript to overcome the backwardness of 
BROWSERS at the time the pages were written.

Surprise: typing romanized Sinhala and Tamil on keyboard layouts, 
slightly altered from QWERTY, is faster than English!
I know that my defining the language as "si" is a problem to you because 
Sinhala has its double-byte Unicode version. We use Orthographic 
smartfonts (OSFs) for Sinhala and Tamil. Further on, we will have OSFs 
for other Indic scripts as well. It seems to me as a necessity to save 
the ancient cultures of South Asia from the Unicode barrier to modern 
communication.

There are many problems with the double-byte Unicode specification for 
the users, and advantages for directors of Unicode Consortium like 
Microsoft. (More than the annual income of a person for each Windows and 
a font -- fonts made by freely copying from letterpress lead fonts). 
Deep at the technical level, double-byte is useless where programs 
evolved in the last four decades have established Single-byte as the 
only acceptable size of a character.

See the arrogance of Unicode pretending to know Indian scripts:
http://ahangama.com/unicode/unicodewrong.htm

Unicode Sinhala needs to be installed on Windows machines as a 
system-altering 'package'. The people mostly use counterfeit Windows and 
therefore can't use that.  (Recall that Microsoft legitimized such 
British systems in 2014. We do not envy the British people as they are 
poor, unlike us).

Please understand that contrary to the expectation by the IT ruling 
class in the West, the literacy rate of  Sri Lankans, is (shockingly) 
96% or somewhere around that. Imagine if their native language is 
English -- they'd happily communicate in it. They won't use English even 
if they can. They had Sinhala traceable back to 6th century BC, about 
1000 years before English happened. (Not bragging as I believe birth is 
only an accident).

How to solve the problem of counterfeit Windows and Unicode Sinhala? 
They instead use an alternative Sinhala method where the underlying text 
is mixed letters and signs -- garbage! Instead, I made this alternative: 
1. romanize the script for phonetic writing, a step better than 
Anglicizing that they are left to do. 2. Then take all the burden of 
shaping letters into a smartfont (skipped work for the obsession, 
falling into poverty).

See: http://www.romanized.club/

Who can approve this given the example of Unicode massacring Indian 
scripts writing irresponsible explanations of its strangeness? Seeing it 
from the point of view of humanity might hurt someone's business, I know.

I do not think you can do anything. I got me cooled down a bit.

Sincerely,

JC Ahangama


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus