Re: Muggy, I'm Confused


Richard Bridgman wrote:
> mg (Google GOD) wrote:
> > Uncle Dave wrote:
> > > You bang on about Simon's posts not having any ">"s, which they do.
> > > But yours don't. Is that deliberate or are you actually - as I am
> > > beginning to suspect - actually attempting to communicate from another
> > > dimension?
> >
> > Hi David, thanks for raising this subject again, not. I had let it
> > slide because I was sick of it, as were a few lurkers who suggested the
> > discussion be taken elsewhere.
> >
> > The problem is not reading Simon's posts, but replying to them. This is
> > well documented online and without getting to technical the fault is
> > Google. And from what I've read the same thing happens with AOL and
> > their News port. You will see a simmilar behaviour when replying to
> > HTML posts.
> >
> > The problem starts with "Content-Transfer-Encoding: quoted-printable"
> > which you will see in the headers of Google posts.
> [snip]
>
> Bollocks, that's got nothing to do with it. Quoted-Printable
> Content-Transfer-Encoding is an encoding method designed to minimize
> mail transport modification. There are documented cases of problems
> associated with decoding messages encoded in QPCT (quite rare), and
> problems where news and mail readers have virus scanners that have
> issues with QPCT (more common).
>
> OK, pull up your chair, furrow your brow, concentrate hard and stick
> with me:
>
> Symptoms:
> 1. You are experiencing problems replying to Simon's posts, viz. when
> you reply to them there are no ">" marks when your reply is posted.
> 2. Other users can verify this, because when we view your replies, we
> can see that Simon's text is unquoted.
> 3. Furthermore, users viewing your reply in a variety of newsreaders
> (including GG) can also see that your replies do not contain ">" marks
> for the text you are replying to.
>
> Your diagnosis:
> 1. Google groups is the problem.
> 2. Messages posted through GG are in QPCT transport
>
> Problem:
> 1. If GG encoding was the problem, other OE users would experience the
> same problem as you. They don't, I just asked a colleague who uses OE
> (shudder) to reply to some QPCT posts. No problem.
> 2. Even *if* GG's encoding was the problem, what that really means is
> that OE is having difficulties decoding GG posts and encoding replies.
> Seeing as there is nothing wrong with GG's encoding (QPCT is widely in
> use not just by GG), then I would suggest the problem is with OE. Your
> suggestion that the issue is GG is like a man shot in the head saying
> he has no problem, and that the gun maker should fix his product
> because bits of lead are shooting out of it.
> 3. Occam's razor...you are the only one having the problem. Hint: look
> a little closer to home.
> 4. Search usenet. There are any number of discussions about OE not
> quoting properly. There is even a free fix available.
>
> Please let this drop. You cocked up, big deal. The situation however is
> irretrievable so lets just say no more about it. I will if you will.
>
> Honest.
>
> Richard Bridgman

wait for it - I feel another lame stab at trying to confuse people more
technically proficient than him coming on.

.

Loading