| Re: [AD] unicode proposal |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On January 20, 2009, Elias Pschernig wrote:
> The topic was brought up a few times already, but at some point we
> should decide what to do about unicode functions in A5.
>
> An easy solution would be to assume that any strings passed to Allegro
> functions are encoded in UTF8 (that includes all 7-bit ASCII strings).
> Then prefix some of the A4 unicode functions with al_ so users aren't
> completely left in the dark when they have to deal with non-ASCII
> strings.
>
> A4 function descriptions are here:
> http://www.liballeg.org/stabledocs/en//alleg002.html
>
>
> Functions which are not needed because they are identical for ASCII and
> UTF8, but which we might keep as prefixed aliases anyway:
>
> ustrcat
> ustrcpy
> ustrdup
Cant UTF8 have embedded null chars in it?
>
> The conversion functions likely can be useful internally in the
> filesystem code - but the user should not have to deal with anything but
> UTF8 when using A5's filesystem layer.
Right I'm hoping to make it all dead simple.
> --
> Elias Pschernig <elias@xxxxxxxxxx>
>
--
Thomas Fjellstrom
tfjellstrom@xxxxxxxxxx