[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] Status attribute
Hi Matteo I use the revision attribute in a very similar way to the case you describe. Simon Dew Technical Author | Stanley Security Solutions 1 Park Gate Close, Bredbury, Stockport SK6 2SZ, U.K. Simon.Dew@SBDInc.com | +44 (0) 161 406 3400 www.stanleysecuritysolutions.co.uk Registered Office: Stanley House, Bramble Road, Swindon Registered in England and Wales No. 181585 VAT No. 232 2446 95 On 24/06/2014 10:04, Matteo Regazzo wrote: > Dear Bob, > thank you for your prompt answer, I've read the link but I've not > reached the point... > We are just using the profiling of the standard stylesheets. > We already use the common attributes "vendor", "audience" and > "condition", and we use even "status" on the Book root declaration to > generate a manual with the "draft" watermark on the pages. > Our need is to implement a condition that allow us to decide if some > section, table, para, ... will be printed or not when the Book "status" > is "draft" or similar. > > Using the "condition" attribute, as you have suggested, I have to assign > to "condition" attribute different flags/strings with different meanings > (e.g. <para condition="green;draft">) it seems a not so clean solution. > Furthermore I have to pass the status condition to the command line > (e.g. -param profile.status=draft), but the status of the manual is > already declared in the source files themselves. > Is it possible to have a status condition, in each element of the book, > where the condition value depends on the status attribute of the book > root element? > > <book status="draft"> > ... > ... > <para ???="draft"> > This para is printed only in the draft version. > </para> > > <para ???="final"> > This para is printed only in the final version. > </para> > </book> > > What could I write instead of "???" ? > > Matteo R. > > Il 18/06/2014 19:39, Bob Stayton ha scritto: >> Hi Matteo, >> DocBook uses the term "profiling" to describe the process of filtering >> out certain elements based on attribute values. The DocBook schema >> provides several common attributes for that purpose, but as you >> discovered, @status is not "common" enough. >> >> The list of profiling attributes is described here: >> >> http://www.sagehill.net/docbookxsl/Profiling.html >> >> I might suggest @condition, which is a general purpose profiling >> attribute that you can adapt to your needs. >> >> BTW, you don't need a customization to implement profiling. The >> DocBook XSL distribution can profile just by setting values for the >> profiling parameters associated with the profiling attributes. That's >> all described in the doc reference above. >> >> Bob Stayton >> Sagehill Enterprises >> bobs@sagehill.net >> >> On 6/17/2014 8:16 AM, Matteo Regazzo wrote: >>> Hi everybody, >>> >>> I'm facing a problem with a customization... I want to inhibit the >>> presence of some object (such as rows, para, ...) in the generation of a >>> PDF document, and I was expecting that I could use the /_status="draft" >>> _/attribute, but it doesn't work. >>> I've discovered that from DocBook 4.5 it doesn't work as a common >>> attribute, but only for "book, chapter, ..." (maybe I can say only for >>> "macro"elements). >>> Which attribute may I use to obtain the same result? Or what else can >>> I do? >>> >>> Thank you since now, >>> Matteo R. >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org >> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.or > > --------------------------------------------------------------------- > To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]