Why bother with keeping your code up to date with what the W3C recommends? Don't! Please, put up bleeding-edge Web pages that take advantage of bugs in browsers. Contribute to the working anarchy we fondly call the Internet.
While I do not enjoy stylistic exploits that unknowingly (or even knowingly) create security holes, exploits that contribute to the art world -- even if they only last until everybody updates their browser to the next version -- are wonderful.
Pushing the boundaries of design is part of the Zen experience of the Web. However,
Thus far, you've read the HTML 4.01 and XHTML 1.0 documentation and you understand their relationship. You have successfully converted a few documents to XHTML 1.0. So, how do you know that your documents are really XHTML 1.0 compliant?
The easiest way, as stated earlier, is to use "xmllint." It was distributed with later versions of libxml, which can be obtained from xmlsoft.org. Once properly installed, you can use xmllint to check your work. Your command line entry will look like this:
xmllint --valid --noout mydoc.html
If you receive error
Why bother with keeping your code up to date with what the W3C recommends? Don't! Please, put up bleeding-edge Web pages that take advantage of bugs in browsers. Contribute to the working anarchy we fondly call the Internet.
While I do not enjoy stylistic exploits that unknowingly (or even knowingly) create security holes, exploits that contribute to the art world -- even if they only last until everybody updates their browser to the next version -- are wonderful.
Pushing the boundaries of design is part of the Zen experience of the Web. However,
Thus far, you've read the HTML 4.01 and XHTML 1.0 documentation and you understand their relationship. You have successfully converted a few documents to XHTML 1.0. So, how do you know that your documents are really XHTML 1.0 compliant?
The easiest way, as stated earlier, is to use "xmllint." It was distributed with later versions of libxml, which can be obtained from xmlsoft.org. Once properly installed, you can use xmllint to check your work. Your command line entry will look like this:
xmllint --valid --noout mydoc.html
If you receive error