Re: Allocation of Georgian Extended block

From: Kenneth Whistler (kenw@sybase.com)
Date: Wed Mar 12 2003 - 20:55:00 EST

  • Next message: John Cowan: "Re: Allocation of Georgian Extended block"

    The reason is that the Myanmar block was given four empty columns
    because we already *know* of numerous characters that will need
    to be added to the Myanmar script to support Shan, Karen, Mon,
    and other minority languages written with the script. Ending the
    Myanmar block at U+109F (instead of U+105F) was done very
    deliberately, after doing an approximate census of what remained
    to be encoded for Myanmar.

    Starting any possible Georgian extensions in that space, in order to
    keep Georgian contiguous, would end up just making Myanmar
    extensions be noncontiguous in turn. It would also require
    redefining both blocks, which is not a good idea at this point.
    And finally, we try to avoid *starting* a block across a
    XX7F/xx80 divide, for implementation reasons.

    --Ken

    > I noticed that a new Georgian Extended block was tentatively allocated at
    > 2D00. The Myanmar block ends with four empty columns, just before the
    > Georgian block, and the space could conceivably be used to extend the Georgian
    > block while keeping it contiguous. I am sure there are good reasons for the
    > proposed allocation, but am curious which ones.
    >
    > Thank you,
    > Laurentiu
    >
    >



    This archive was generated by hypermail 2.1.5 : Wed Mar 12 2003 - 21:39:07 EST