Re: Questions on Myanmar encoding

[Eric Muller]

Thank you very much for your help.


I don't know what you mean third row of Table 10.3.

It is in Unicode 4.0, section 10.3, page 273,  and  you can see it  at: 
<http://www.unicode.org/versions/Unicode4.0.0/ch10.pdf#G24999>

With current model..
1018 102C 1039 101B 1031 102C 1010 102C 101C 1032 0020 1001 1004 1039 200C
1017 1039 101A 102C 1038 => "What you said?"
correct. But it used Space(0020), current rules said to use ZWSP.

Ok.

1021 1013 1031 101B 102D 1000 1014 1039 200C 1012 1031 102C 1039 200C 101C
102C 0020 1042 1048 0020 1042 002C 1040 1040 1040 0020 1000 1030 100A 102E=>
"US$28 2,00 ...?" I think help? 1000 1030 100A 102E 1015 102C
Just one character wrong 1031on third place should be 1012. 

my original: 1021 1013 1031...
your correction: 1021 1013 1012 ...
I am a bit confused, and looking more carefully, my new guess is: 1021 
1019 1031... Apparently, that makes the first word sound like "american".

And there should
be no space between 18 2,00.
ok

1010 102D 101B 1005 1039 1006 102C 1014 1039 200C 1025 101A 1039 101A 102C
1025 1039 200C 1018 102F 102D 1037 0020 2018 1015 1004 1039 200C 1012 102C
1014 102E 2019 0020 101B 1031 102C 1000 1039 200C => " 'PandaNi' for zoo..."
I don't know what red Panda mean but flow is correct just one big mistake
there
is no 1025 1039 200C LetterU Killer. The characters after 1021 to 102A can
not use as character of Killer.
It is 1009 1039 200C. Character 1009 NYA have two glyph. What you see on
Unicode is normal form glyph. Another form glyph is similar, you can say
same, with 1025 U
used only to pressed killer and Character, that have subscript, also another
kind of killer.
I think I understand. Also, I corrected 1018, which should be 101E.

Nice to see you and I'm also wish to change some encoding rules but every
body said TOO LATE.
Just to be clear, I am not proposing any modification to the encoding 
model. At best, I can think of clarifications that could help people 
like me, who have limited knowledge of the script.

In another place in your message, you mention that the current model is 
not optimal for sorting. I am not a specialist of sorting, but this is 
not an entirely unusual situation. It is in general not possible to make 
the encoding model such that it is optimal for all processings 
(rendering, sorting, etc.) You may want to check carefully the UCA, to 
see if and how it can handle proper sorting.

Eric.