Subject: Re: Patch: Encoding Manager
From: ha shao (hashao@chinese.com)
Date: Sun Jun 03 2001 - 10:00:49 CDT
On Sun, Jun 03, 2001 at 11:48:04PM +1000, hippietrail@yahoo.com wrote:
> Vlad Harchev wrote:
> > ---------------
> > +// Warning:
> > +// This code forces us to use "GB2312", "BIG5", etc instead
> > +// of "CP936", "CP950", etc even when our iconv supports
> > +// the "CPxxx" form and the encodings differ.
> > +// Be sure this is what you want if you call this function.
> > const char* XAP_EncodingManager::charsetFromCodepage(int lid) const
> > {
> > ---------------
> > Yes, the warning is correct. It would be nice if somebody rewritten it
> > properly.
>
> I think this is a job for somebody who is expert in both
> CJK and iconv on various platforms. There are other issues when
> we're calling different versions of iconv. Some iconvs recognize
> different names for the same encoding, in other cases we might not
> have access to the exact required encoding but we can have a table
> which uses the "least lossy" fallback. Many encodings are subsets
> of others and some have very minor differences from one another.
> I've stumbled across these issues in my Encoding Dialog...
>
I did a patch which takes a list of fallback locales for certain Codepage.
I am not sure if there already is a XP class for string-> string array
somewhere. So the patch is more c like. :)
Old mail attached.
-- Best regard hashao
attached mail follows:
Patch Attached....
On Wed, May 23, 2001 at 05:28:12PM +1000, hippietrail@yahoo.com wrote: > We probably need somewhere a table that takes an array of > fallback encoding names. Most of the entries probably only > need one fallback name but the Japanese Shift JIS ones > might need more. Look in the encodings.def file in the > libiconv source... >
Does this patch meet the requirement?
-- Best regard hashao
This archive was generated by hypermail 2b25 : Sun Jun 03 2001 - 10:00:37 CDT