| 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: "Milan Mimica" <milan.mimica@xxxxxxxxxx>
- Date: Thu, 4 May 2006 12:00:05 +0100
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=m9eEyFYdgGj4ewxLTRrg1GFnxiq4yARViE1wtVefdnk8IapmjE+ZvtmPBI8/eSua/qJlTNPmojlt2zpbfdzauz8W868AqeP0mtDHzIRZhdESzdFr78d9DKFKFWYWyu1DYzZ+ex3QKgXpOSoznHwyeRG79ICtAISsI0kyVZTds7s=
On 20/04/06, Chris <chris.kcat@xxxxxxxxxx> wrote:
Since I made a patch for Unix a while ago to support UTF-8/Unicode filenames,
it'd only be fair for Windows to support Unicode filenames too. I don't
believe Windows' _stat/_findfirst/etc would work properly with UTF-8 names
like the similar routines seem to in Unix, so I opted to change it to use the
wide-char/UTF-16 equivilants (_wstat/_wfindfirst/etc).
I had a Windows user test it and it seems to work in his app.
Still, functions like load_bitmap() won't work with "strange"
characters because open() in file.c would need to be replaced with
wopen() when available. We should probably implement _al_open for
every platform, not just mac.
--
Milan Mimica
http://sparklet.sf.net