Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3F4FBDDF.85DA1F2B@phekda.freeserve.co.uk>
Date: Fri, 29 Aug 2003 21:55:59 +0100
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: Eli Zaretskii <eliz AT elta DOT co DOT il>
CC: djgpp AT delorie DOT com
Subject: Re: wide character functions
References: <Kq53b.5954$L15 DOT 1502 AT newsfep4-winn DOT server DOT ntli DOT net> <2427-Thu28Aug2003000602+0300-eliz AT elta DOT co DOT il> <Dxj3b.94$c12 DOT 961 AT newsfep4-glfd DOT server DOT ntli DOT net> <8296-Thu28Aug2003162425+0300-eliz AT elta DOT co DOT il> <3F4E90EF DOT 33122DA4 AT phekda DOT freeserve DOT co DOT uk> <2110-Fri29Aug2003133636+0300-eliz AT elta DOT co DOT il>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello.

Eli Zaretskii wrote:
[snip]
> Wide characters is one representation of non-ASCII characters.
> Another representation, which should also be supported by the library,
> is the multibyte representation, whereby every characters is
> represented as a series of 8-bit bytes.  (Many libraries choose UTF-8
> as their multibyte representation.)  The is* macros should support the
> multibyte representation in a manner equivalent to what the isw*
> macros do with the wide characters.  That is, if you pass a wide
> representation of a character CH to iswprint and the multibyte
> representation of the same character to isprint, you should get ther
> same result (I think).

If DJGPP were to support multibyte characters, then UTF-8 seems like the sane
choice.

I don't understand how is* can support multibyte characters, when they only
take an int argument.

Bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]