[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] conditional from source
I would look into using text entities for the keybindings. Then you would just need to substitute a different set of entity declarations for each different flavor of output. You could use different XML catalog files to select a different entity declaration file at runtime. Let me know if you need more explanation. Bob Stayton Sagehill Enterprises DocBook Consulting bobs@sagehill.net ----- Original Message ----- From: "Aaron" <aamehl@actcom.net.il> To: <docbook-apps@lists.oasis-open.org> Sent: Thursday, March 30, 2006 10:35 AM Subject: [docbook-apps] conditional from source > Hi all, > > I have the following problem: > > I am writing a manual for Denemo in docbook. > Denemo has a lot of keybindings and the ability to use > different > keybinding files as well. > > > I wrote a manual using one keybinding file, but it won't be > much use > to someone using a different keybinding file. > > > We came up with the idea of a script that will search the > manual for > some element or attribute or code to search for to replace the > key > bindings depending on the keybinding file used. > > For building the script I have someone, but the question is how > to > markup the manual in a way where the xml will parse and it > will be > fairly easy to tag. > > This isn't really conditional text, but maybe it would be part > of the > solution? > > Any suggestions would be most appreciated. > > Thanks > Aaron > > --------------------------------------------------------------------- > 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]