[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RE: filename and normalization (was gcc identifiers)
On Wed, Dec 04, 2002 at 05:45:36PM -0600, starner@xxxxxxxxxxx wrote:
> >For that reason, I dont like form D at all. I wonder how much space
> >it would take to represent every possible Jamo-combination, then just
> >do away with combining characters alltogether...
>
> Besides Korean, Arabic and Hebrew both need combining characters, as do
> many, many minor languages (Lakota, Navaho, Sioux, etc.) You're looking
> at least a few hundred characters there.
>
> But that's not your big problem. Both phonetic alphabets (IPA, UPA
> and dictionary phonetic systems, among others) and mathematics make
> liberal use of combining marks. To replace thoses, you'll basically
> need to encode the cross of 30+ combining marks times 31+ combining
> marks times 1200 Latin, Greek and mathematical characters. Be prepared
> to add more, as requests will come pouring in for three or four combining
> marks on a character, or weird combinations under a double combining mark.
Yes, I think combining characters are good for those purposes,
but not for real letters, that are used in real languages.
I think this is how it was thought of in ISO 10646 when the
standard was approved.
Kind regards
keld
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/