From: Hugo van der Kooij <hvdkooij@vanderkooij.org>
To: docbook-tools-discuss@sources.redhat.com
Subject: Re: Any luck with DocBook/SGML 3.1 with Red Hat 7.3?
Date: Fri, 20 Dec 2002 19:23:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0207032300290.9740-100000@ultra1.hugo.vanderkooij.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0207032245300.1366-100000@ven.sslug>
On Wed, 3 Jul 2002, Peter Toft wrote:
> On Tue, 2 Jul 2002, Tim Waugh wrote:
>
> > On Tue, Jul 02, 2002 at 10:47:57PM +0200, Peter Toft wrote:
> >
> > > Acknowledged!
> > > What is the simplest way to set the
> > > %use-id-as-filename% to true then? I do not know how to
> > > make a custom stylesheet (yet).
> >
> > Other than a custom stylesheet, use '-V %use-id-as-filename%'. The -V
> > option was added to docbook-utils in 0.6.10. (It just gets passed
> > through to openjade.)
> >
> > Tim.
>
> While we are at it....
>
> Assume that I have a set of these variables that I want
> to change - some could be common, some HTML-specific
> others print-specific. I suppose that there is a way
> that I could have a local "stylesheet" where I set e.g.
> %use-id-as-filename% to t
> %stylesheet% "/mystylesheet.css"
> %paper-type% "A4"
> Is this possible - how - can it be be done?
I guess you like to customize your output a bit to match your site as
well. All of this can be done.
I actually described that paces it took me to get things going. And I use
it to bend the html output a lot to fit into different sites.
Just compare these two links created from the same SGML DocBook source:
http://hvdkooij.xs4all.nl/docs/Nessus-FAQ.html
http://www.nessus.org/doc/faq.html
The steps I took are written down on:
http://hvdkooij.xs4all.nl/docs-docbook.cms
I hope that helps.
Hugo.
--
All email send to me is bound to the rules described on my homepage.
hvdkooij@vanderkooij.org http://hvdkooij.xs4all.nl/
Don't meddle in the affairs of sysadmins,
for they are subtle and quick to anger.
WARNING: multiple messages have this Message-ID
From: Hugo van der Kooij <hvdkooij@vanderkooij.org>
To: docbook-tools-discuss@sources.redhat.com
Subject: Re: Any luck with DocBook/SGML 3.1 with Red Hat 7.3?
Date: Wed, 03 Jul 2002 14:04:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0207032300290.9740-100000@ultra1.hugo.vanderkooij.org> (raw)
Message-ID: <20020703140400.P9LQGCI8NorgW-1HzU_gpPDyzODCgwsvC8agCWiKIAA@z> (raw)
In-Reply-To: <Pine.LNX.4.44.0207032245300.1366-100000@ven.sslug>
On Wed, 3 Jul 2002, Peter Toft wrote:
> On Tue, 2 Jul 2002, Tim Waugh wrote:
>
> > On Tue, Jul 02, 2002 at 10:47:57PM +0200, Peter Toft wrote:
> >
> > > Acknowledged!
> > > What is the simplest way to set the
> > > %use-id-as-filename% to true then? I do not know how to
> > > make a custom stylesheet (yet).
> >
> > Other than a custom stylesheet, use '-V %use-id-as-filename%'. The -V
> > option was added to docbook-utils in 0.6.10. (It just gets passed
> > through to openjade.)
> >
> > Tim.
>
> While we are at it....
>
> Assume that I have a set of these variables that I want
> to change - some could be common, some HTML-specific
> others print-specific. I suppose that there is a way
> that I could have a local "stylesheet" where I set e.g.
> %use-id-as-filename% to t
> %stylesheet% "/mystylesheet.css"
> %paper-type% "A4"
> Is this possible - how - can it be be done?
I guess you like to customize your output a bit to match your site as
well. All of this can be done.
I actually described that paces it took me to get things going. And I use
it to bend the html output a lot to fit into different sites.
Just compare these two links created from the same SGML DocBook source:
http://hvdkooij.xs4all.nl/docs/Nessus-FAQ.html
http://www.nessus.org/doc/faq.html
The steps I took are written down on:
http://hvdkooij.xs4all.nl/docs-docbook.cms
I hope that helps.
Hugo.
--
All email send to me is bound to the rules described on my homepage.
hvdkooij@vanderkooij.org http://hvdkooij.xs4all.nl/
Don't meddle in the affairs of sysadmins,
for they are subtle and quick to anger.
next prev parent reply other threads:[~2002-07-03 21:04 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 19:23 Peter Toft
2002-06-30 13:21 ` Peter Toft
2002-12-20 19:23 ` Tim Waugh
2002-06-30 14:02 ` Tim Waugh
2002-12-20 19:23 ` Éric Bischoff
2002-07-01 0:49 ` Éric Bischoff
2002-12-20 19:23 ` Eric S. Raymond
2002-07-03 0:19 ` Eric S. Raymond
2002-12-20 19:23 ` Tim Waugh
2002-07-01 1:13 ` Tim Waugh
2002-12-20 19:23 ` Ismael Olea
2002-07-03 4:07 ` Ismael Olea
2002-12-20 19:23 ` Tim Waugh
2002-07-03 4:59 ` Tim Waugh
2002-12-20 19:23 ` Peter Toft
2002-07-01 14:22 ` Peter Toft
2002-12-20 19:23 ` Norman Walsh
2002-07-02 3:55 ` Norman Walsh
2002-12-20 19:23 ` Peter Toft
2002-07-02 13:48 ` Peter Toft
2002-12-20 19:23 ` Hugo van der Kooij
2002-07-03 13:59 ` Hugo van der Kooij
2002-12-20 19:23 ` Peter Toft
2002-07-03 14:01 ` Peter Toft
2002-12-20 19:23 ` Tim Waugh
2002-07-02 15:17 ` Tim Waugh
2002-12-20 19:23 ` Peter Toft
2002-07-03 13:50 ` Peter Toft
2002-12-20 19:23 ` Tim Waugh
2002-07-03 14:52 ` Tim Waugh
2002-12-20 19:23 ` Éric Bischoff
2002-07-03 21:16 ` Éric Bischoff
2002-12-20 19:23 ` Tim Waugh
2002-07-03 23:33 ` Tim Waugh
2002-12-20 19:23 ` Éric Bischoff
2002-07-04 2:51 ` Éric Bischoff
2002-12-20 19:23 ` Hugo van der Kooij [this message]
2002-07-03 14:04 ` Hugo van der Kooij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0207032300290.9740-100000@ultra1.hugo.vanderkooij.org \
--to=hvdkooij@vanderkooij.org \
--cc=docbook-tools-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).