| 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 13:05:36 -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=LZsTDBHlvZvO1/fxlEMAmDDwqM9Tqb4O2KvSnexCXe0ZZ1nYZ0nuWWGKM3bfZX9by1qL5/vPfTf54QyUPCNyv+MSeYlM+EYMQKZhNmcoOxEqgV7+QZvf3HURFjE/RaZLsTJosQ0+mBt7FYvAV3GMOSlMubaUnoF0hf+vIM7jvpk=
On Thursday 04 May 2006 06:42, Victor wrote:
> As a game programmer using a portable library, I intend that my
> software run everywhere regardless of OS details (even if the user is
> running it in Win95, or maybe DOS). I agree, as a programmer, that
> really is a bad pratice to depend in nôn-ÁNSI chãrçters, bút as a
> nõn-ênglïsh spèaker they may eventually appear somewhere (sometimes
> they could be some user input). Users don't want to know deep details
> of the implementation, so limiting them to not use extended characters
> is not a good choice (even if just on a few old OSes). So I think that
> trying to support them, even if this could get complex, is a good idea.
Non-ANSI characters will only have "problems" in Win9x, and really, Allegro
won't have any less functionality than it currently has. Things that worked
before will continue to work. The only change this patch makes is to allow
the use of _wstat, _wfindfirst, etc, on Windows systems that support it.
Win9x's codepage API has the potential to create problems, which is why WinNT
and up started using UTF-16. There's no reason to support potentially
problematic, esoteric methods for extended characters when a simpler method
is available. Win9x is not known for good extended character support, for
users or programmers, and this is why.