Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 58463 invoked from network); 28 Oct 2004 07:45:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 28 Oct 2004 07:45:04 -0000 Received: (qmail 6556 invoked by uid 500); 28 Oct 2004 07:45:02 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 6499 invoked by uid 500); 28 Oct 2004 07:45:01 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@forrest.apache.org Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 6478 invoked by uid 99); 28 Oct 2004 07:45:00 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from [65.77.211.93] (HELO indexgeo.net) (65.77.211.93) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 28 Oct 2004 00:45:00 -0700 Received: from [192.168.1.100] (static-109.227.240.220.dsl.comindico.com.au [220.240.227.109]) (authenticated bits=0) by www2.kc.aoindustries.com (8.12.9-20030917/8.12.9) with ESMTP id i9S7istR030312 for ; Thu, 28 Oct 2004 02:44:56 -0500 Subject: Re: Catalog for Docbook Plugin From: David Crossley To: dev@forrest.apache.org In-Reply-To: <200410280905.52292.sean@inwords.co.za> References: <200410260917.15849.sean@inwords.co.za> <200410262022.05669.sean@inwords.co.za> <1098943288.22785.27492.camel@ighp> <200410280905.52292.sean@inwords.co.za> Content-Type: text/plain Organization: Message-Id: <1098949443.22785.27914.camel@ighp> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 28 Oct 2004 17:44:04 +1000 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Sean Wheller wrote: > David Crossley wrote: > > ARPINA? Google could not answer that one. > Typo, ARPITB. > > > > > I would if we should move Forrest's core catalog.xml > > up one directory level. Would that help with consistency? > > Is it worth making these changes. Remember its only a plug-in. Personally I > don't mind where it sits so long as we don't need to backward reference. I gather that by "backward reference" you mean stuff like ../../ > > What you have suggested below is interesting. I had not > > considered the use of rewriteSystem and rewriteURI > > (i will need to go look up the difference). In the core > > catalogs we mainly relied on PublicIdentifiers. This use > > of rewriteSystem is neat. > > > > However i don't understand the forrest.a.o/release/ URIs. > > We don't have such resources, so this would be confusing. > > They are fake. They don't point anywhere. But rewriteURI requires that the > uriStartString be a URI. file:///, /, http://, svn:// whatever. > > Would you prefer I change > uriStartString="http://forrest.apache.org/release/xsl/current/xhtml/" > to something else? Yes, i think so. Otherwise we will confuse people. > Looking at it I think I should change to just using a uri map. > > name="http://forrest.apache.org/release/xsl/current/xhtml-cust.xsl" > uri="custom/xhtml-cust.xsl"/> > > name="http://forrest.apache.org/release/xsl/current/fo-cust.xsl" > rewritePrefix="custom/fo-cust.xsl"/> > > To answer the question about rewriteSystem and rewriteURI. > Instead of having a large number of catalog entries I have used rewriteSystem > and rewriteURI to map the first part of the the reference to a different > prefix. This way I can map many files located in the same place with a single > catalog entry. It makes life easier, especially with the XSL's. People can > call different XSL's to do different things in Docbook e.g docbook.xsl for > normal transform, profile.xsl for transformations that are profiled. > chunk.xsl to get write a long document to many files. Yes that is good. Sorry to make you explain that. I should be more careful with words. I mean the difference between "rewriteSystem" and "rewriteURI", not between those and Public Identifiers. > I call the nextCatalog only to solve the PUBLIC ID's. Instead of writing them > into my own file as we have with catalog.xcat I just call them and use the > catalog of the package. This way, as an example, I just need to add one more > nextCatalog when Docbook 4.4 becomes official. Damn, crossed-wires again. Looking back at the example catalog that you showed, i wondered why you were using rewriteSystem for the DocBook DTDs and then *also* doing the nextCatalog. It would only need the latter. > Oh, and I can rewrite*** > prefixes to the local location. I considered doing this for catalog.xcat, but > decided to leave it. It ain't broken, so don't fix it. The Public Identifiers that we are currently using in our core catalogs work beautifully. --David > Documents will always use the standard DocTypeDecl.