On 04 May 2001 21:43:08 -0400, Christopher James Lahey wrote:
> On 04 May 2001 12:50:59 -0400, Jon Trowbridge wrote:
> > OK, I've just committed some tweaks to gal's g_utf8_* functions that make
> > them check all their inputs and print a warning if they are applied to bad
> > utf-8.
> >
> > The checks are macroified, but I've turned them on by default. This way,
> > there will at least be some warning when we are doing something broken.
> >
> > -JT
>
> The problem is that these are often outside world generated strings.
> I'm not sure if we should leave dealing with checking in real life
> situations to the caller or to the internal functions. It would be less
> programmer work probably to fix the internal functions to handle
> incorrect utf8. Ideally to assume that incorrect utf8 is latin1 since
> that's what it will be most of the time.
Of course you did not want to say "ideally" ;)
Especially when you talk about gal, which has locale charset detecting
functions e_utf8_*_locale_string.
--
Gediminas Paulauskas
Kaunas, Lithuania
_______________________________________________
evolution-hackers maillist - [EMAIL PROTECTED]
http://lists.helixcode.com/mailman/listinfo/evolution-hackers
