From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: nnhtml type backends -- idea
Date: 18 Apr 2000 12:57:54 -0400 [thread overview]
Message-ID: <2ng0sj9wj1.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "18 Apr 2000 15:55:56 +0200"
>>>>> "KG" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
KG> It seems that many of the web-based backends have problems because
KG> the HTML format changes and thus the parsing rules break.
KG> WIBNI there was a central server (www.gnus.org would be an obvious
KG> choice) which offered a couple of files containing the parsing
KG> rules? And that the nnhtml backends would fetch the current
KG> parsing rules before sending a query to the web server in
KG> question?
The idea sounds good. The parsing rules could be some urls and elisp
codes.
--
Shenghuo
next prev parent reply other threads:[~2000-04-18 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-18 13:55 Kai Großjohann
2000-04-18 16:57 ` Shenghuo ZHU [this message]
2000-04-19 13:37 ` Jaap-Henk Hoepman
2000-04-20 12:49 ` Eric Marsden
2000-04-20 18:28 ` Lars Magne Ingebrigtsen
2000-04-19 23:36 ` Lars Magne Ingebrigtsen
2000-04-19 23:44 ` Dan Christensen
2000-04-20 6:46 ` Kai Großjohann
2000-04-20 18:28 ` Lars Magne Ingebrigtsen
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=2ng0sj9wj1.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).