From: Tim Waugh <twaugh@redhat.com>
To: Peter Toft <pto@sslug.dk>
Cc: Norman Walsh <ndw@nwalsh.com>, 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: <20020702231711.I8943@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207022241150.1603-100000@ven.sslug>; from pto@sslug.dk on Tue, Jul 02, 2002 at 10:47:57PM +0200
[-- Attachment #1: Type: text/plain, Size: 392 bytes --]
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.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
WARNING: multiple messages have this Message-ID
From: Tim Waugh <twaugh@redhat.com>
To: Peter Toft <pto@sslug.dk>
Cc: Norman Walsh <ndw@nwalsh.com>, docbook-tools-discuss@sources.redhat.com
Subject: Re: Any luck with DocBook/SGML 3.1 with Red Hat 7.3?
Date: Tue, 02 Jul 2002 15:17:00 -0000 [thread overview]
Message-ID: <20020702231711.I8943@redhat.com> (raw)
Message-ID: <20020702151700.igmps7DxuzRqBy7TDt94fxrj3SF8_nvmInIaQfPienM@z> (raw)
In-Reply-To: <Pine.LNX.4.44.0207022241150.1603-100000@ven.sslug>; from pto@sslug.dk on Tue, Jul 02, 2002 at 10:47:57PM +0200
[-- Attachment #1: Type: text/plain, Size: 392 bytes --]
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.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-07-02 22:17 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 ` 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 [this message]
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
2002-07-03 14:04 ` Hugo van der Kooij
2002-12-20 19:23 ` Éric Bischoff
2002-07-01 0:49 ` Éric Bischoff
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 ` Eric S. Raymond
2002-07-03 0:19 ` Eric S. Raymond
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=20020702231711.I8943@redhat.com \
--to=twaugh@redhat.com \
--cc=docbook-tools-discuss@sources.redhat.com \
--cc=ndw@nwalsh.com \
--cc=pto@sslug.dk \
/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).