Re: Maybe codec bug in MS1252, i.e., encoding Cp1252

2011-09-05 Thread Eric Liang
On 09/03/2011 03:50 AM, Xueming Shen wrote: > On 09/02/2011 02:14 AM, Eric Liang wrote: >> On 09/02/2011 04:04 AM, Xueming Shen wrote: >>> Hi, >>> >>> These 5 code points are "undefined" character in Cp1252. The first one >>> should be 0x81 not 0x83, since 0x83<->u_0192 is defined and works >>> cor

Re: Maybe codec bug in MS1252, i.e., encoding Cp1252

2011-09-02 Thread Xueming Shen
On 09/02/2011 02:14 AM, Eric Liang wrote: On 09/02/2011 04:04 AM, Xueming Shen wrote: Hi, These 5 code points are "undefined" character in Cp1252. The first one should be 0x81 not 0x83, since 0x83<->u_0192 is defined and works correctly in Cp1252 charset). The mapping table you referred to is "

Re: Maybe codec bug in MS1252, i.e., encoding Cp1252

2011-09-02 Thread Eric Liang
On 09/02/2011 04:04 AM, Xueming Shen wrote: > Hi, > > These 5 code points are "undefined" character in Cp1252. The first one > should be 0x81 not 0x83, since 0x83<->u_0192 is defined and works > correctly in Cp1252 charset). The mapping table you referred to is > "bestfit" type mapping table, in wh

Re: Maybe codec bug in MS1252, i.e., encoding Cp1252

2011-09-01 Thread Xueming Shen
Hi, These 5 code points are "undefined" character in Cp1252. The first one should be 0x81 not 0x83, since 0x83<->u_0192 is defined and works correctly in Cp1252 charset). The mapping table you referred to is "bestfit" type mapping table, in which it tries to provide the mapping between the local