From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: \201 *waugh*
Date: 28 Dec 2000 23:12:50 +0100 [thread overview]
Message-ID: <m3vgs49ov1.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <vafofxwjs9z.fsf@lucy.cs.uni-dortmund.de>
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
prev parent reply other threads:[~2000-12-28 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-28 19:55 Lars Magne Ingebrigtsen
2000-12-28 18:27 ` ShengHuo ZHU
2000-12-28 22:10 ` Lars Magne Ingebrigtsen
2000-12-29 6:07 ` ShengHuo ZHU
2000-12-28 18:48 ` Kai Großjohann
2000-12-28 22:12 ` Lars Magne Ingebrigtsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3vgs49ov1.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).