Re: \201 *waugh*

[ShengHuo ZHU <zsh@cs.rochester.edu>]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> After upgrading to the latest cvs, nnwfm stopped working with Emacs
> 20.6.  Which is really weird, since nnwfm didn't change at all.
> 
> Now -- I insert lots of stuff into a unibyte buffer.  I then use
> w3-parse on the stuff in the buffer.  I then get strings like
> 
>   "aksje-\345r"
> 
> Now, how on earth do I get that inserted back into a buffer, and why
> did it stop working?
> 
> (insert "aksje-\345r")
> => aksje-år
> 
> That's not what I want.  I want something I can then run
> decode-coding-region on, like in all other groups.

When a unibyte string is inserted into a multibyte buffer, Emacs
automatically converts 8-bit characters into iso8859-1 characters.  To
insert literally 8-bit characters, you have to use some tricks like

 (insert (string-as-multibyte "aksje-\345r"))

XEmacs doesn't have string-as-multibyte, so we'd better define a
compatible function mm-string-as-multibyte.  Though you may see 
aksje-år in XEmacs buffer if you insert the string, it is OK. XEmacs
people claim that XEmacs doesn't suffer the \201 problem.

ShengHuo