Re: guchar -> gchar?

On Tue, 2005-08-02 at 18:04 -0600, Andreas J. Guelzow wrote:
> It will likely cause lots of warning messages in existing code using
> guchar* to call those functions! Note that the real cause of the
> warnings that you see is _not_ that those functions expect guchar* but
> that you (or whoever wrote the code) is passing to them gchar*.

strlen, strdup, strcpy all use char. The convention seems to use char
for all (user readable) strings. I don't see added value for=20
- casting strings to unsigned char when passing them to libgnomeprint
- casting them to char within libgnomeprint
- casting them to unsigned char when returning them
- casting them to char for further use in the calling function.

On Tue, 2005-08-02 at 19:25 -0300, John Coppens wrote:=20
> Won't you have problems with upper-128 characters like =E9, =ED, =FC et=
c?

We're using UTF-8.

--=20
Lutz M=FCller <[email protected]>