From owner-freebsd-doc@FreeBSD.ORG Mon Feb 23 11:26:32 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 2569E16A4CE; Mon, 23 Feb 2004 11:26:32 -0800 (PST) Received: from out012.verizon.net (out012pub.verizon.net [206.46.170.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9ACB43D1F; Mon, 23 Feb 2004 11:26:31 -0800 (PST) (envelope-from cswiger@mac.com) Received: from mac.com ([68.160.202.196]) by out012.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040223192630.CVAI1590.out012.verizon.net@mac.com>; Mon, 23 Feb 2004 13:26:30 -0600 Message-ID: <403A53E1.2040305@mac.com> Date: Mon, 23 Feb 2004 14:26:25 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <8D03FA54-4BA6-11D8-8D97-003065ABFD92@pkix.net> <20040216130659.GC617@submonkey.net> <4031364A.2070708@pkix.net> <20040222181114.GB32524@graf.pompo.net> <40390248.1060104@pkix.net> <4039D0FE.3010905@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Authentication-Info: Submitted using SMTP AUTH at out012.verizon.net from [68.160.202.196] at Mon, 23 Feb 2004 13:26:30 -0600 cc: freebsd-doc@FreeBSD.org cc: Thierry Thomas cc: Alex Dupre Subject: Re: 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: Mon, 23 Feb 2004 19:26:32 -0000 Dag-Erling Smørgrav wrote: > Alex Dupre writes: >> [ ...talking about -preserve in tidy... ] > This reminds me of the many good reasons to convert the doc tree to > XML. One of these is that xmllint can both validate input files and > clean up output files, and it does a far better job of it than tidy. An interesting idea. I took a quick look at converting an existing SGML document into XML in order to gain some idea as to the work involved. Given an SGML prologue of: %man; %freebsd; %trademarks; ]> ...from doc/en_US.ISO8859-1/articles/filtering-bridges (written by ale@, of course :-), it's easy to add an XML prologue-- this could be done automaticly-- and "make lint" works just fine with an XML declaration in place. So far, so good. How does one generate proper SystemLiterals per: |4.2.2 External Entities | |[Definition: If the entity is not internal, it is an external entity, |declared as follows:] | |External Entity Declaration | |[75] ExternalID ::= 'SYSTEM' S SystemLiteral | | 'PUBLIC' S PubidLiteral S SystemLiteral 69-sec% xmllint article.sgml article.sgml:3: parser error : SystemLiteral " or ' expected ^ article.sgml:4: parser error : SystemLiteral " or ' expected ^ article.sgml:4: parser error : SYSTEM or PUBLIC, the URI is missing ^ article.sgml:5: parser warning : PEReference: %man; not found %man; ^ [ ... ] Are these entities published via a URI, or does one need to refer to a local path? Is there a tool to update (normalize?) these ENTITY declarations automaticly, as using "xmllint --catalogs --loaddtd" didn't seem to help? Maybe this seems trivial, but there are several hundred SGML source files which would all need to be updated this way... -- -Chuck