From user-return-1128-apmail-forrest-user-archive=forrest.apache.org@forrest.apache.org Fri Nov 05 15:35:30 2004 Return-Path: Delivered-To: apmail-forrest-user-archive@www.apache.org Received: (qmail 46922 invoked from network); 5 Nov 2004 15:35:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 5 Nov 2004 15:35:29 -0000 Received: (qmail 31778 invoked by uid 500); 5 Nov 2004 15:35:21 -0000 Delivered-To: apmail-forrest-user-archive@forrest.apache.org Received: (qmail 31489 invoked by uid 500); 5 Nov 2004 15:35:18 -0000 Mailing-List: contact user-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: user@forrest.apache.org Delivered-To: mailing list user@forrest.apache.org Received: (qmail 31437 invoked by uid 99); 5 Nov 2004 15:35:18 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [65.104.121.53] (HELO mail.medata.com) (65.104.121.53) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 05 Nov 2004 07:35:15 -0800 Received: from [172.24.2.66] ([172.24.2.66]) (authenticated bits=0) by mail.medata.com (8.12.8/8.12.8) with ESMTP id iA5FZ991030073 for ; Fri, 5 Nov 2004 07:35:09 -0800 Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <1099643794.22785.83170.camel@ighp> References: <200411050635.iA56Z39r045968@oakgrovesystems.com> <1099643794.22785.83170.camel@ighp> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <465550C9-2F40-11D9-AB7D-00039385397E@medata.com> Content-Transfer-Encoding: 7bit From: Clay Leeds Subject: Re: Howto: "macros" in xdocs? Date: Fri, 5 Nov 2004 07:35:08 -0800 To: user@forrest.apache.org X-Mailer: Apple Mail (2.619) X-Virus-Scanned: ClamAV 0.80rc4/532/Fri Oct 15 11:22:57 2004 clamav-milter version 0.80j on mail.medata.com X-Virus-Status: Clean X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Nov 5, 2004, at 12:36 AM, David Crossley wrote: >> We're building a product documentation site with Forrest. We want to >> define >> site-wide "macros", like ${product-version} and ${release-date}, that >> can be >> inserted in individual content\xdocs\* files and replaced by >> corresponding >> literal values, like "6.0.1", at render time. >> >> What's the easiest way to do this with Forrest? > > We have been discussing such a need on the development list. > http://marc.theaimsgroup.com/?l=forrest-dev&r=4&b=200410 > http://marc.theaimsgroup.com/?l=forrest-dev&m=109895958631116 > > I don't want to get into too much tech discussion > on this "user" list. > > One potential solution would be to use xml entities. > Each project could define a text file with entity > definitions ... > > ------ > > > ... > ------ > > Then you use then in your XML instances like > this ... &project-name; > and maybe even use them in stylesheets too. Not sure yet. > > There would be a project-based set and a Forrest main set. For completeness-sake, where would such ENTITY definitions be placed? Could they go in forrest.properties or skinconf.xml? The forrest.properties file already has many of these, so that makes sense to me. Web Maestro Clay -- Clay Leeds - Webmaster/Developer - Medata, Inc. - PGP Public Key: