From: Jochem Huhmann <joh@gmx.net>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: Docbook tools
Date: Tue, 07 Sep 1999 00:44:00 -0000 [thread overview]
Message-ID: <m3906jywqm.fsf@localhost.revier.com> (raw)
In-Reply-To: <76btbfyyxq.fsf@odie.lanl.gov>
Mark Galassi <rosalia@lanl.gov> wrote:
> But the real godsend will be if we can pull together with the
> SGMLTools effort and do the automake/autoconf stuff I mentioned in a
> message earlier today.
Is this effort limited to get jade and DSSSL-related stuff going?
SGMLTools did so and suffered a lot by doing so. There are docbook2man
translators in perl (which allows to write man pages as REFENTRY
elements) and there is also a docbook2texinfo translator (really great
if you need info as documentation format, especially when working with
emacs, but also an alternative approach to get printed documentation
via LaTeX).
Would be nice if there would be a central store to get all this, with
a unified interface and such...
Jochem
--
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
next prev parent reply other threads:[~1999-09-07 0:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-05 14:13 Eric Bischoff
1999-09-06 1:27 ` Guy Brand
1999-09-06 21:01 ` Mark Galassi
1999-09-06 21:07 ` Rahul Dave
1999-09-06 21:09 ` Mark Galassi
1999-09-10 0:39 ` Eric Bischoff
1999-09-10 0:30 ` Eric Bischoff
1999-09-06 22:43 ` Jason Molenda
1999-09-07 0:02 ` Derek Simkowiak
1999-09-07 0:16 ` Mark Galassi
1999-09-07 0:44 ` Jochem Huhmann [this message]
1999-09-07 1:59 ` Derek Simkowiak
1999-09-06 5:31 Stephane Bortzmeyer
1999-09-06 8:55 ` Mark Galassi
1999-09-06 8:21 David C. Mason
1999-09-06 13:43 ` Eric Bischoff
1999-09-07 7:27 ` David C. Mason
1999-09-10 1:06 ` Eric Bischoff
1999-09-10 7:38 ` David C. Mason
1999-09-10 7:52 ` Edward C. Bailey
2000-12-27 6:36 DocBook tools Clarissa Kao
2000-12-27 6:36 ` Mark Galassi
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=m3906jywqm.fsf@localhost.revier.com \
--to=joh@gmx.net \
--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).