public inbox for
 help / color / mirror / Atom feed
From: Ronald Hayden <>
To: Peter Toft <>, <>
Subject: Re: DocBook roadmap?
Date: Thu, 12 Apr 2001 14:42:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <Pine.LNX.4.30.0104112243060.2744-100000@pto.sslug>

> From: Peter Toft <>
> Date: Thu, 12 Apr 2001 23:13:31 +0200 (CEST)
> Subject: DocBook roadmap?
> I have now eight books in SGML/DocBook 3.1 running on
> Linux boxes. Should I consider to swap the source to
> XML at some point? What is the status on the XML
> DocBook resources??

I'm putting together the Darwin Documentation Project, and have been playing
with various DocBook XML solutions for a few months.  The current status, in
my experience so far, is that there are mature processing solutions as long
as you can use a Java-based solution.  This doesn't mean a Java application,
but Java commands that you call from the command-line.

The tools being used by the Darwin Doc Project are outlined here:

There are a number of C- and Perl-based XSLT processing solutions in the
works, but none of them that I've tried has successfully handled DocBook.
This will certainly change in the next 6-9 months, but that's where it is
now near as I can tell.

On the editing side, there isn't anything really better than just using
Emacs if you can stick with that.  Certainly nothing mature (that I've seen)
that a user not comfortable with tags is going to find very usable.  That
too will hopefully change in the next year.

Of course I'm interested in hearing if other's experience varies.

 -- Ron Hayden

  reply	other threads:[~2001-04-12 14:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-12 14:13 Peter Toft
2001-04-12 14:42 ` Ronald Hayden [this message]
2001-04-12 14:55   ` Peter Toft
2001-04-12 16:12     ` Ronald Hayden
2001-04-12 16:14     ` Gregory Leblanc
2001-04-12 16:29       ` Ronald Hayden
2001-04-12 17:16         ` Gregory Leblanc
2001-04-16 10:18 ` Norman Walsh

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