| Re: [AD] al_font_textprintf() and uvszprintf() |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Wednesday 29 October 2008, Peter Wang wrote:
> On 2008-10-29, Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx> wrote:
> > whatever is the current... It currently should handle unicode incoming
> > strings. If it doesn't, sorry, my-bad.
> >
> > What should happen is the fshook api should send in "native" format
> > strings, which could be ASCII, some codepage, 16bit unicode or UTF8
> > depending on the platform and "locale". And fshook should be able to take
> > in whatever format the user gives it that allegro supports.
>
> Sorry, I didn't find that very clear.
>
> Let's take an example. Say the filesystem encoding is UTF-8, but the
> user decided to make his application use ISO-8859-1 (Latin-1) just because.
> What happens with the path API?
I would think the path api could do whatever it wants. (use the current
encoding), its fshooks and the current driver that needs to care.
This way everything is in the format the user expects, and the only place that
needs a conversion is inside the fshook driver. Which does need fixed, the
current stdio code doesn't bother to detect what the OS actually wants, and it
really should. and all that would take is a uconvert(U_CURRENT, ...,
os_wants_this_mode, ...); wherever a path/string gets passed to the OS.
> I would expect the path API to work with UTF-8 and not Latin-1,
> otherwise there may be files on disk which are not accessible!
> Of course, if the font addon works with Latin-1 then there may
> be valid paths that won't display on the screen.
>
> And then there are Unicode normalisations to consider.
Hm?
> Peter
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge Build the coolest Linux based applications with Moblin SDK & win
> great prizes Grand prize is a trip for two to an Open Source event anywhere
> in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
--
Thomas Fjellstrom
tfjellstrom@xxxxxxxxxx