Re: Industry Thai Cell-Clustering Rules



Kaixo!

On Fri, Nov 10, 2000 at 12:03:28PM -0800, Chookij Vanatham wrote:

> ] By the way, what is the position of the Wtt2.0 about the SaraAm ambiguity

> Wtt2.0 doesn't say anything about SaraAm. The wtt2.0 cell-clustering rule
> is treating SaraAm as the starting of the cell. Wtt2.0 doesn't say anything
> how SaraAm should be shaped when it is following (1) consonance or

I wasn't talking about shaping or clustering; but about input and text
encoding standardization.
How is the word "water" supposed to be written ?

> In the Thai computer industry, for those window applications which use
> "I-BEAM" type of cursor, like desktop appls, the way they treat SaraAm,
> they treat it as shown below.
> 
> 	(1) Consonance + SaraAm            ----> 1 cluster (2 columns)
> 	(2) Consonance + Tonemark + SaraAm ----> 1 cluster (2 columns)
> 	
> The SaraAm will be displayed as 2 pieces which are Nikhahit (U+0E4D) and
> SaraAA (U+0E32) if it's following the above sequences, (1) and (2).

Which makes sense.

So my question is; should the input standardize SaraAm -> Nikhait + SaraAA
and SaraAm + tonemark --> Nikhait + tonemark + SaraAm ?

> When I was a kid, here is what they taught me how to write SaraAm.

I was not referring to handwritting; but to computer writting; as for
a computer different bytes don't match, even if the visual output is the same

> Don't know who invented SaraAm. Not quite sure if it was from computer
> person who tried to have Thai support in the computer. Then,

>From what I read, it was on old mechanical typewritters; then when computers
started to be used, the keyboard was copied from mechanical typewritters
and a SaraAm key being there, it needed a code in the charset encoding.
It would have been better avoiding it imho.

-- 
Ki ça vos våye bén,
Pablo Saratxaga

http://www.srtxg.easynet.be/		PGP Key available, key ID: 0x8F0E4975




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]