Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@www.apache.org Received: (qmail 90997 invoked from network); 7 Nov 2003 16:23:22 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 7 Nov 2003 16:23:22 -0000 Received: (qmail 90816 invoked by uid 500); 7 Nov 2003 16:23:14 -0000 Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 90761 invoked by uid 500); 7 Nov 2003 16:23:14 -0000 Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 90740 invoked from network); 7 Nov 2003 16:23:14 -0000 Received: from unknown (HELO moutng.kundenserver.de) (212.227.126.183) by daedalus.apache.org with SMTP; 7 Nov 2003 16:23:14 -0000 Received: from [212.227.126.161] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1AI9OF-0005IN-00; Fri, 07 Nov 2003 17:23:15 +0100 Received: from [217.22.155.67] (helo=taggart) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1AI9OE-0004ym-00; Fri, 07 Nov 2003 17:23:14 +0100 From: "Neil Tait" To: , Subject: RE: Extending Document v1.2 Date: Fri, 7 Nov 2003 16:23:29 -0000 Message-ID: <000c01c3a54b$7d88bf70$1401a8c0@taggart> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi Nicola, Thank you for your reply, I understand that the source should only = present the information, and not be concerned with the presentation. Its = just that our needs extend beyond only the one style for fonts (for = example). I think we shall look at importing the doc v1.2 dtd into one that = supports our own defined tags, that can then be output and styled = accordingly. Does this seem like a sensible approach? Kind regards, Neil=20 Neil Tait=20 - Software Engineer - =20 =20 TecSphere Limited Centre for Advanced Industry Coble Dene, Royal Quays Newcastle Upon Tyne NE29 6DE United Kingdom =20 Direct Dial: +44 (191) 270 31 13=20 Fax: +44 (191) 270 31 09 E-mail: neil.tait@tecsphere.co.uk=20 Web: www.tecsphere.co.uk =20 -----Original Message----- From: news [mailto:news@sea.gmane.org] On Behalf Of Nicola Ken Barozzi Sent: 07 November 2003 10:29 To: forrest-dev@xml.apache.org Subject: Re: Extending Document v1.2 Neil Tait wrote: > Hello >=20 > Has anyone made any attempts to extend the document v1.2 DTD? Forrest=20 > seems ideal for a project of ours, but a bit light on the style = vocabulary. The style vocabulary should tend to 0 for us, as content (the source)=20 should only present the information, not how to present it. So if you have a problem in how to output things, you can have the=20 necessity of using a custom DTD and/or a custom skin, as described in=20 the Forrest docs. What are the things that you miss? --=20 Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) ---------------------------------------------------------------------