On Mon, 28 May 2007 11:51:32 -0500, "Neil Gould" wrote in
:

Recently, Jose posted:

Notice that I also modified the subject to include
a couple more colons, which, as you can see, were posted correctly.

That's not the bug. The bug (and I don't know if OE has it) is that
when a subject line is automatically processed, the automatic
processing strips incorrectly.

I am using Netscape 7.2. It does not have this bug. However, I am
noticing it has a different bug. Everything to the =right= of the
second colon has been stripped. Interesting.

Actually, that might even be the intended operation, since what was to
the right was the "(was..." and maybe the program is stripping that
away to complete the transition to the intended new subject line.

Curiouser and curiouser. I really wish the documentation would
indicate just =what= is supposed to happen.

That *is* interesting.

I don't know that I'd call these "bugs", if they are working as originally
intended. Perhaps the reasons for executing these actions don't match the
expectations of the user, but that is a somewhat different matter.

The moral of the story is not to use colons as punctuation
in a subject line IF you care about what happens to it later
as it passes through the hands of various and sundry
newsreaders.

Google was also swallowing up square brackets last time I checked
(five or six months ago), so tags like [OT], [META], [FA], etc.,
don't show up in the archive the way they did on first reading
from my NSP.

I'm not saying anyone has to care ...

Marty
--
Big-8 newsgroups: humanities.*, misc.*, news.*, rec.*, sci.*, soc.*, talk.*
See http://www.big-8.org for info on how to add or remove newsgroups.