Re: iconv vs. libiconv, was Re: Patch: Fix for Bug 1164, 2nd try


Subject: Re: iconv vs. libiconv, was Re: Patch: Fix for Bug 1164, 2nd try
From: Andrew Dunbar (hippietrail@yahoo.com)
Date: Wed May 23 2001 - 01:33:46 CDT


ha shao wrote:
>
> On Wed, May 23, 2001 at 03:51:42PM +1000, hippietrail@yahoo.com wrote:
> > This seems related. I've noticed in xap_EncodingManager.cpp the
> > function charsetFromCodepage returns "GB2312", "BIG5", etc instead
> >
> > of "CP936", "CP950", etc even when the iconv supports
> > the "CPxxx"
> > form and the encodings differ.
> >
> >
> > I've looked at where this function is called and it seems to me this
> > opens the door to lossy conversions. Should this function also use
> > some form of fallback so that "BIG5" is only returned when iconv
> > doesn't support "CP950"? Or maybe this function is ambiguous and
> > really should be two separate functions?
>
> This is what I've suggested in another mail. Yes, please replace
> the mapping to a fallback call/macros.

Could somebody more familiar with the relevant code implement this?
I don't think I know it well enough. Especially Unix iconv
implementation issues.

Should we report it as a bug?

Andrew.

-- 
http://linguaphile.sourceforge.net

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com




This archive was generated by hypermail 2b25 : Sat May 26 2001 - 03:51:06 CDT