From: Stephan Kulow <coolo@kde.org>
To: Eric Bischoff <eric@caldera.de>, Bob Stayton <bobs@sco.COM>,
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 06:07:00 -0000 [thread overview]
Message-ID: <1cf36dc842a7bf3667a2ec7d2c148530@NO-ID-FOUND.mhonarc.org> (raw)
In-Reply-To: <20010417114438.B2062@ns.caldera.de>
Am Dienstag, 17. April 2001 11:44 schrieb Eric Bischoff:
> 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?
The DocBook browser is our new help system.
>
> 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.
You mixed that up completly. poxml is not based on libxml, but our new help
system is and it uses libxslt for rendering docbook online without any other
tool. And this also means, we're using XSL stylesheets now and no DSSL
anymore.
Greetings, Stephan
--
People in cars cause accidents. Accidents in cars cause people.
prev parent reply other threads:[~2001-04-17 6:07 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
2001-04-17 6:07 ` Stephan Kulow [this message]
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=1cf36dc842a7bf3667a2ec7d2c148530@NO-ID-FOUND.mhonarc.org \
--to=coolo@kde.org \
--cc=bobs@sco.COM \
--cc=cs@caldera.de \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=eric@caldera.de \
--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).