Re: unicode is a fail

Path	csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From	Mark Carroll <mtbc@bcs.org>
Newsgroups	comp.programming
Subject	Re: unicode is a fail
Date	Wed, 02 Dec 2015 16:32:18 +0000
Organization	none
Lines	11
Message-ID	<87h9k0stf1.fsf@ixod.org> (permalink)
References	<4466b45b-1a0a-4b55-8d60-c8bee032b294@googlegroups.com> <87vb8i83oq.fsf@ixod.org> <6a401998-fed6-4dd9-ac7f-4778e47cf8ff@googlegroups.com>
Mime-Version	1.0
Content-Type	text/plain
Injection-Info	mx02.eternal-september.org; posting-host="1b3e5cba9e4d07a53741e6f3d1717925"; logging-data="8424"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19ft+z9i+WXR0z3V3JvYAi/"
User-Agent	Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)
Cancel-Lock	sha1:6bCZmJ2xfDTtke0A2+lKcB2R+QU= sha1:YC+yrpR25h+7jGYVH1SpcTevmUU=
Xref	csiph.com comp.programming:6001

Show key headers only | View raw

On 02 Dec 2015, fir wrote:
(snip)
> i think general convention of using utf-32 everywhere could repair this mess
> maybe though 1) some maybe can see this crazy as utf-32 is probably now least
> used 2) im not sure (if utf-32 is as simple as it should i mean one letter is
> one 32-bit int in memory and no other things do occur)

If one's typically working with text that ISO-8859 could handle,
UTF-32 is a fairly wasteful way of storing such text.

-- Mark

Thread

unicode is a fail fir <profesor.fir@gmail.com> - 2015-12-01 08:34 -0800
  Re: unicode is a fail Mark Carroll <mtbc@bcs.org> - 2015-12-01 17:43 +0000
    Re: unicode is a fail fir <profesor.fir@gmail.com> - 2015-12-02 08:00 -0800
      Re: unicode is a fail Mark Carroll <mtbc@bcs.org> - 2015-12-02 16:32 +0000
        Re: unicode is a fail fir <profesor.fir@gmail.com> - 2015-12-02 09:53 -0800

csiph-web