| 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: Victor <vwss1984@xxxxxxxxxx>
- Date: Thu, 4 May 2006 17:37:10 -0300 (ART)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.br; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=AbrqhHU27N9EpkCDVBoS4pbRQzWsEVujK1jAmEg/eKwnf+PVRW6ViIGwbeRmgb5l83kUP2qE04dlktojU5JXtWItaVRGkJuFYD4TnsRaxwH6SI17UCMyaNZOruZhISltvbfJYsAav2ui1RWG+51R1BpD91H7GW7weJom7/8i1NU= ;
--- Chris <chris.kcat@xxxxxxxxxx> escreveu:
> 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.
>
I wasn't very clear in my previous e-mail, sorry. I was refering to
filenames with non-ansi characters passed down to allegro functions. In
Win9x, filenames with non-ansi characters tends to be incorrectly
interpreted by allegro (like as these files doesn't exist) [honestly i
didn't tested this, since I don't have these old Windows around
anymore, but if that is not the case so no one would be complaining
about, or maybe i'm confused and missed completely the point].
Everyone here know that Windows is something with highly weird and
anti-crossplatform API with some stupid and buggy behavior in some
places and there are plenty of known and unknown oddities. So it is
obvious that trying to support this is hard. But if we can do support
that, even if partially, we got an advance.
Simply saying "i won't fix" is something contrary to allegro-filosofy,
as we want our library being cross-platform, multilanguage, backwards
compatible (ok, not everyone agrees here) and mainly _bug free_
(something unreachable, i know, but we need run for it).
Or maybe, since this is a small issue easy to workaround, and if we
decide to "stay as it is", so we should at least document that.
Victor Williams Stafusa da Silva
_______________________________________________________
Abra sua conta no Yahoo! Mail: 1GB de espaço, alertas de e-mail no celular e anti-spam realmente eficaz.
http://br.info.mail.yahoo.com/