[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] html validator for docbook output
Hi Tristan, HTML is not XML, it is SGML. Since browsers are known to accept invalid HTML, there hasn't been much effort to ensure that all HTML generated by DocBook is valid SGML. In any case, you should not be getting that namespace prefix in your output. The stylesheet explicitly excludes that prefix from the output. Is there something in your customization layer that might be generating it? Can you provide a sample document and your processing method? Bob Stayton Sagehill Enterprises DocBook Consulting bobs@sagehill.net ----- Original Message ----- From: "Tristan Fiedler" <fiedler@cshl.edu> To: "Docbook-Apps" <docbook-apps@lists.oasis-open.org> Sent: Wednesday, June 01, 2005 11:50 AM Subject: [docbook-apps] html validator for docbook output Hi All, I am attempting to make my output html from Docbook xml compliant with w3c standards using http://validator.w3.org/ I have manually added the following to the beginning of the file, since this was the first error : <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd";> Am I choosing the wrong DocType perhaps? Is it possible to validate the HTML (not xhtml) output from DocBookXML conversion? I still get the following errors, which nearly all deal with namespaces. # Line 25, column 40: there is no attribute "XMLNS:SUWL" <sup xmlns:suwl="http://nwalsh.com/xslt/ext/com.nwalsh.s You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. ✉ # Line 30, column 34: there is no attribute "XMLNS:SUWL" <div xmlns:suwl="http://nwalsh.com/xslt/ext/com.nwalsh.saxon.U ✉ # Line 35, column 29: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag <p></p></span></span></div> The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element. One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>"). ✉ # Line 86, column 26: there is no attribute "XMLNS:SUWL" <p xmlns:suwl="http://nwalsh.com/xslt/ext/com.nwalsh.saxon.UnwrapLin ✉ # Line 94, column 145: there is no attribute "XMLNS:SUWL" ...izing the beta-catenin <a xmlns:suwl="http://nwalsh.com/xslt/ext/com.nwalsh.s Cheers, Tristan --- Tristan J. Fiedler Postdoctoral Fellow - Stein Lab Cold Spring Harbor Laboratory --------------------------------------------------------------------- To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]