| Re: [AD] Windows unicode filename support |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Windows unicode filename support
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Wed, 19 Apr 2006 21:52:51 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=LbwyZUlH/WGK42VVCm1JLHMlDq8HaFBFxkhIv+Z4X0l4SuLYbgmfHhUmObUP72nH93UBLD0ul0hnNOYaTMfiv++fRXxvWdCBskFx2LpDrhUbk+Vkey+G7bbD1012Wxe+rJ/7sYaV6uV59HO0WFlj6fHn1EeuFqoz6t5GxfSYRtY=
On Wednesday 19 April 2006 21:34, Victor wrote:
> Can we use wchar_t?
wchar_t is a wide-char (2 bytes), and thus wouldn't be compatible with
non-UTF-16 modes (and I'm not sure it's standard, either). Personally I
prefer UTF-8, which is stored in normal char arrays and is compatible with
ASCII-7. AFAIK, there are also no standard routines to deal with UTF-16 data,
either.. so everything from printf, to vsnprintf, to strcat, to strncasecmp,
would all have to be reimplemented (granted Allegro does some of this, but
you can still use UTF-8 and most of the standard text functions without them
(or Allegro at all)).