Re: Are self-sealing tires good?



On Sun, 18 Nov 2007 13:29:13 -0700, carlfogel@xxxxxxxxxxx wrote:

On Sun, 18 Nov 2007 14:25:45 -0600, A Muzi <am@xxxxxxxxxxxxxxxx>
wrote:

A Muzi <a...@xxxxxxxxxxxxxxxx> wrote:
In my email and replies, it displays normally. Sometimes on r.b.t. it
looks weird with sketchy line breaks. But not always.
--
Andrew Muziwww.yellowjersey.org
Open every day since 1 April, 1971

carlfo...@xxxxxxxxxxx wrote:
Your signature appears normally when you first post or reply to
someone else.

When another poster replies to your post, Google tacks the leading
greater-than sign onto the front of your lines and reformats them.

In the process, it can wrap lines, mistakenly jamming the word at the
end of a line together with the link that begins the next line.

Both of these should appear normally in _this_ post:

Andrew Muziwww.yellowjersey.org

Andrew Muzi
www.yellowjersey.org

Andrew Muzi

www.yellowjersey.org
But when I reply to myself in a moment, the first may be wrapped,
while the other two (I hope) will be protected by the leading spaces
and the extra line.

carlfogel@xxxxxxxxxxx wrote:
See? That's why I put the ugly little space in front of links in my
posts. It leads to extra blank lines, but it prevents Google from
goofing up the links that are practically the only valuable things in
my ravings.

I added spaces to my sig file.
Why should Google affect this? I never go there.

Dear Andrew,

It isn't your original non-Google post that gets goofed up.

Things go wrong when someone else using Google replies to your
original post, which Google re-formats with the leading greater-than
signs and other fuss.

It may also get goofed up when going through _other_ sites, not just
Google.

Let's see what happens when Comcast gets its hands on things. Here are
the three versions again, the first one that Google wraps together
onto one line in replies, the second with leading spaces and the third
with a blank line in the middle to foikl Google:

Andrew Muzi
www.yellowjersey.org

Andrew Muzi
www.yellowjersey.org

Andrew Muzi

www.yellowjersey.org

I'll reply in a moment through Comcast and Forte Agent again.

Cheers,

Carl Fogel

Yes, replying through Comcast with Forte avoids the Google line-wrap
reply goof in the first example above.

Given that Google is free and maintains an enormous searchable
archive, it's hard to complain about this bug.

Luckily, no complaints are too hard or too small for RBT.

:-)

It looks as if you need to stick a bridge in there to keep your name
and site separated. Otherwise, the unbraced text can collapse and jam
things together in rare circumstances.

:-)

Cheers,

Carl Fogel
.



Relevant Pages

  • Re: apt-get install synaptic / sources.list
    ... to many that some users don't bother _READING_ anywhere. ... Google is your friend, as is browsing the archives of the mailing list. ... Andrew I'm sure you get a lot of threads where people haven't bothered looking. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". ...
    (Debian-User)
  • Re: Are self-sealing tires good?
    ... Andrew Muziwww.yellowjersey.org ... When another poster replies to your post, Google tacks the leading ... Andrew Muzi ...
    (rec.bicycles.tech)
  • Re: OT..Public email to Andrew .a little long
    ... Why not try a google. ... It is my email that I sent to andrew the other day. ... It's the private email that I sent to ... that I was a racist and bigot this might now have made google's 1st page. ...
    (alt.vacation.las-vegas)
  • Re: Road Test
    ... Andrew Muziwww.yellowjersey.org ... preceding blank line. ... Replying through Google Groups provokes the bug. ...
    (rec.bicycles.tech)
  • Re: Are self-sealing tires good?
    ... Andrew Muziwww.yellowjersey.org ... When another poster replies to your post, Google tacks the leading ... Andrew Muzi ...
    (rec.bicycles.tech)