public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Peter Toft <pto@sslug.dk>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: SGML -> HTML split level
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0007161140260.31506-100000@laptop.linus.dk> (raw)

When I use db2html to compile SGML->HTML it will
generate a new HTML file for each <sect1>.

Where can I control it so that the split is done at
each new <sect2> or <sect3>? (this is a global
setting)

System: Linux Red Hat 6.2 - SGML docbook

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

"You don't win a battle by asking, `Will we win?' 
You win it by doing your best to win"
- Richard M Stallman

----> Visit http://petition.eurolinux.org <---


WARNING: multiple messages have this Message-ID
From: Peter Toft <pto@sslug.dk>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: SGML -> HTML split level
Date: Sun, 16 Jul 2000 02:47:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0007161140260.31506-100000@laptop.linus.dk> (raw)
Message-ID: <20000716024700.C5fKeUrmk3BY367B1lAUpXG7yYcDu10uu1reOeTzyw4@z> (raw)

When I use db2html to compile SGML->HTML it will
generate a new HTML file for each <sect1>.

Where can I control it so that the split is done at
each new <sect2> or <sect3>? (this is a global
setting)

System: Linux Red Hat 6.2 - SGML docbook

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

"You don't win a battle by asking, `Will we win?' 
You win it by doing your best to win"
- Richard M Stallman

----> Visit http://petition.eurolinux.org <---


             reply	other threads:[~2000-12-27  6:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 Peter Toft [this message]
2000-07-16  2:47 ` Peter Toft
2000-12-27  6:36 ` Norman Walsh

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.21.0007161140260.31506-100000@laptop.linus.dk \
    --to=pto@sslug.dk \
    --cc=docbook-tools-discuss@sourceware.cygnus.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).