public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Norman Walsh <ndw@nwalsh.com>
To: 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: <87vgyinj8n.fsf@nwalsh.com> (raw)
In-Reply-To: <00070422425701.09328@ehome.inhouse>

/ Eric Lee Green <eric@badtux.org> was heard to say:
| Unfortunately, the SGML purists appear to believe that their job is
| done once they've created the raw DTD... "just read the DTD!"
| appears to be the notion.

Reading the DTD isn't going to help at all with the problem of setting
up a toolchain, so I'm confused. Are you saying that SGML/XML are not
well described? Or that a particular DTD (e.g, DocBook) is not well
described? Or that the mechanics of setting up a toolchain (on your
system, for the output you want) are not well described?

| Correct. I've already discussed the notion that SGML purists appear
| to believe that their job is done once they've created the raw DTD
| and (optionally) style sheet. 

An SGML purist *is done* when they've created the doctype (or Schema).
That's the job you hire them to do. (Note that a doctype includes
prose documentation, a .dtd file isn't enough and was never believed
to be enough.) That said, I don't consider myself a purist and I've
spent a lot of time writing stylesheets and documenting them as best I
could under the constraints of time and a day job.

No one (that I know) would be silly enough to argue that you *don't
need* a toolchain, but there is tremendous variablity in setting up
the toolchain. Thanks to the tremdous effort of folks involved in
efforts like docbook-tools, we're beginning to see open source
distributions of tools that can be reasonably documented and will
produce results for lots of folks on lots of platforms. This is a
welcome change for those of us who have been lamenting the fact that
SGML was almost completely a "build your own" environment for so many
years.

| This attitude is what has prevented
| SGML from supplanting TeX/LaTeX for structured document creation.

Prevented where? Oh, nevermind, it's an inflammatory remark.

| I have taken to running jadetex by hand until the 'unresolved
| reference' messages go away, then running dvi2ps by hand. Some of my
| page references STILL turn out to be -999.

I've forgotten where this started. These are TOC page references or
index page references?

| > that situation is not likely to improve what with SGML is dead
| proclamations > doing the rounds and shift is towards XML . but
| again tools for XML are not unix > favorable at all .

For the purposes of this discussion, XML is SGML. There's no
appreciable difference.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | All professional men are handicapped by
http://nwalsh.com/            | not being allowed to ignore things
                              | which are useless.--Goethe

  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
2000-07-04 10:25   ` Eric Lee Green
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       ` David C. Mason
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         ` Eric Lee Green
2000-07-06 14:22           ` Eric Lee Green
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       ` Norman Walsh
2000-07-07  7:49         ` Norman Walsh
2000-12-27  6:36       ` Crash-course to DocBook Eric Bischoff
2000-12-27  6:36         ` Mark Johnson
2000-12-27  6:36           ` Eric Bischoff
2000-12-27  6:36         ` Peter Toft
2000-12-27  6:36     ` docbook-tools-discuss: Re: I'm trying to set up docbook-tools Bill Campbell
2000-12-27  6:36       ` Norman Walsh
2000-12-27  6:36         ` Eric S. Raymond
2000-12-27  6:36         ` Edward C. Bailey
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   ` 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 [this message]
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 ` 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     ` Chuck Mead
2000-07-04  8:45       ` Chuck Mead
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     ` Norman Walsh
2000-07-07  7:49       ` Norman Walsh
2000-12-27  6:36 David C. Mason
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 Volker Paul
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=87vgyinj8n.fsf@nwalsh.com \
    --to=ndw@nwalsh.com \
    --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).