From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0016_01C3933B.F7CE1EA0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Replace "browser" with "HTML viewer".  It's HTML. 
It's expressed as =
a comment for backward compatibility.  The same has been used in the = past
for other HTML constructs like script.

   None of this has anything to do with spam.  George made a bad =
assumption and failed to test these.  He has only himself to blame.

Rich

  "John Beamish"  wrote in message =
news:3f8dd908{at}w3.nls.net...
  Not a good example, Rich. =20

  The opening sentence on the page reads "One of the most common =
operations performed in a Web page is to detect the browser type and =
version. " =20

  George was talking about using Word for an email editor.  Web pages =
and email/spammail are hardly likely to be overlapping sets.

    "Rich"  wrote in message news:3f8da505$1{at}w3.nls.net...
       These are not comments to be read.  These are conditional =
comments =
(http://msdn.microsoft.com/workshop/author/dhtml/overview/ccomment_ovw.as=
p) and have meaning.

       You have only yourself to blame for deploying something you =
obviously did not test.

    Rich

      "Geo."  wrote in message =
news:3f8d9f59$1{at}w3.nls.net...

      Well Microsoft to the rescue.. All the idiots who use Word 10 as =
their email
      editor are now generating code with tons of comments like:

      
      
      
      
      
      
      
      
      

      I mean come on people, is anyone at Microsoft even thinking about =
how this
      affects things, do they WANT more spam? What are you guys =
thinking, someone
      actually reads the SOURCE besides email admins trying to filter =
the crap?

      Geo.


------=_NextPart_000_0016_01C3933B.F7CE1EA0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Replace
"browser" with =
"HTML=20
viewer".  It's HTML.  It's expressed as a comment
for backward =

compatibility.  The same has been used in the past for other
HTML=20 constructs like script.
 
   None of
this has anything =
to do with=20
spam.  George made a bad assumption and failed to test
these.  = He has=20
only himself to blame.
 
Rich
 

  "John Beamish" <abuse{at}aol.com>=20">mailto:abuse{at}aol.com">abuse{at}aol.com>=20
  wrote in message news:3f8dd908{at}w3.nls.net...
  Not a good
example, =
Rich. =20
  
   
  The
opening sentence on the =
page reads=20
  "One of the most common operations performed in a Web page is to =
detect the=20
  browser type and version. "  
   
  George was
talking about =
using Word for=20
  an email editor.  Web pages and email/spammail are hardly likely =
to be=20
  overlapping sets.
   
  

    "Rich" <{at}> wrote in message news:3f8da505$1{at}w3.nls.net...
       These
are not comments =
to be=20
    read.  These are conditional comments (http://msdn.microsoft.com/workshop/author/dhtml/overview/ccomment=
_ovw.asp">http://msdn.microsoft.com/workshop/author/dhtml/overview/ccomme=
nt_ovw.asp)=20
    and have meaning.
     
       You
have only yourself =
to blame=20
    for deploying something you obviously did not test.
     
    Rich
     
    
      "Geo." <fake{at}barkdom.com>=20">mailto:fake{at}barkdom.com">fake{at}barkdom.com>=20
      wrote in message news:3f8d9f59$1{at}w3.nls.net...Well=20
      Microsoft to the rescue.. All the idiots who use Word 10 as their=20
      emaileditor are now generating code with tons of comments=20
      like:<!--[if gte mso =
9]><![endif]--><!--[if=20
      gte mso
9]><![endif]--><!--[if=20
     
!mso]><![endif]--><!--[if
gte mso=20
     
10]><![endif]--><!--[if gte
mso =
9]>I mean=20
      come on people, is anyone at Microsoft even thinking about how=20
      thisaffects things, do they WANT more spam? What are you guys=20
      thinking, someoneactually reads the SOURCE besides email =
admins trying=20
      to filter the=20
crap?Geo.

------=_NextPart_000_0016_01C3933B.F7CE1EA0--

--- BBBS/NT v4.01 Flag-5