On Mon, Dec 05, 2005 at 02:31:46PM +0100, Alain Bench wrote: > -a) You force "set charset=GBK" in muttrc: Remove this line. $charset > must be free to follow the current locale, whatever it is.
Yes, it's here. And I have removed it already. | [EMAIL PROTECTED]:~$ unset LC_ALL | [EMAIL PROTECTED]:~$ unset LC_CTYPE | [EMAIL PROTECTED]:~$ export LANG=zh_CN.GBK | [EMAIL PROTECTED]:~$ locale | LANG=zh_CN.GBK | LC_CTYPE="zh_CN.GBK" | LC_ALL= Then it segfaulted. While it displayed '?' for the latin accent and did not segfault if I set | LC_CTYPE=C > > Did this mean 1) The library think this char is in GBK charset. > > Well a discrepency: Part thinks it's good GBK, part it's invalid > US-Ascii. In a correct C setup, the display should be masked by one "?" > (because the E9 byte does not exist in US-Ascii): > > | Rog?rio Brito Yes, It did just as you said. > > 2) This char cannot be found in my GBK fonts. > > It surely exists in font, because at shell you can see a "lowercase > e with an acute accent" (a small slash above the e letter) doing: > > | printf "\xA8\xA6" > > BTW: On your GBK terminal, is it a "half-wide" character as Ascii e, > or full-width as Chinese chars? A full-width as Chinese chars. > Not annoying at all: This fact brings 2 small informations to the > puzzle. Precious, as any other precisions you give us. I still don't get > the full picture, since my best so far "invalid multibyte" hypothesis > seems dead. Let's dig a little more, if you accept. Sure! > > While both your mails were perfectly valid UTF-8 mails. So the > segfault is not only with ISO-8859-1 chars. Yet another small piece for > the puzzle. :-) Yes, It's utf-8 indeed. And it will segfault even if I unset LC_ALL and remove the charset declaration in .muttrc. > > > Hum... Random idea. Could you check: > > | $ printf "Rog\xE9rio\n" | iconv -f l1 -t wchar_t | iconv -f wchar_t -t gbk |[EMAIL PROTECTED]:~$ printf "Rog\xE9rio\n" | iconv -f l1 -t wchar_t | iconv -f wchar_t -t gbk |Rogério Yet another full-width Chinese char, e with accent. Thanks for your explanation and hope the informations helpful. Regards, Wang Xu > > > Bye! Alain. > -- > When you want to reply to a mailing list, please avoid doing so from a > digest. This often builds incorrect references and breaks threads. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
