From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/61637 Path: news.gmane.org!not-for-mail From: Mark Plaksin Newsgroups: gmane.emacs.w3m,gmane.emacs.gnus.general Subject: [emacs-w3m:08492] Re: nnrss should borrow nnshibmun's RSS date processor...or something Date: Fri, 06 Jan 2006 08:17:24 -0500 Message-ID: <871wzlpkbf.fsf@stone.tss.usg.edu> References: <87y82dokdt.fsf@stone.tss.usg.edu> <8764p2g0wc.fsf@stone.tss.usg.edu> <87psn8aepk.fsf@stone.tss.usg.edu> <87lkxwadgc.fsf@stone.tss.usg.edu> <878xtug279.fsf@stone.tss.usg.edu> Reply-To: emacs-w3m@namazu.org NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1136553476 9667 80.91.229.2 (6 Jan 2006 13:17:56 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 6 Jan 2006 13:17:56 +0000 (UTC) Cc: ding@gnus.org Original-X-From: emacs-w3m-admin@namazu.org Fri Jan 06 14:17:54 2006 Return-path: Envelope-to: emacs-w3m@deer.gmane.org Original-Received: from quimby.gnus.org ([80.91.224.244]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EurTZ-0007jn-FL for emacs-w3m@deer.gmane.org; Fri, 06 Jan 2006 14:17:50 +0100 Original-Received: from vaj.namazu.org ([61.215.208.42]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1EurTY-0001U0-00 for ; Fri, 06 Jan 2006 14:17:49 +0100 Original-Received: from vaj.namazu.org (localhost [127.0.0.1]) by vaj.namazu.org (Postfix) with ESMTP id 1CDDF20049; Fri, 6 Jan 2006 22:17:41 +0900 (JST) Original-Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by vaj.namazu.org (Postfix) with ESMTP id B7A831FF51 for ; Fri, 6 Jan 2006 22:17:39 +0900 (JST) Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1EurTJ-0007gD-4c for emacs-w3m@namazu.org; Fri, 06 Jan 2006 14:17:33 +0100 Original-Received: from stone.tss.usg.edu ([168.24.82.77]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 06 Jan 2006 14:17:33 +0100 Original-Received: from happy by stone.tss.usg.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 06 Jan 2006 14:17:33 +0100 Original-Sender: news Original-To: emacs-w3m@namazu.org X-ML-Name: emacs-w3m X-Mail-Count: 08492 X-MLServer: fml [fml 4.0.3 release (20011202/4.0.3)]; post only (anyone can post) X-ML-Info: If you have a question, please contact emacs-w3m-admin@namazu.org; User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0 (gnu/linux) X-Injected-Via-Gmane: http://gmane.org/ Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: stone.tss.usg.edu Cancel-Lock: sha1:gA9rvSO/QHFe34M9iJShviadjRI= X-Spam-Flag: No X-Spam-Probability: 0.000000 Precedence: bulk Original-Lines: 47 List-Id: emacs-w3m.namazu.org List-Software: fml [fml 4.0.3 release (20011202/4.0.3)] List-Post: List-Owner: List-Help: List-Unsubscribe: Xref: news.gmane.org gmane.emacs.w3m:5853 gmane.emacs.gnus.general:61637 Archived-At: Katsumi Yamaoka writes: >>>>>> In <878xtug279.fsf@stone.tss.usg.edu> Mark Plaksin wrote: > >> Katsumi Yamaoka 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 using > nnrss gave me a hint. Some articles contain html tags, e.g., >

...

,
...
, 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

,

, 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.