Re: [AD] Allegro unable to deal with non ascii filenames

[Elias Pschernig <elias@xxxxxxxxxx>]

On Sun, 2006-05-28 at 09:54 -0400, Jon Rafkind wrote:
> >   
> What if Allegro tried to write out a UTF8 file, or something, at startup
> and then read it back in using a variety of methods until one of them
> works. Then Allegro will know what the default character set is for that
> user. Is this the sort of guessing python does?
> 
> Sorry if this doesn't make any sense, I probably didn't follow the
> thread too well.

Sounds like a good idea. It still means though, we are limited to the
encodings Allegro supports - which are: U_ASCII, U_UTF8, U_UNICODE,
U_ASCII_CP

This in turn means, it will only take 3 comparisons of the file name to
find the encoding :) Actually, U_ASCII_CP seems not useful here, so it
leaves the other 3. U_UNICODE is 16-bit, so it also can't be used
(unless we switch to libc's wide string functions).

Which means, all we can do is, use either U_ASCII or U_UTF8, since
Allegro doesn't even supports things like ISO-8859-1.

Do I see this right? I hope not.. maybe U_ASCII_CP can be used somehow
after all..

-- 
Elias Pschernig