>>>>Hilmar,
>>>>You should read this site, especially point #4
>>>>
>>>>http://www.opera.com/pressreleases/20011101.html
>>>>
>>>>JLK
>>>
>>>That's an interesting article. I am sure Michel isn't involved in this plot, but it would be interesting, all the same, to check the UT against validator.w3.org. While I don't develop Web pages, it seems that some of the corrections suggested are actually quite easy to implement.
>>>
>>>In fact, I'll put this on the Task List right now.
>>>
>>>Hilmar.
>>
>>I don't believe for a second that Michel is envolved either. But, it's hard to create a W#C compliant web page when the tools you use are designed not to be complient by utilizing platform dependent controls, etc...
>
>Oh, well, I didn't think about that. Probably includes some tools from Microsoft. OTOH, it DOES cost some additional work to ensure cross-platform compatibility.

Not really. That's what the W3C standards are for. Just following those standards is easier than breaking them with 3rd party functionality, deliberately designed to embrace, extend and extinquish compilant applications. Easier because 3rd party tools are well known for producing "upgrades" with builtin incompatibilities designed to force the consumer to follow by rendering previous apps unreadable with the new release, and simulataneously shutting down sales and support of the previous release. For example, while designing a webpage with FrontPage may be easier, it locks one into the WinXX platform and the never-ending upgrade treadmill. If one used an HTML editor that designed W3C compliant pages, like Quanta+, that problem is never encountered, nor is the expense.
JLK