public inbox for
 help / color / mirror / Atom feed
From: Mark Galassi <>
Subject: ANNOUNCE new DocBook tools packages released
Date: Tue, 24 Aug 1999 09:53:00 -0000	[thread overview]
Message-ID: <> (raw)

        ANNOUNCE: the DocBook tools packages, 1999-08-24

Dear DocBook enthusiasts,

A new release of the DocBook tools is available.

These tools are now being maintained on the Cygnus sourceare site:
thank you to Cygnus for hosting this and many other projects on 

The RPM packages can be found at

My DocBook intro is at:

------------ some of the changes ------------

* Ultra-sparc RPMs are still there, but they are older.  I'm not using
  those right now, and I don't have an ultra-sparc platform to build
  them on.  I'd be curious to see if anyone has good results with that.

* Tracking the latest version of all the component tools (jade,
  stylesheets, PSGML...)

* New DocBook 3.1 DTD!!  Note that the old one is also still
  installed, and both can be used simultaneously.  So you can gently
  migrate your documents form
  <!DOCTYPE book PUBLIC "-//Davenport//DTD DocBook V3.0//EN">
  <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V3.1//EN">

* RPMs are now generated on Red Hat 6.0.  The old ones are still squirreled
  away on the ftp for Red Hat 5.2 users, and the SRPMs can probably
  be used too.

------------ project status ------------

DocBook is now ubiquitous in the free software world, and the
maintainers of sgml-tools, FreeBSD documentation project and the
Debian DocBook packages are all doing a much more energetic job than I

So why do we continue with the docbook-tools packaging?  I can give of
a few reasons without thinking hard:

1. Strangely, these packages are still by far the easiest to install
   on a Red Hat system, so people need it.  This is probably because
   I'm less ambitious (the others deal with the old LinuxDoc format
   and so forth...), but that creates an important niche.

2. I actually enjoy working on it when I make the time, and I have
   lots of nice things I want to do with it :-)

3. I forget what point #3 was...  I'm sure it was good!

intro to docbook
   My tutorial at
   is getting a lot of coverage, so I will continue to maintain that
   document.  I'm priming up for some major additions.

------------ Yours truly, --------------

Mark Galassi

------- Here is the INSTALL file -------


To use jadetex (to get printed output with TeX) you will need to
install teTeX 0.9 (or newer).  RedHat 4.x, 5.0 and 5.1 come with teTeX
0.4 which cannot handle jadetex.  On newer versions of Red Hat Linux
(5.2 and 6.0) you are fine.

You can get teTeX 0.9 from the RedHat 5.2 distribution and install it
on older RedHat releases.  You will need tetex and tetex-latex, and
you will probably also want tetex-dvips and tetex-xdvi.

Here are ftp URLs for the various teTeX packages: .

Sometimes Red Hat will come with SgmlTools 1.something installed,
which has a couple of conflicts (nsgmls and possibly jade).  In this
case you can "rpm -e sgml-tools" to remove it, or if you want to keep
it you can use some RPM magic commands to run the "rpm --upgrade" with
flags that are lenient toward files shared with another package.


It used to be that you had to install the RPMs in a specific order.
That is no longer necessary: you can grab all the packages


put them in one directory, and type
    rpm --upgrade *.rpm

                 reply	other threads:[~1999-08-24  9:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

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