[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: UTF-8 curses

To: linux-utf8@nl.linux.org
Subject: Re: UTF-8 curses
From: hpa@transmeta.com (H. Peter Anvin)
Date: 24 Oct 1999 18:44:28 GMT
Copyright: Copyright 1999 H. Peter Anvin - All Rights Reserved
Disclaimer: Not speaking for Transmeta in any way, shape, or form.
Organization: Transmeta Corporation, Santa Clara CA
References: <19991024154556.C564@rano.rano.org> <E11fRD6-0003Uc-00@heaton.cl.cam.ac.uk> <19991024194332.A1707@light.dkuug.dk>
Reply-To: linux-utf8@nl.linux.org
Sender: owner-linux-utf8@nl.linux.org

Followup to:  <19991024194332.A1707@light.dkuug.dk>
By author:    =?iso-8859-1?Q?Keld_J=F8rn_Simonsen?= <keld@dkuug.dk>
In newsgroup: linux.utf8
> 
> I would rather advise: go clean, do not use space that is reserved for
> character coding. UCS4 is 31 bit. You may encounter private-use planes
> that goes beyound the 21 bits. And you may erroneously output
> characters that have bits set in the first 11 bits if you use these for
> character properties.
> 

I would second this recommendation.  The PU planes may be used for
large systematic symbol sets.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/

References:
- UTF-8 curses
  - From: Edmund GRIMLEY EVANS <edmundo@rano.demon.co.uk>
- Re: UTF-8 curses
  - From: Markus Kuhn <Markus.Kuhn@cl.cam.ac.uk>
- Re: UTF-8 curses
  - From: Keld Jørn Simonsen <keld@dkuug.dk>

Prev by Date: Choosing right character representation for i18n issues
Next by Date: Re: Choosing right character representation for i18n issues
Prev by thread: Re: UTF-8 curses
Next by thread: Re: UTF-8 curses
Index(es):
- Date
- Thread