[mew-int 2496] Re: A patch: make-string in emacs 23
Kazu Yamamoto ( 山本和彦 )
kazu at example.com
Thu May 15 15:49:16 JST 2008
Harald,
Thank you for your message.
> The funny thing is this: From my investigations, it seems that text
> from the imap server really gets decoded into "ø Ω", which in turn
> leads to the problem we're discussing here: Mew creates a unibyte
> string, stuffs the letter "ø" into it, then the space, and finally the
> "Ω" – which fails, since the string is now a unibyte non-ASCII string.
> There seems to be another underlying bug here, in that data from the
> server is decoded using what seems like utf-8 with a fallback to
> latin-1 for stuff that can't be utf-8?
OK. I will start talking with Handa-san again.
I will ask him, whether or not Mew should guard with
(if (char-valid-p 256) 256 ?x)
Unfortunately, CVS HEAD today is broken. I cannot compile it. So, it
would take a time.
One suggestion: backtrace does not show much information if Emacs Lisp
files are byte-compiled. Removing *.elc and executing Emacs would show
much information in backtrace.
--Kazu
More information about the Mew-int
mailing list