public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <e.bischoff@noos.fr>
To: Bill Brooks <wbrooks@lug.ee.calpoly.edu>,
	docbook-tools-discuss@sources.redhat.com
Subject: Re: Processing DocBook XML sources?
Date: Wed, 11 Apr 2001 02:03:00 -0000	[thread overview]
Message-ID: <01041111033600.00885@s010> (raw)
In-Reply-To: <Pine.LNX.4.10.10104091753510.934-100000@lug.calpoly.edu>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2211 bytes --]

Le Tuesday 10 April 2001 03:05, Bill Brooks a écrit :
> Hi all,
>
> Didn't someone on this list say a while back that a new version of the
> docbook tools were available somewhere that would allow one to process
> documents based on DocBook 4.x XML DTD markup? Using the existing DSSSL
> stylesheets? if so, can someone refresh my memory as to where they are?

ftp://sourceware.cygnus.com/pub/docbook-tools/new-trials

You need the new docbook-dtd41-xml package, the existing DSSSL style sheets 
are perfectly okay. You need a recent sgml-common (with the SGML declaration 
of XML) and docbook-utils (knowing about XML headers) though.

For those interested in the XSL style sheets, I'm planning to package Xalan, 
Xerces, FOP, and the new docbook XSL style sheets.

<flame-war-start>
Why Xerces/Xalan and not another parser/style sheet engine? Well, I evaluated 
quite a lot and
a) this one does not need java (but yes, FOP does)
b) it is validating, supports DOM and SAX, XSLT and XPath
c) its development goes on
d) documentation is not bad (although java-centered)
e) at some point you have to choose something ;-)
I know this was not the unique choice, though.
</flame-war-start>

Of course the docbook-utils will get adapted to be able to control this other 
parser.

For all those who sent me patches or reported bugs recently, don't worry, 
I'll try to implement them *before* ;-), if not done yet. Among them:
- support DTDs with more complicated version numbers
   (Stephan Kulow)
- print the name of generated files when possible
  (Daag Wiers)
- use by default a .dsl with the same name as main sgml/xml file
   (Daag Wiers)
- do not output 3 parasitic lines with --nochunk
  (Stephan Dalibor)
- let sgmldiff run from somewhere else than /usr/bin
   (John Bowers)
- behave correctly when "rpm -Uh" and not "rpm -e; rpm -ih"
   (Eric S. Raymond)
- simulate openjade's -v option behaviour when using jade and not openjade
   (Stephan Dalibor)
Thanks to all contributors!

-- 
+----------------------------------------------------------------------+
| Éric Bischoff                              mailto:e.bischoff@noos.fr |
+----------------------------------------------------------------------+

  reply	other threads:[~2001-04-11  2:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-09 18:05 Bill Brooks
2001-04-11  2:03 ` Eric Bischoff [this message]
2001-04-11  0:51 ekkehard.goerlach

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=01041111033600.00885@s010 \
    --to=e.bischoff@noos.fr \
    --cc=docbook-tools-discuss@sources.redhat.com \
    --cc=wbrooks@lug.ee.calpoly.edu \
    /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).