[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: DOCBOOK-APPS: Strategies & Tips Sought for Single Sourcing w/DocBook
Hi list... ... I intend to do a similar thing but after reading some of the Definitve Guide and Learning XML (both O'Reilly), I concluded that I was better off introducing a customization layer with special attributes (not that I knew right now how to any of this ;-))... Does anyone have any hints on advantages and drawbacks of either approach? I would prefer 'the XML way', though. Thanks a lot for bearing with all of us beginners, Peter. P.S.: Just FYI, currently, all docs that we produce are in Word97 format, and new editions are to be made by copying a .doc file and editing that (please don't comment on this, I know it's a brilliant approach). To change that and get 'official' support inside the company, I want to show XML 'effectiveness' on a document (probably read: set of documents) that describes a particular system on a more or less high level with the variations/customizations of the system due to customer requirements contained in the same document. --- Peter Cornelius Customer Training ATC COMSOFT GmbH email: cornelius@comsoft.de Wachhausstr. 5a phone: +49 721 9497 160 D-76227 Karlsruhe fax: +49 721 9497 129 Germany http://www.comsoft.de > -----Original Message----- > From: Jirka Kosek [mailto:jirka@kosek.cz] > Sent: Monday, October 01, 2001 9:42 AM > To: Megan Golding; docbook-apps@lists.oasis-open.org > Subject: Re: DOCBOOK-APPS: Strategies & Tips Sought for > Single Sourcing w/DocBook > > > Megan Golding wrote: > > > Is "role" the way to go for including/excluding text? How > do I modify my > > You can use role as it is general purpose extension attribute. It is > also possible to use attriutes "userlevel", "arch" or "os" to store > profiling information. > > > DSSSL to inclue all elements with no role and include > elements with only > > a specific role (bob, for example) but not elements of > other roles (joe, > > for example)? > > It is possible but you came in big troubles when included/excluded > elements are part of ToC or automaticaly numbered (figure, section and > so on). > > The reliable and easy to use way is in first step create new document > only with included elements and in second apply common > stylesheet on it. > You can download XSL stylesheets, there is stylesheet > tools/profile/profile.xsl which is able to include/exclude elements > based on content of any attribute. The result taken from this > stylesheet > can be then processed by DSSSL stylesheets. > > Documentation for profiling stylesheet can be found at > > http://docbook.sourceforge.net/projects/xsl/doc/tools/profiling.html > > Jirka > > ----------------------------------------------------------------- > Jirka Kosek > e-mail: jirka@kosek.cz > http://www.kosek.cz > > ---------------------------------------------------------------- > To subscribe or unsubscribe from this elist use the subscription > manager: <http://lists.oasis-open.org/ob/adm.pl> >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC