Re: \201 *waugh*

Re: \201 *waugh*

[ShengHuo ZHU]

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

Re: \201 *waugh*

[Kai Großjohann]

On 28 Dec 2000, Lars Magne Ingebrigtsen wrote:

> Now -- I insert lots of stuff into a unibyte buffer.  I then use
> w3-parse on the stuff in the buffer.

I wonder: does w3-parse want to see a sequence of bytes or a sequence
of characters in the buffer?  Maybe it helps to see what url.el
deposits in url-working-buffer.

kai
-- 
~/.signature

\201 *waugh*

[Lars Magne Ingebrigtsen]

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.

Please.  Help me.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: \201 *waugh*

[Lars Magne Ingebrigtsen]

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> When a unibyte string is inserted into a multibyte buffer, Emacs
> automatically converts 8-bit characters into iso8859-1 characters.

Oh.  Huh.  Is that a new thing?  How does it know that I want
iso8859-1 and not anything else?

> To insert literally 8-bit characters, you have to use some tricks
> like
> 
>  (insert (string-as-multibyte "aksje-\345r"))

That did the trick; thanks.

> XEmacs doesn't have string-as-multibyte, so we'd better define a
> compatible function mm-string-as-multibyte.

Yup.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: \201 *waugh*

[Lars Magne Ingebrigtsen]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> I wonder: does w3-parse want to see a sequence of bytes or a sequence
> of characters in the buffer?  Maybe it helps to see what url.el
> deposits in url-working-buffer.

Hm...  I would guess that w3 wants characters, and not bytes.  So
perhaps the correct thing would be to decode the text, give it to w3,
and then encode the results, since Gnus expects a sequence of bytes.
And then Gnus will decode it again.

Alternatively, I can just use string-as-multibyte.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: \201 *waugh*

[ShengHuo ZHU]

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

> ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> 
> > When a unibyte string is inserted into a multibyte buffer, Emacs
> > automatically converts 8-bit characters into iso8859-1 characters.
> 
> Oh.  Huh.  Is that a new thing?  How does it know that I want
> iso8859-1 and not anything else?

I guess it is at least as old as the \201 problem. The default coding
system can be customized, but it can not be binary (no decoding).

ShengHuo