public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Peter Toft <pto@sslug.dk>
To: Norman Walsh <ndw@nwalsh.com>
Cc: Tim Waugh <twaugh@redhat.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 13:48:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0207022241150.1603-100000@ven.sslug> (raw)
Message-ID: <20020702134800.I2zXshaJxDy2rzmZ3kK1opTTli16T9qJnG1lJ32tGqs@z> (raw)
In-Reply-To: <873cv21jst.fsf@nwalsh.com>

On Tue, 2 Jul 2002, Norman Walsh wrote:

> / Peter Toft <pto@sslug.dk> was heard to say:
> |> The default value for %use-id-as-filename% is false.  Turn it back on
> |> if you like, in a custom stylesheet.
> |
> | Well - or directly in the 
> | /usr/share/sgml/docbook/dsssl-stylesheets-1.76/html/dbparam.dsl
> | (I can't really see why this is so bad.)
> 
> Because when you update to 1.77, your modification will get blown away.

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).

> 
> | Actually - I just tried it and found that I still find 
> | all my html-files named x1182.html etc.
> 
> Are you sure your chunks have IDs. The IDs have to be on the chunk
> elements (article, chapter, section, etc.) not the titles.

Sure thing - all <chapter> <sect1> <sect2> etc. has 
id="ID" added. e.g.  <chapter id="introduction">

Best

-- 
Peter Toft, Ph.D. [pto@sslug.dk] http://www.sslug.dk/~pto

"Unix? What's that? Is that like Linux?"

  parent reply	other threads:[~2002-07-02 20:48 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 [this message]
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
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.0207022241150.1603-100000@ven.sslug \
    --to=pto@sslug.dk \
    --cc=docbook-tools-discuss@sources.redhat.com \
    --cc=ndw@nwalsh.com \
    --cc=twaugh@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).