> > Please apply following one-line-patch and test it again. If it's ok, I
> > will commit it to both current and stable trees.
> >
> > ! return (b2c3[i][1] | 0x8080U);
>
> Yes, it's OK. Thank you!
Thanks for the testings. I will commit soon.
> But I wonder why we
> > Please apply following one-line-patch and test it again. If it's ok, I
> > will commit it to both current and stable trees.
> >
> > ! return (b2c3[i][1] | 0x8080U);
>
> Yes, it's OK. Thank you!
> But I wonder why we need to "| 0x8080U"?
> b2c3[][] and BIG5toCNS()
Tatsuo,
Tatsuo Ishii ¼g¹D¡G
> Please apply following one-line-patch and test it again. If it's ok, I
> will commit it to both current and stable trees.
>
> ! return (b2c3[i][1] | 0x8080U);
Yes, it's OK. Thank you!
But I wonder why we need to "| 0x8080U"?
b2c3[][] a
Chih-Chang,
> Do you remember the mb problem about Big5?
Sure.
> Now I have tested all Big5 chars (with ETen extension -- some chars in
> CNS 11643-1992 Plane 3) by the program in the attachment on
> PostgreSQL 7.0.3 with patches from you show me.
> The execution result is also in the attachmen