public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gregory Leblanc <gleblanc@cu-portland.edu>
To: docbook-tools-discuss@sources.redhat.com
Subject: Re: DocBook roadmap?
Date: Thu, 12 Apr 2001 16:14:00 -0000	[thread overview]
Message-ID: <987116985.16651.2.camel@grego1.cu-portland.edu> (raw)
In-Reply-To: <Pine.LNX.4.30.0104122352380.1255-100000@pto.sslug>

On 12 Apr 2001 23:55:44 +0200, Peter Toft wrote:
> On Thu, 12 Apr 2001, Ronald Hayden wrote:
> 
> > > From: Peter Toft <pto@sslug.dk>
> > > 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.
> 
> Any clues about the performance compared to jade which
> I use to do SGML->HTML/PS/PDF

I haven't tried this myself (yet), but libxslt is very fast, and should
be stable and mostly bug-free at this point.  www.xmlsoft.org/XSLT I
think.  I know that KDE is planning to use this for their next release,
as will GNOME, for their next major release.
    Greg

  parent reply	other threads:[~2001-04-12 16:14 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
2001-04-12 14:55   ` Peter Toft
2001-04-12 16:12     ` Ronald Hayden
2001-04-12 16:14     ` Gregory Leblanc [this message]
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:
  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=987116985.16651.2.camel@grego1.cu-portland.edu \
    --to=gleblanc@cu-portland.edu \
    --cc=docbook-tools-discuss@sources.redhat.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).