public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Lee Green <eric@badtux.org>
To: "Eric S. Raymond" <esr@snark.thyrsus.com>,
	docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: I'm trying to set up docbook-tools...
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <00070410352500.07357@ehome.inhouse> (raw)
In-Reply-To: <200007041511.LAA15779@snark.thyrsus.com>

On Tue, 04 Jul 2000, Eric S. Raymond wrote:
> I'm trying to set up docbook-tools, and finding it a hideously
> frustrating experience.  Why does all the SGML software and
> documentation in the world read as though it was carefully designed 
> to prevent any actual document production from getting done?

That puzzles me too. Even Norm Walsh's so-called "Docbook" book reads as if it
were a briefly written summary written in a foreign language to be as terse as
possible. You would suspect that the authors of documentation tools would
themselves be enamored of documentation. WIth the exception of Donald Knuth, 
that, alas, does not appear to be the case. 

It's bad enough that the authors of every book and document that exists on SGML
have invented their own inscrutable terminology for the process of marking up
documentation... but none of them, zero, zilch, appears to have considered the
notion of a GLOSSARY, and the very thought of explaining complex terms in a
simple, clear manner appears to break every single SGML author out in hives. 
Yes, it's difficult. I've done it before, I know how difficult it is. But it's
as if the creators of SGML DTD's and tools have a death wish... or else they're
trying to protect their cult's purity by keeping out the riff-raff (same
thing). 

Despite all of the above, I have become reasonably proficient in using the
Docbook-Tools set and in Docbook itself.  But the tool kits still do not work
well enough for me to actually use them to produce real documentation. I am
using Docbook for the design documentation for a major project at the office,
but nobody on this list has been able to explain to me why half the entries in
my index have "-999" as the page number, even when the 'jadetex' script does not
complain about unresolved references.  I've even tried updating everything
from the Docbook-tools site thinking maybe Red Hat had a wonked out
docbook-tools installation.  I even tried using Caldera eDesktop 2.4 rather than
Red Hat, thinking maybe Red Hat had something totally foobar in their setup. No
go. I'm on the verge of abandoning the tool kit in frustration. LyX will now
generate decent HTML output, which was my main reason for using DocBook in the
first place (the difficulty of getting good HTML output out of "latex2html" and
its ilk).  My only issue with LyX is the difficulty of maintaining multi-source
documentation in a CVS depository... CVS won't do merges of multi-author edits
of .lyx files, sigh.  But if it's a choice of LyX or using StarOffal, I know
which I'll choose -- at least LyX is a structured markup tool, whereas
StarOffal.. no, don't get me started. 

> The < http://sourceware.cygnus.com/docbook-tools/ > page directs me to
> < ftp://sourceware.cygnus.com:/pub/docbook-tools >.  That server is
> perpetually swamped.  Going to one of the mirrors, I find a
> docbook-3.1-5.noarch.rpm, but it does not contain any of the db2*
> scripts referenced on the DocBook page.  Where are those scripts?

On Red Hat 6.2 Linux, they're in "stylesheets-1.54.13rh-1.xxx.rpm" (put
architecture of choice in place of 'xxx').  Red Hat ships with what is
basically a slight tweak of the docbook-tools kit. 

'docbook-3.1-5.noarch.rpm' is just the DTD (Data Type Definition), it does not
contain the other software you'll need to convert programs written using that
DTD into a useful form. You'll need 'jade' and 'stylesheets' to do that. 
'jade' is the actual grunt engine, while 'stylesheets' is the Scheme and
scripts that the grunt engine uses to know how to do the conversion. 

export SGML_CATALOG_FILES=/usr/lib/sgml/CATALOG 
export SGML_ROOT=/usr/lib/sgml

are also nice to tell Emacs's psgml mode where to find the overall catalog and
SGML dtd and tools. I use 'xemacs', which puts up a nice SGML menu at the top.

-- 
Eric Lee Green      There is No Conspiracy
eric@badtux.org     http://www.badtux.org  

WARNING: multiple messages have this Message-ID
From: Eric Lee Green <eric@badtux.org>
To: "Eric S. Raymond" <esr@snark.thyrsus.com>,
	docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: I'm trying to set up docbook-tools...
Date: Tue, 04 Jul 2000 10:25:00 -0000	[thread overview]
Message-ID: <00070410352500.07357@ehome.inhouse> (raw)
Message-ID: <20000704102500.Ind9SX9x2i0wouyUl6UP8IbhkPp_PmgXE2QEbiN4AOE@z> (raw)
In-Reply-To: <200007041511.LAA15779@snark.thyrsus.com>

On Tue, 04 Jul 2000, Eric S. Raymond wrote:
> I'm trying to set up docbook-tools, and finding it a hideously
> frustrating experience.  Why does all the SGML software and
> documentation in the world read as though it was carefully designed 
> to prevent any actual document production from getting done?

That puzzles me too. Even Norm Walsh's so-called "Docbook" book reads as if it
were a briefly written summary written in a foreign language to be as terse as
possible. You would suspect that the authors of documentation tools would
themselves be enamored of documentation. WIth the exception of Donald Knuth, 
that, alas, does not appear to be the case. 

It's bad enough that the authors of every book and document that exists on SGML
have invented their own inscrutable terminology for the process of marking up
documentation... but none of them, zero, zilch, appears to have considered the
notion of a GLOSSARY, and the very thought of explaining complex terms in a
simple, clear manner appears to break every single SGML author out in hives. 
Yes, it's difficult. I've done it before, I know how difficult it is. But it's
as if the creators of SGML DTD's and tools have a death wish... or else they're
trying to protect their cult's purity by keeping out the riff-raff (same
thing). 

Despite all of the above, I have become reasonably proficient in using the
Docbook-Tools set and in Docbook itself.  But the tool kits still do not work
well enough for me to actually use them to produce real documentation. I am
using Docbook for the design documentation for a major project at the office,
but nobody on this list has been able to explain to me why half the entries in
my index have "-999" as the page number, even when the 'jadetex' script does not
complain about unresolved references.  I've even tried updating everything
from the Docbook-tools site thinking maybe Red Hat had a wonked out
docbook-tools installation.  I even tried using Caldera eDesktop 2.4 rather than
Red Hat, thinking maybe Red Hat had something totally foobar in their setup. No
go. I'm on the verge of abandoning the tool kit in frustration. LyX will now
generate decent HTML output, which was my main reason for using DocBook in the
first place (the difficulty of getting good HTML output out of "latex2html" and
its ilk).  My only issue with LyX is the difficulty of maintaining multi-source
documentation in a CVS depository... CVS won't do merges of multi-author edits
of .lyx files, sigh.  But if it's a choice of LyX or using StarOffal, I know
which I'll choose -- at least LyX is a structured markup tool, whereas
StarOffal.. no, don't get me started. 

> The < http://sourceware.cygnus.com/docbook-tools/ > page directs me to
> < ftp://sourceware.cygnus.com:/pub/docbook-tools >.  That server is
> perpetually swamped.  Going to one of the mirrors, I find a
> docbook-3.1-5.noarch.rpm, but it does not contain any of the db2*
> scripts referenced on the DocBook page.  Where are those scripts?

On Red Hat 6.2 Linux, they're in "stylesheets-1.54.13rh-1.xxx.rpm" (put
architecture of choice in place of 'xxx').  Red Hat ships with what is
basically a slight tweak of the docbook-tools kit. 

'docbook-3.1-5.noarch.rpm' is just the DTD (Data Type Definition), it does not
contain the other software you'll need to convert programs written using that
DTD into a useful form. You'll need 'jade' and 'stylesheets' to do that. 
'jade' is the actual grunt engine, while 'stylesheets' is the Scheme and
scripts that the grunt engine uses to know how to do the conversion. 

export SGML_CATALOG_FILES=/usr/lib/sgml/CATALOG 
export SGML_ROOT=/usr/lib/sgml

are also nice to tell Emacs's psgml mode where to find the overall catalog and
SGML dtd and tools. I use 'xemacs', which puts up a nice SGML menu at the top.

-- 
Eric Lee Green      There is No Conspiracy
eric@badtux.org     http://www.badtux.org  

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

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 Eric S. Raymond
2000-07-04  8:02 ` Eric S. Raymond
2000-12-27  6:36 ` Eric Lee Green [this message]
2000-07-04 10:25   ` Eric Lee Green
2000-12-27  6:36   ` madhu
2000-07-04 22:01     ` madhu
2000-12-27  6:36     ` Eric Lee Green
2000-12-27  6:36       ` Sam Roberts
2000-07-05  7:40         ` Sam Roberts
2000-12-27  6:36         ` Ismael Olea
2000-07-05  9:57           ` Ismael Olea
2000-12-27  6:36           ` Mark Galassi
2000-07-05  9:59             ` Mark Galassi
2000-12-27  6:36       ` Norman Walsh
2000-12-27  6:36     ` Sam Roberts
2000-07-05  7:32       ` Sam Roberts
2000-12-27  6:36   ` Mark Galassi
2000-07-04 11:21     ` Mark Galassi
2000-12-27  6:36     ` Norman Walsh
2000-07-07  7:49       ` Norman Walsh
2000-12-27  6:36   ` David C. Mason
2000-07-05  7:41     ` David C. Mason
2000-12-27  6:36   ` Norman Walsh
2000-07-06  9:21     ` Norman Walsh
2000-12-27  6:36     ` Eric S. Raymond
2000-12-27  6:36       ` Crash-course to DocBook Eric Bischoff
2000-12-27  6:36         ` Peter Toft
2000-12-27  6:36         ` Mark Johnson
2000-12-27  6:36           ` Eric Bischoff
2000-12-27  6:36       ` I'm trying to set up docbook-tools Norman Walsh
2000-07-07  7:49         ` Norman Walsh
2000-12-27  6:36       ` Mark Galassi
2000-07-06 10:25         ` Mark Galassi
2000-12-27  6:36         ` Eric S. Raymond
2000-07-06 10:37           ` Eric S. Raymond
2000-12-27  6:36           ` Kendall Clark
2000-07-06 10:48             ` Kendall Clark
2000-12-27  6:36             ` Mark Galassi
2000-07-06 10:53               ` Mark Galassi
2000-12-27  6:36               ` Eric Lee Green
2000-07-06 13:38                 ` Eric Lee Green
2000-12-27  6:36                 ` Norman Walsh
2000-12-27  6:36       ` David C. Mason
2000-12-27  6:36         ` Eric Lee Green
2000-07-06 14:22           ` Eric Lee Green
2000-12-27  6:36         ` Eric S. Raymond
2000-07-06 11:59           ` Eric S. Raymond
2000-12-27  6:36           ` David C. Mason
2000-07-06 13:55             ` David C. Mason
2000-12-27  6:36             ` Eric Lee Green
2000-07-06 14:32               ` Eric Lee Green
2000-12-27  6:36             ` Eric S. Raymond
2000-07-06 14:52               ` Eric S. Raymond
2000-12-27  6:36               ` David C. Mason
2000-07-06 15:23                 ` David C. Mason
2000-12-27  6:36                 ` Eric S. Raymond
2000-07-06 15:52                   ` Eric S. Raymond
2000-12-27  6:36                 ` Eric Lee Green
2000-07-06 15:57                   ` Eric Lee Green
2000-12-27  6:36               ` Edward C. Bailey
2000-07-06 16:05                 ` Edward C. Bailey
2000-12-27  6:36                 ` Eric S. Raymond
2000-07-06 16:46                   ` Eric S. Raymond
2000-12-27  6:36                   ` Norman Walsh
2000-07-07  7:49                     ` Norman Walsh
2000-12-27  6:36                     ` Derek Simkowiak
2000-12-27  6:36                     ` Mark Galassi
2000-12-27  6:36                     ` Eric S. Raymond
2000-12-27  6:36                       ` Norman Walsh
2000-07-07 14:42                         ` Norman Walsh
2000-12-27  6:36     ` docbook-tools-discuss: " Bill Campbell
2000-12-27  6:36       ` Norman Walsh
2000-12-27  6:36         ` Edward C. Bailey
2000-12-27  6:36         ` Eric S. Raymond
2000-12-27  6:36         ` Bill Campbell
2000-12-27  6:36     ` Chuck Dale
     [not found]     ` <ndw@nwalsh.com>
2000-12-27  6:36       ` richard offer
2000-12-27  6:36         ` Norman Walsh
2000-07-07  7:49           ` Norman Walsh
2000-12-27  6:36         ` Eric Bischoff
2000-12-27  6:36           ` Norman Walsh
2000-07-28 10:44             ` Norman Walsh
2000-12-27  6:36 ` Mark Galassi
2000-07-04  8:05   ` Mark Galassi
2000-12-27  6:36   ` Eric S. Raymond
2000-07-04  8:22     ` Eric S. Raymond
2000-12-27  6:36     ` Mark Galassi
2000-07-04  8:27       ` Mark Galassi
2000-12-27  6:36       ` Eric S. Raymond
2000-07-04  8:45         ` Eric S. Raymond
2000-12-27  6:36     ` Chuck Mead
2000-07-04  8:45       ` Chuck Mead
2000-12-27  6:36     ` Norman Walsh
2000-07-07  7:49       ` Norman Walsh
2000-12-27  6:36 David C. Mason
2000-12-27  6:36 Volker Paul
2000-12-27  6:36 Peter Ring
2000-07-07  2:27 ` Peter Ring
2000-12-27  6:36 ` Eric Lee Green
2000-12-27  6:36 Gregory Leblanc
2000-12-27  6:36 ` Mark Galassi
2000-07-04 15:44   ` Mark Galassi
2000-12-27  6:36 Peter Ring
2000-12-27  6:36 ` Eric Bischoff
2000-08-14 23:07   ` Eric Bischoff
2000-12-27  6:36   ` Volker Paul
2000-08-16  6:57     ` Volker Paul
2000-12-27  6:36     ` Norman Walsh
2000-08-16  7:30       ` Norman Walsh
2000-12-27  6:36       ` Eric Bischoff
2000-08-18  4:11         ` Eric Bischoff
2000-12-27  6:36         ` b_maddy_016
2000-12-27  6:36           ` Eric Bischoff
2000-08-18  5:55             ` Eric Bischoff
2000-12-27  6:36 Gregory Leblanc
2000-12-27  6:36 ` Eric Lee Green

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=00070410352500.07357@ehome.inhouse \
    --to=eric@badtux.org \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=esr@snark.thyrsus.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).