public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <eric@caldera.de>
To: Bob Stayton <bobs@sco.COM>, Stephan Kulow <coolo@kde.org>,
	Cornelius Schumacher <cs@caldera.de>
Cc: docbook-tools-discuss@sourceware.cygnus.com,
	Gregory Leblanc <gleblanc@cu-portland.edu>,
	Peter Toft <pto@sslug.dk>
Subject: Re: libxslt in KDE?
Date: Tue, 17 Apr 2001 02:45:00 -0000	[thread overview]
Message-ID: <20010417114438.B2062@ns.caldera.de> (raw)
In-Reply-To: <10104130925.aa01995@mammoth.sco.com>

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

On Fri, Apr 13, 2001 at 09:25:21AM -0700, Bob Stayton wrote:
> Did you see this item from the docbook-apps list?
> Have you tried libxslt?  Other messages indicate it
> is quite fast, and that it handles docbook.

I tested it.

I'm quite ignorant about "KDE using libxslt for their next release".
Perharps indirectly, through Scrollkeepr. Perharps for the upcoming
DocBook browser, I don't know. Coolo?

I only know that Coolo (at KDE) has recently set up a system named "poxml"
which allows us to translate docs using the xgettext/msgmerge mechanism
(po files used as a translation memory). This system is meant to allow
easiest updates of DocBook documentation translations. This system
is based, if I remember correctly, on libxml, which is the basement
for libxslt.

I plan to package xalan/xerces as part of the docbook-tools project.
You don't need java, excepted for printed output (though FOP).
Jade is also fine, but it isn't XSL style sheets but DSSSL ones.

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

-- 
Éric Bischoff  -  Documentation and Localization
Caldera (Deutschland) GmbH - Linux for eBusiness
Tel: +49 9131 7192 300 -  Fax: +49 9131 7192 399
http://www.caldera.de/

       reply	other threads:[~2001-04-17  2:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <10104130925.aa01995@mammoth.sco.com>
2001-04-17  2:45 ` Eric Bischoff [this message]
2001-04-17  6:07   ` Stephan Kulow

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=20010417114438.B2062@ns.caldera.de \
    --to=eric@caldera.de \
    --cc=bobs@sco.COM \
    --cc=coolo@kde.org \
    --cc=cs@caldera.de \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=gleblanc@cu-portland.edu \
    --cc=pto@sslug.dk \
    /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).