| 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: Thu, 4 May 2006 17:37:49 -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=e1rZpEaZnSssj0zmEUIVpWTV+DuF6dmoDkkLU5CyLqyOqQii1efKGkIpbXjBfIrxOJ2zVcFnA9fTe2XcOnUU0y4jEuMEXqwPvPrdN4O5llzhwvB9HquHEI6iYW18yNLVMwhT5DcVlOMabS3EkjhZtutdDfmruCsUb5GyYL7AdWw=
On Thursday 04 May 2006 17:29, Michal Molhanec wrote:
> Chris napsal(a):
> > Yes, and the stack already has a nice 1K buffer on it for this, and
> > globals aren't terribly nice. Hence, problematic. ;)
>
> My patch didn't use any global variable.
I know. I mean that besides using dynamicly allocated strings, you'd have to
use a static array on the stack (which already has stuff on it), or a global
array.
> But that's not important, you are not specifying any particular encoding
> in the WideCharToMultibyte function, you are just saying "convert it
> to user's ANSI codepage whatever it is". You are not interested in exact
> encoding.
Right. So if you have a filename with, say, an accented e, and the user's
codepage doesn't have an accented e, it'll be mapped to the "unknown"
character, and the file won't be found.