From: Victor Nazarov <vir@comtv.ru>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] strangely typed functions in standard library
Date: Fri, 19 May 2006 17:03:19 +0400 [thread overview]
Message-ID: <446DC217.7080201@comtv.ru> (raw)
In-Reply-To: <7871fcf50605190543g36e65966r90f938c9e8b1478d@mail.gmail.com>
Joel Salomon wrote:
> On 5/18/06, Bruce Ellis <bruce.ellis@gmail.com> wrote:
>
>> 32 bit unicode is not Rune friendly
>
>
> The "other" standard, ISO 10646, has promised that 21 bits will always
> be sufficient to represent characters.
>
> Making Rune a 32 bit type allows all characters to be represented and
> leaves room for out-of-band information; for example, the end of a
> utf8 text stream (EOF) can be (Rune32)-1, with no need for a wider
> type.
>
> --Joel
Oh, I think it is resonable. I thought that ISO10656 is 32 bit, so EOF
detection
and so on will break expanding Rune to 32 bit...
Composing seems to me a better solution than encoding everything to one
alphabet. I mean sorting, transformations and so on (convertion to ASCII
at least).
But I really not competent in this question.
--
Victor
next prev parent reply other threads:[~2006-05-19 13:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 3:06 erik quanstrom
2006-05-18 9:21 ` Bruce Ellis
2006-05-19 4:43 ` quanstro
2006-05-19 5:03 ` geoff
2006-05-19 12:43 ` Joel Salomon
2006-05-19 13:03 ` Victor Nazarov [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-16 3:03 Matt Stewart
2006-05-16 11:40 ` Martin Neubauer
2006-05-16 15:09 ` R
2006-05-19 22:49 ` Lluís Batlle i Rossell
2006-05-19 22:43 ` quanstro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=446DC217.7080201@comtv.ru \
--to=vir@comtv.ru \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).