"John D. Wentzky" <johndwentzky@alumni.furman.edu> writes:

Ridiculous.

No, completely true

Wrong, again.

No true.

- otherwise you'd have known the difference between a content type
and a content transfer encoding.

Do what?

You didn't know the difference because you don't understand the
technology.

Since when can I not see those things in my newsreader options or in
the header information? Quoted printable was removed from one of
parsifals posts and was in there in many of them.

Aside from your turgid grammar, if your newsreader does not handle the
header properly, you should simply get a better newsreader.

Of course they are "tedious" - they are written for professionals
trying to actually implement something,

I know they are written by a self-regulating industry group.

You missed the point.

You forgot the point.

Idiot.

Which means you are unable to answer my question with definitively?

Look jerk,

Peeved already?

When I give you an answer and you ignore it and then claim I didn't
answer it, you should expect me to be a bit peeved.

the answer to your question was in what followed. If you
expect to get any help or explanation, you can ***** well try to
be polite or nobody will bother to help you.

But wasn't that speculation?

No, it wasn't.

So, is it the case that google self-imposes differing content
transfer
encodings on its own in some instances?

You'll have to ask Google, but many news readers do change the
content
transfer encoding when necessary. It is for a legitimate reason:
some
servers do not like email or news posts with lines longer than 76
characters and my wrap long lines. So, if you post something with
lines close to that limit (including text you merely quoted), Google
or a user's news reader may use a quoted-printable transfer encoding
to prevent that line wrap from occurring (it will break the line at
a
length of about 76 characters by inserting an '=' followed by a line
break, and the recipient is expected to know how to restore it. A
separate sequence is used at intended line breaks.

Ok, maybe that is what has occurred.
I know what you are telling me.

As people reply, and include old text in the post, the level of
indentation (the leading '>' characters) increases with each reply
so eventually lines will exceed 76 characters in length, and using
a quoted-printable encoding will allow those lines to be displayed
properly regardless of which server the post passes through.

Hmmm.
I wonder why google's system would be setup that way?

So your post won't be altered when it is forwarded through a server
that wraps long lines or otherwise can't handle them. That's what I
just told you. If you can't understand it, you should just accept it
as a fact.

Quoted printable screws up the trail on usenet but it is somehow secure?

It doesn't have any adverse effect on usenet, and it has nothing to do
with security. As was explained to you, your newsreader is simply
deficient.

Is this evidence of their failure to comply with newsgroup RFC
standards?

Sigh.

Just can't adapt to acceptable posting guidelines, huh? Too busy
trying to find another cam girl or computer porno lay to fix the
system?

Oh, so you make bogus statements about porn because you can't
understand the standards, nor that users do not explicitly pick
content transfer encodings.

The standards allow newsreaders (which google provides) and
news servers (which google provides) to pick a content transfer
encoding.

My newsreader allows ME to make choices.
Why isn't google's compliant with plain text ascii newsgroup posting
standards?

Sigh. "plain text" is a content type, not a content encoding, and a
content transfer encoding has nothing to do with which charset you
use (ASCII being simply one example).

Are you really sure that mr screwup the trail didn't intentionally use
quoted printable or are you just blowing smoke again to cover for your
bud?
Gotta have that last word syndrome getting parsfial down too much?
What does that say about his ability to conduct effective debate?

Look moron, as was explained to you, the content transfer encoding is
not set by users.

The one used is noted in the headers and it is then the
responsibility of the recipient to handle it correctly. The
quoted-printable content transfer encoding is one that appears in
the RFCs. Every news reader should know about it, including yours.
If it doesn't, replace it with one that works.

Sounds like parisfal donates to you. Gotta defend those clients,
huh? Or, do you pay him to sow ***** to cover for you?

Wentzky, ***** - I was nice enough to give you a simple explanation
of what is going on and instead of thanking me for the explanation,
you post lies, stupid insults, and conspiracy theories.