Philippe Verdy verdy underscore p at wanadoo dot fr wrote:
Please don't use UTF-8 to encode anything other than Unicode code
points.
As long as I use it internally for intermediate processing, I can do
what I want. For now it is just a convenient way to represent variable
size integers up
As long as you are sure that this will not leak out into the outside
world, you are free to use the UTF-8 mechanism internally to represent
any type of 31-bit data you like, including this private replacement for
allkeys.txt. (You do know about allkeys.txt, don't you? And the fact
that UCA
Philippe Verdy verdy underscore p at wanadoo dot fr wrote:
As I have not determined the correct size of these bitfields, I need
some intermediate solution to pack them a little, and the UTF-8 TES
(not the UTF-8 CES used by Unicode)venient for now, until I change it
to a better encoding, which
Michael Everson writes:
Peter Constable wrote:
I think the TDIL chart is wrong.
It seems reasonable that one should need extra persuasion to take
the word of an American living in Ireland over Indians. (Sorry.)
Isn't there a specific list for Brahmic scripts? ([EMAIL PROTECTED] ???).
Philippe Verdy verdy underscore p at wanadoo dot fr wrote:
I've tried to experiment a collation algorithm to implement UCA by the
same system as used in UCD decompositions, but with added (and
sometimes modified) decompositions. This system creates new code
points needed to represent only
Philippe Verdy [EMAIL PROTECTED] wrote:
I also think that Tibetan issues should be discussed in that list, despite
its composition model is very different from Brahmic scripts of India,
unless there's a specific rapporteur group for it.
There already is a specific list for Tibetan script
6 matches
Mail list logo
