From: Mark Plaksin <happy@usg.edu>
Cc: ding@gnus.org
Subject: [emacs-w3m:08492] Re: nnrss should borrow nnshibmun's RSS date processor...or something
Date: Fri, 06 Jan 2006 08:17:24 -0500 [thread overview]
Message-ID: <871wzlpkbf.fsf@stone.tss.usg.edu> (raw)
In-Reply-To: <b4mirsy44d4.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>>>>> In <878xtug279.fsf@stone.tss.usg.edu> Mark Plaksin wrote:
>
>> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>
>>> P.S. I've also fixed the way to fill text/plain parts.
>
>> Ha! I've noticed some problems in this area but haven't tracked them down
>> yet. Your changes don't seem to make a difference for me. For example,
>> when I W Q in the Summary buffer this text/plain part:
>
>> http://feeds.feedburner.com/arstechnica/BAaf?m=1590
>> Ars Technica is at CES 2006, and this quick item will detail how our coverage
>> will pan out over the next few days.
>
>> gets filled to this:
>
>> http://feeds.feedburner.com/arstechnica/BAaf?m=1590
>> Ars Technica is at CES 2006, and this quick item will detail how our
>> coverage
>> will pan out over the next few days.
>
>> fill-column is set to 75.
>
> No, what I changed was not the `W Q' code. Formerly, no matter
> how it was long, nnrss always generated a single long line in
> the text/plain part like this:
> #v+
> Ars Technica is at CES 2006, and this quick item will detail how our coverage will pan out over the next few days.
> #v-
> What I did in nnrss.el was to fold the text/plain part, binding
> fill-column to 7/8 of the window width.
>
> BTW, reading <http://feeds.feedburner.com/arstechnica/> using
> nnrss gave me a hint. Some articles contain html tags, e.g.,
> <p>...</p>, <blockquote>...</blockquote>, even in the text/plain
> parts (they are quoted like "<p>" in the xml source).
> Perhaps we might need to render such contents properly. I don't
> have an idea how to do it, though.
This brings me back to wondering about the utility of text/plain parts in
RSS feed articles. I mean the "right" way to handle <p>, <blockquote>, and
such is to render them as HTML which is what happens when you look at the
text/html part. You never know what HTML tags are going to show up in RSS
articles so you have handle them all.
next prev parent reply other threads:[~2006-01-06 13:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 3:55 [emacs-w3m:08473] " Mark Plaksin
2005-12-22 5:27 ` [emacs-w3m:08474] " Katsumi Yamaoka
2006-01-02 14:28 ` Mark Plaksin
2006-01-04 2:13 ` [emacs-w3m:08485] " Katsumi Yamaoka
2006-01-04 2:50 ` [emacs-w3m:08486] " Mark Plaksin
2006-01-04 3:05 ` Katsumi Yamaoka
2006-01-04 3:17 ` Mark Plaksin
2006-01-05 7:09 ` [emacs-w3m:08489] " Katsumi Yamaoka
2006-01-05 14:48 ` [emacs-w3m:08490] " Mark Plaksin
2006-01-05 23:55 ` [emacs-w3m:08491] " Katsumi Yamaoka
2006-01-06 13:17 ` Mark Plaksin [this message]
2006-01-10 10:13 ` [emacs-w3m:08495] " Katsumi Yamaoka
2006-01-14 16:03 ` [emacs-w3m:08502] " Mark Plaksin
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=871wzlpkbf.fsf@stone.tss.usg.edu \
--to=happy@usg.edu \
--cc=ding@gnus.org \
--cc=emacs-w3m@namazu.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).