| Re: [AD] Allegro unable to deal with non ascii filenames |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: Coordination of admins/developers of the game programming library Allegro <alleg-developers@xxxxxxxxxx>
- Subject: Re: [AD] Allegro unable to deal with non ascii filenames
- From: Elias Pschernig <elias@xxxxxxxxxx>
- Date: Sat, 27 May 2006 23:23:37 +0200
On Sat, 2006-05-27 at 22:50 +0200, Grzegorz Adam Hankiewicz wrote:
> On 2006-05-27, Elias Pschernig <elias@xxxxxxxxxx> wrote:
> > > So, it seems we should do just what you said - try to detect a default
> > > encoding, and convert filenames to that (instead of ASCII as right now).
> > > If possible, maybe we could include it in 4.2.1 still - seems like a
> > > serious flaw :/
> >
> > Attached is a first conceptual patch. With this patch, your testcase
> > works fine here. It adds a new function "set_file_encoding", used like
> > this:
>
> I thought this would break the API? That's why I suggested doing
> all this stuff for 4.2.x with no function (tweaking through
> configuration/environment), and add the call to 4.3.x.
No, we only provide backwards compatibility (use 4.2.1 library when code
was compiled against 4.2.0) - so adding new symbols is no problem. In
fact 4.2.1 already has got several new symbols compared to 4.2.0.
--
Elias Pschernig