From: Hugo van der Kooij <hvdkooij@vanderkooij.org>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: SGML processing description
Date: Fri, 20 Dec 2002 19:23:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0201311257560.32387-100000@ultra1.hugo.vanderkooij.org> (raw)
Hi,
For those that seek a way to process their DocBook SGML documents and
influence the HTML output I have made a description of my own setup.
You can read it on: http://hvdkooij.xs4all.nl/docs-docbook.cms
Sample output can be found on my own site and the nessus faq
(http://www.nessus.org/doc/faq.html) which uses it's own set of HTML
wrapper files.
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@sourceware.cygnus.com
Subject: SGML processing description
Date: Thu, 31 Jan 2002 03:58:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0201311257560.32387-100000@ultra1.hugo.vanderkooij.org> (raw)
Message-ID: <20020131035800.O8mh0zKY-wwuRExheva0eq4kzclFzqBrLqPQapZ7kqU@z> (raw)
Hi,
For those that seek a way to process their DocBook SGML documents and
influence the HTML output I have made a description of my own setup.
You can read it on: http://hvdkooij.xs4all.nl/docs-docbook.cms
Sample output can be found on my own site and the nessus faq
(http://www.nessus.org/doc/faq.html) which uses it's own set of HTML
wrapper files.
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 reply other threads:[~2002-01-31 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 19:23 Hugo van der Kooij [this message]
2002-01-31 3:58 ` 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.0201311257560.32387-100000@ultra1.hugo.vanderkooij.org \
--to=hvdkooij@vanderkooij.org \
--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).