From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: emacs-w3m@namazu.org
Subject: [emacs-w3m:08495] Re: nnrss should borrow nnshibmun's RSS date processor...or something
Date: Tue, 10 Jan 2006 19:13:34 +0900 [thread overview]
Message-ID: <b4mk6d84chd.fsf@jpl.org> (raw)
In-Reply-To: <871wzlpkbf.fsf@stone.tss.usg.edu>
>>>>> In <871wzlpkbf.fsf@stone.tss.usg.edu> Mark Plaksin wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> 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 might not be qualified for saying how text/plain parts are
useful, but
> 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.
I realized it is effective to render even text/plain parts as
HTML if a user prefers to see them, and we will be able to call
it a bug that text/plain parts contain raw HTML tags. So, I've
added the following variable (and the code). Could you try it?
`nnrss-wash-html-in-text-plain-parts'
Non-`nil' means that `nnrss' renders text in `text/plain' parts as
HTML. The function specified by the `mm-text-html-renderer'
variable (*note Display Customization: (emacs-mime)Display
Customization.) will be used to render text. If it is `nil',
which is the default, text will simply be folded. Leave it `nil',
if you prefer to see `text/html' parts.
next prev parent reply other threads:[~2006-01-10 10:13 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 ` [emacs-w3m:08492] " Mark Plaksin
2006-01-10 10:13 ` Katsumi Yamaoka [this message]
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=b4mk6d84chd.fsf@jpl.org \
--to=yamaoka@jpl.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).