From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Wed, 24 Jul 2013 19:55:35 -0400
To: 9fans@9fans.net
Message-ID: <15adcddaacabd54f772b69a24f72945e@brasstown.quanstro.net>
In-Reply-To: <20130724223831.f/7DZAZ/zn9IdHZP3sfBHBfb@dietcurd.local>
References: <201307240259.r6O2xWGj003062@skeeve.com>
	<e2fb870296da3e564ea1eea95700bd08@kw.quanstro.net>
	<20130724223831.f/7DZAZ/zn9IdHZP3sfBHBfb@dietcurd.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] off topic: full unicode support isn't easy
Topicbox-Message-UUID: 6d17784a-ead8-11e9-9d60-3106f5b1d025

On Wed Jul 24 17:39:45 EDT 2013, sdaoden@gmail.com wrote:
> erik quanstrom <quanstro@quanstro.net> wrote:
>  |0.  uncode support isn't binary.  one might reasonably support a subs=
et.
>=20
> But it is not that you are totally against supporting
> decomposition that includes Korean ("Hangul Syllable
> Decomposition", must be performed algorithmically)?
> It's only missing yet.

i wasn't making any statements about particular languages,
or even endorsing supporting a subset.

but consider, file names in plan 9 support a subset of unicode.
they may not contain the codepoints u+00002f (/) or u+000000.
otherwise, a directory could contain the file entry "a/b" or "a/b\0c"
which could lead to confusion.  many file servers expand
the frogs list to include codepoints < or =E2=89=A4 u+00020 (space)
to prevent accidents.

http://xkcd.com/327/

- erik