public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrey Slepuhin <pooh@msu.ru>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: DocBook XML tools
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <20000801164554.A20690@glade.nmd.msu.ru> (raw)

Hi everybody,

I was managed to write some program docs (what I really don't like to do :-()
in XML. I got DocBook XML DTD/Norman Walsh's XSL stylesheets/James Clark's
XP/XT toolkit. As a result I built some (very preliminary) RPM packages with
DocBook/XML support. So I have some questions:

1) Is this mailing list a correct place to discuss DocBook/XML problems or
   it is SGML-orieented?
2) Does anybody already have packaged tools for DocBook/XML processing?
3) If 2) == false, does anybody interested in maintaining such packages?
4) It seems that XP/XT are slightly outdated. Does anybody know if Clark
   still supports his tools or I should try other XSLT implementations?

FYI, I built the following RPMs:
xml-tools - XP/XT with catalogs support from ArborText
xml-docbook - DocBook DTD from Oasis, simplified DocBook DTD and XSL
  stylesheets from Norman Walsh and TDG
xml-website - WebSite DTD and stylesheets from Norman Walsh including XBel
xml-slides - Slides DTD and stylesheets from Norman Walsh

What I didn't try yet:
Chunk support using perl (XT-oriented chunking works)
Printing (i.e. converting to FO and passing it to Passive TeX)

If anybody interested I can upload my RPMs to HTTP server.

Best regards,
Andrey.

P.S. I'm not aware about licensing issues of used tools so please tell
me if I did something wrong.

             reply	other threads:[~2000-12-27  6:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 Andrey Slepuhin [this message]
     [not found] <Pine.LNX.4.21.0008021316270.1875-100000@kg.netgroup.dk>
2000-12-27  6:36 ` Andrey Slepuhin

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=20000801164554.A20690@glade.nmd.msu.ru \
    --to=pooh@msu.ru \
    --cc=docbook-tools-discuss@sourceware.cygnus.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).