Thread: could not convert (0xf9db) BIG5 to UTF-8
Hi! Experts, I am not absolutely sure this is a bug but I get local_to_utf: could not convert (0xf9db) BIG5 to UTF-8. Ignored local_to_utf: could not convert (0xf9d7) BIG5 to UTF-8. Ignored when inserting/copying these 2 BIG5 characters to tables. The server encoding is set to "UNICODE" and client is set to "BIG5". Best Regards, CN -------------------------------------------------------- You too can have your own email address from Eurosport. http://www.eurosport.com
> I am not absolutely sure this is a bug but I get > > local_to_utf: could not convert (0xf9db) BIG5 to > UTF-8. Ignored > local_to_utf: could not convert (0xf9d7) BIG5 to > UTF-8. Ignored > > when inserting/copying these 2 BIG5 characters to > tables. The server encoding is set to "UNICODE" and > client is set to "BIG5". The messages says BIG5 code points 0xf9db and 0xf9d7 are not valid. Are you sure that these BIG5 characters are valid? -- Tatsuo Ishii
I entered these 2 characters in 2 files using vi by telneting to Linux from Windows95 (Tranitional Chinese). One in t1 and the other in t2. These 2 characters are visible in vi and Windows notepad. Then, #od -tx t1 0000000 000adbf9 0000003 #od -tx t2 0000000 000ad7f9 Did I correctly conduct the testing? Regards, cn > > I am not absolutely sure this is a bug but I get > >=20 > > local_to_utf: could not convert (0xf9db) BIG5 to > > UTF-8. Ignored > > local_to_utf: could not convert (0xf9d7) BIG5 to > > UTF-8. Ignored > >=20 > > when inserting/copying these 2 BIG5 characters to > > tables. The server encoding is set to "UNICODE" and > > client is set to "BIG5". > The messages says BIG5 code points 0xf9db and 0xf9d7 are not > valid. Are you sure that these BIG5 characters are valid? -------------------------------------------------------- You too can have your own email address from Eurosport. http://www.eurosport.com