From owner-freebsd-doc@FreeBSD.ORG Tue Jan 20 16:13:05 2004 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B096E16A4CE for ; Tue, 20 Jan 2004 16:13:05 -0800 (PST) Received: from pi.codefab.com (pi.codefab.com [66.234.138.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 562C743D41 for ; Tue, 20 Jan 2004 16:13:03 -0800 (PST) (envelope-from chuck@pkix.net) Received: from [10.1.1.193] (nfw2.codefab.com [66.234.138.66]) by pi.codefab.com (8.12.10/8.12.10) with ESMTP id i0L0Cp0I067404 for ; Tue, 20 Jan 2004 19:12:51 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v609) Content-Transfer-Encoding: 7bit Message-Id: <8D03FA54-4BA6-11D8-8D97-003065ABFD92@pkix.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-doc@FreeBSD.org From: Chuck Swiger Date: Tue, 20 Jan 2004 19:12:50 -0500 X-Mailer: Apple Mail (2.609) X-Spam-Status: No, hits=0.0 required=6.0 tests=HTML_MESSAGE autolearn=no version=2.62 X-Spam-Checker-Version: SpamAssassin 2.62 (2004-01-11) on pi.codefab.com Subject: Validating docbook articles... X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2004 00:13:05 -0000 Hi, all-- I've noticed a few issues trying to validate HTML generated via the FreeBSD Docbook infrastructure, using the tools from W3C.org. While I noticed this checking on an article I'd written myself, the same issues I've noticed also seem to affect content like: http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/ Feeding that URL to the W3C validator (apologies for an URL that will wrap): http://validator.w3.org/check? uri=http%3A%2F%2Fwww.freebsd.org%2Fdoc%2Fen_US.ISO8859-1%2Fbooks%2Ffdp- primer%2F ...complains that no valid character encoding is present. How does one convince Docbook to place something like: ...into the section of the resulting XHTML, or else generate an XML declaration containing an encoding type in the document prolog? -- The W3C validator lets one override the character encoding, and doing so lets the tool proceed, but this uncovers another possible issue: Below are the results of attempting to parse this document with an SGML parser. 1. Line 618, column 15: value of attribute "align" cannot be "LEFT"; must be one of "left", "center", "right" (explain...).
The XHTML spec defines the attributes of the hr element as: ...so I'm willing to believe the W3C validator is right, and that Docbook should be generating these attribute values in lower case. This problem affects a number of other elements, such as img, h1-h6, and so forth which use the ImgAlign or TextAlign attributes. -- -Chuck PS: Yes, I know that elements and attribute names used to be case-insensitive, but section 4.2 of the XHTML spec says otherwise. And yes, I am picking nits. The question is, am I picking useful nits...? :-)