| 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 16:56:15 -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=EbTpXYBEFf+YxJNJnUuvuwp6wQMCmHKnZETXWfsh9fNGTyWspqBRgUXrbuicsSnRFfmb5IYeisHEg4ZIHCFK4omnvTcKdGCuSGQzhQz512mZevkhEoAkz1TTiqsdRziiQ2j1yLKwEC/7a5y0OsQfj1RQusty5WRUlKVGTzLRZTo=
On Thursday 04 May 2006 16:23, Michal Molhanec wrote:
> Well, you don't need dynamically allocated strings, I used them because
> I just hate fixed size buffers.
Yes, and the stack already has a nice 1K buffer on it for this, and globals
aren't terribly nice. Hence, problematic. ;)
> Every Windows machine has proper codepage set, many applications would
> not work otherwise.
I was under the impression that the user can set a different codepage
depending on their want. These codepages could have the same 7-bit ASCII base
set, but then add over a hundred more.. like, Latin characters, or German
characters, or whatever.