public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jochem Huhmann <joh@revier.com>
To: docbook-tools-discuss@sourceware.cygnus.com
Cc: docbook-tools@bazar.conectiva.com.br
Subject: Re: --parser and --nochunks are available
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <m39003kozn.fsf@nova.revier.com> (raw)
In-Reply-To: <38BD2E8F.A3A3F14@cybercable.tm.fr>

* Eric Bischoff <ebisch@cybercable.tm.fr> wrote:
> Jochem Huhmann wrote:
> > 
> > * Jorge Godoy <godoy@conectiva.com.br> wrote:
> > > We can write the man page in docbook... It has support on that. ;-)
> > 
> > Has anyone tried docbbook2man (which produces man-pages from REFENTRY
> > elements)? http://shell.ipoline.com/~elmert/comp/docbook2X/
> 
> No, but db2man can become part of the docbook-utils ;-)
> 
> I've been writing the man page for the docbook-utils and try
> to use docbook2man with it.
> 
> By the way, another feature I could add to the db2* scripts
> would be an option to call collateindex.pl. Has someone
> already played with a docbook index and this tool ?

Not yet. But shouldn't be there some framework for such things in a more
generalized way?

SGMLTools calls these "backends". So "-b html" converts to HTML, "-b ps"
to Postscript, "-b txt" to plain text (via --nochunks and then stripping
the HTML away with "lynx --dump")...

It would be the most flexible approach to make such backends
pluggable. If called with a not builtin backend (say "-b foo") the
script could look if there is a file "/etc/sgml/backends/foo.sh" and
just source it. From this sh-snippet one would have comfortable access
to all parsed commandline arguments and such, so that a new wrapper
around db2man or collateindex.pl (or docbook2latex, or whatever) could
be written in a few lines and simply thrown in.


[I've cc'ed this to the new list]

        Jochem

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!

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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 db* does it serve the purpose madhu
2000-12-27  6:36 ` Jorge Godoy
2000-12-27  6:36   ` (docbook-tools) " Eric Bischoff
2000-12-27  6:36     ` Jorge Godoy
2000-12-27  6:36       ` Jochem Huhmann
2000-12-27  6:36     ` Jochem Huhmann
2000-12-27  6:36       ` Eric Bischoff
2000-12-27  6:36         ` Jochem Huhmann
2000-12-27  6:36     ` madhu
     [not found]       ` <38BC0BF9.1E8F29B8@cybercable.tm.fr>
2000-12-27  6:36         ` --parser and --nochunks are available madhu
2000-12-27  6:36           ` Jorge Godoy
2000-12-27  6:36             ` Jochem Huhmann
2000-12-27  6:36               ` Eric Bischoff
2000-12-27  6:36                 ` Jochem Huhmann [this message]
2000-12-27  6:36                 ` Mark Galassi
2000-12-27  6:36                 ` Edward C. Bailey
2000-12-27  6:36                 ` Jorge Godoy
2000-12-27  6:36           ` man page for docbook-utils scripts Eric Bischoff
2000-12-27  6:36 ` db* does it serve the purpose Mark Galassi
2000-12-27  6:36   ` madhu
2000-12-27  6:36 ` Eric Bischoff

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=m39003kozn.fsf@nova.revier.com \
    --to=joh@revier.com \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=docbook-tools@bazar.conectiva.com.br \
    /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).