From: "Rich" 

This is a multi-part message in MIME format.

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

   Believe what you wish but this mechanism is codifiled in the HTML =
standard.  Comments allow for constructs that are to be ignored by =
implementations that don't support them.  If you think that backward =
compatibility is stupid, so be it.

Rich

  "Antti Kurenniemi"  wrote in message =
news:3f8e2d99$1{at}w3.nls.net...
  I don't agree with you on this one. Nothing inside a comment should =
make any
  damn difference if it is altered or taken out, so using comments as
  conditional identifiers is not only wrong but also very stupid, and =
bound to
  fail sooner or later.

  Antti Kurenniemi

  "Rich"  wrote in message news:3f8ddc7b$1{at}w3.nls.net...
     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.

    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. "

    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_00BF_01C3936F.E356DF00
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Believe
what you wish but =
this=20
mechanism is codifiled in the HTML standard.  Comments =
allow for=20
constructs that are to be ignored by implementations that don't support=20
them.  If you think that backward compatibility is stupid, so
be=20 it.
 
Rich
 

  "Antti Kurenniemi" <Antti{at}AnttiK.com>">mailto:Antti{at}AnttiK.com">Antti{at}AnttiK.com>
wrote in =
message news:3f8e2d99$1{at}w3.nls.net...I=20
  don't agree with you on this one. Nothing inside a comment should make =

  anydamn difference if it is altered or taken out, so using =
comments=20
  asconditional identifiers is not only wrong but also very stupid, =
and=20
  bound tofail sooner or later.Antti =
Kurenniemi"Rich"=20
  <{at}> wrote in message news:3f8ddc7b$1{at}w3.nls.net...=
  =20
  Replace "browser" with "HTML viewer".  It's
HTML.  It's =
expressed as=20
  acomment for backward compatibility.  The same has been used =
in the=20
  past forother HTML constructs like
script.   =
None of=20
  this has anything to do with spam.  George made a bad =
assumptionand=20
  failed to test these.  He has only himself to=20
  blame.Rich  "John
Beamish" <abuse{at}aol.com>">mailto:abuse{at}aol.com">abuse{at}aol.com>
wrote in =
messagenews:3f8dd908{at}w3.nls.net...&nbs=
p; Not=20
  a good example, Rich.  The opening sentence
on the page =
reads=20
  "One of the most common operationsperformed in a Web page is to =
detect the=20
  browser type and version. "  George was
talking about =
using Word=20
  for an email editor.  Web pages andemail/spammail are hardly =
likely=20
  to be overlapping sets.   
"Rich" <{at}> =
wrote in=20
  message news:3f8da505$1{at}w3.nls.net...=
      =20
  These are not comments to be 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)and=20
  have
meaning.      
You have =
only=20
  yourself to blame for deploying something you obviouslydid not=20
  test.    =
Rich     =20
  "Geo." <fake{at}barkdom.com>">mailto:fake{at}barkdom.com">fake{at}barkdom.com>
wrote in=20
  messagenews:3f8d9f59$1{at}w3.nls.net...=
     =20
  Well Microsoft to the rescue.. All the idiots who use Word 10 as=20
 
theiremail     
editor are now =
generating=20
  code with tons of comments
like:     
=

  <!--[if gte mso
9]>     =20
 
<![endif]-->     
<!--[if gte =
mso=20
  9]>     =20
 
<![endif]-->     
<!--[if=20
  !mso]>     =20
 
<![endif]-->     
<!--[if gte =
mso=20
  10]>     =20
 
<![endif]-->     
<!--[if gte =
mso=20
 
9]>     
I mean come on people, is =
anyone=20
  at Microsoft even thinking about =
howthis     =20
  affects things, do they WANT more spam? What are you guys=20
 
thinking,someone     
actually reads =
the=20
  SOURCE besides email admins trying to filter=20
 
thecrap?     =20
Geo.

------=_NextPart_000_00BF_01C3936F.E356DF00--

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