Subject:
|
quoted-printable encoding
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Thu, 16 Mar 2000 18:41:24 GMT
|
Viewed:
|
1011 times
|
| |
|
|
In lugnet.admin.general, Todd Lehman writes:
> > Is LUGNET modular enough to allow many hands in the code?
> It really isn't, no. But from time to time there might be things which
> are encapsulatable enough to be done independently and worked in afterwards.
> The FTX-to-HTML compiler, for example, is fairly encapsulated -- except for
> the transclusion portions which slurp in news articles.
Just thought of something...
One thing missing which would be 100% encapsulatable would be a filter to
fix up icky encodings like "quoted-printable" (which cause stuff like =F6
and =20 to appear all over the place) into regular non-encoded 'text/plain'.
For example:
http://www.lugnet.com/news/raw.cgi?lugnet.cad:2049
Worse example:
http://www.lugnet.com/news/raw.cgi?lugnet.robotics:7793
And a really perverse example of what evil lies downstream when people reply
and reply to a quoted-printable message with a newsreader that doesn't handle
it properly:
http://www.lugnet.com/news/raw.cgi?lugnet.robotics:10737
The filter would need to take a raw[1] NNTP news article on stdin, produce a
raw NNTP news article on stdout, and examine the 'Content-Transfer-Encoding'
and 'Content-Type' headers to determine what, if any, conversion needed to be
applied. It would then run alongside the other filters which run when an
article is received.
Fortunately, the "quoted-printable" encoding doesn't need to have (AFAIK) any
particular de-encoding mechanism if the 'Content-Type' header contains the
name of the character set (e.g. "ISO-8859-1") -- all it has to do is un-hexify
and handle line-endings the right way (whatever those rules are).
--Todd
[1] Well, not exactly 100% "raw" -- it'll already have the CRLF's converted
to Unix LF format. But raw in the sense of just being a stream of article
text -- headers plus body.
|
|
Message is in Reply To:
 | | Re: Cleaning up the main homepage
|
| (...) It really isn't, no. But from time to time there might be things which are encapsulatable enough to be done independently and worked in afterwards. The FTX-to-HTML compiler, for example, is fairly encapsulated -- except for the transclusion (...) (24 years ago, 13-Mar-00, to lugnet.admin.general)
|
111 Messages in This Thread:
(Inline display suppressed due to large size. Click Dots below to view.)
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
