Re: Microsoft writing libs that produce bad markup (again) (was /

Thank you David , Great answers .
  Well I was told , by a search engine submission company I use that I should just use front page to write coding for pages as its universal in its applications.
  And yes Microsoft office live is vary limited in what it can and can not do as well.
  Oh well I think Ive done all can do with my web sites , Ive tryed to make pages that will work with all browsers on my test web site on office live , but still have errors with the V , its funny all the errors were in the programming I have no controll over.
  I my self wonder why microsoft is always sending me their surveys on what I think they need to do to fix their web sites and then dont do any thing I tell them to do.
  possibly I should just give up.
  Thanks again.

David Dorward <> wrote:
  On Tue, Jun 12, 2007 at 12:22:52PM -0700, Greg Sabin wrote:

> I was not able to get to make the validator work with
> Microsoft office live web sites.

If I remember rightly, the series of events was something like this:

* W3C produce a specification for HTML

* W3C and volunteers produce a tool to test against against various

* Microsoft produce a code library that generates HTML.

* You use that library to generate a webpage.

* You test that webpage against the aforementioned HTML specification,
and it doesn't conform.

I can't see how anyone would be impressed by Microsoft's contribution
to that chain of events, or how the people writing the testing tool
could do anything about it. The only fixes that I can see are:

(a) Microsoft fixing their libraries

(b) Someone writing a specification for the code generated by those
libraries, this should be Microsoft, since reverse engineering a black
box is unlikely to produce as good a result as the authors of a piece
of code documenting it themselves.

(c) Not using the libraries that generate the bad code

Option b, in my opinion would be the worst such option since, as far
as I know, the deviation from standard HTML do not provide any
benefits (so this would require all tools that consume HTML to be
updated or continue to depend on error recovery routines in exchange
for no additional features or solved problems).

> The validator is actually Vary limited in what it can and can not do

It is fairly limited, in the same way that a pencil is fairly
limited. It does a job and it does it well.

> , and when I asked I was told in no short terms that I should make
> my web site conform to the validator , rather then have the
> validator be able to read multiple formats on a single web site.

I think the problem was that you were using an undocumented
format. How can you test for conformance to something without knowing
what the 'something' is ?

> I have noticed many vary good looking web sites can not pass the
> test , possibly is only interested in diction and
> grammar verses real life applications , free thinking and or
> thinking out side of the box.

When one thinks outside the box, it is usually to provide some
tangible benefit. What benefits over standard HTML do Microsoft's
non-standard changes provide? If there is no benefit, it is simply
unnecessary complication that forces user agents to compensate for the
deviations from the specification (making them larger, slower and less

> It would seem the people at don't like Microsoft or their
> programming vary much.

The quality of their generated HTML code is less then good, but this
issue is not so much about not liking Microsoft as it is about a group
of mostly volunteers refusing to invest a good deal of their time into
cleaning up Microsoft's mess for them. Correction, not cleaning it up
- sweeping it under the carpet.

David Dorward

You snooze, you lose. Get messages ASAP with AutoCheck
 in the all-new Yahoo! Mail Beta. 

Received on Thursday, 14 June 2007 00:04:27 UTC