Message-ID: <011401c0887b$6034c580$788324d5@zephyr>
From: "Eric Botcazou" <ebotcazou AT libertysurf DOT fr>
To: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Cc: <djgpp AT delorie DOT com>
References:  <94ucfc$bgc$1 AT news6 DOT isdnet DOT net> <1858-Sat27Jan2001162857+0200-eliz AT is DOT elta DOT co DOT il>
Subject: Re: [ANNOUNCE] Allegro 3.9.34 WIP
Date: Sat, 27 Jan 2001 17:04:15 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Reply-To: djgpp AT delorie DOT com

> This is probably not entirely correct.  A "full Unicode" support would
> require support for such features as bidirectional text, letter cases
> beyond lower and upper, character equivalence, and others.  Does
> Allegro really support all these?

No, probably not all of them.
I should have written "Unicode support throughout the library", but I'm a
little lazy :-)
That's almost entirely Shawn's work; Allegro can use 4 encoding formats :
      U_ASCII     - fixed size, 8 bit ASCII characters
      U_ASCII_CP  - alternative 8 bit codepage
      U_UNICODE   - fixed size, 16 bit Unicode characters
      U_UTF8      - variable size, UTF-8 format Unicode characters

--
Eric Botcazou
ebotcazou AT multimania DOT com