| |
In lugnet.admin.suggestions, William R. Ward writes:
> [...]
> LUGNET should detect this and convert the =NN codes to the appropriate
> characters (NN is the hexadecimal value for the encoded characters).
Heh heh, funny you should mention that... Last night I was just thinking
about this again and am 98% ready to deploy a fix. I've really noticed the
increase in these posts lately too (especially coming in through the
News-by-Mail gateways).
A which back, Dan Boger contributed a Perl5 script which does the conversion
to 8bit content transfer encoding. We did a bunch of regression testing,
feeding it old article data, but then it fell between the cracks. The open
issue is what to do with lines greater than 80 columns... The
quoted-printable transfer encoding decodes to some pretty nasty long lines
in some cases. I'm tempted to simply word-wrap lines that don't begin with '>'.
|
|
Message has 1 Reply:
Message is in Reply To:
 | | quoted-printable support
|
| LUGNET does not correctly decode quoted-printable messages on the web interface. For example, look at: (URL) the brickshelf URL with the =3D in it. My newsreader displays it correctly, along with the other funny characters shown at the bottom, (...) (22 years ago, 16-May-03, to lugnet.admin.suggestions)
|
13 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
