public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jochem Huhmann <joh@gmx.net>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: (docbook-tools) Re: db* does it serve the purpose
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <m39004ojl6.fsf@nova.revier.com> (raw)
In-Reply-To: <38BAFD7A.9D78AF96@cybercable.tm.fr>

* Eric Bischoff <ebisch@cybercable.tm.fr> wrote:
> Having "db --format=html" or "db2html" is almost the same
> (less letters in the second one). If there is a big
> pressure, I will merge db2html, db2pdf, db2rtf and db2ps
> together, but this will result in an incompatibility with
> previous docbook-tools :-(.

You could symlink "db" to "db2html" and such, than look at $0 to see how
the script was called and act accordingly. SuSE does it this way too. A
single script seems to make sense to me, since it's just simpler to hack
on.

> "--converter" flag seems more interesting to implement. I
> must admit that I don't know openjade. It's a kind of
> rewriting of Jade, no ? Can someone explain me in private
> how you call it usually ? (executable name, are options
> names and semantics identical to jade ?) Users normally only
> use only one out of them, no ?
> 
> "--nochunk" looks suspicious to me. Isn't it something you
> are supposed to cusstomize through an alternate stylesheet ?
> Then you would better use "db2html --dsl nochunk.dsl", no ?

Well, if this wrappers are meant for DocBook with jade only, one could
stay with "--nochunk", I think. "--dsl nochunk.dsl" is more generic but
also more verbose. That's not far away from calling jade directly
anymore. Maybe just supply "--nochunk" as a shortcut?

> I have been sending the new db2* scripts to the connectiva
> list. If people feel like hacking them, why not ? Or they
> can give suggestions that I will implement.

I've some trouble with my email adresses right now, so I haven't
subscribed to the new list yet (and I haven't got around to post the
list announcement, too - tommorow). 

If you could put the new scripts on ftp somewhere? I could offer some
space if necessary, just upload them to ftp.revier.com/incoming and I
set up a cron-job for moving them to a directory accessible for anon-ftp
(say /pub/sgml/scripts/).




        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 madhu
2000-12-27  6:36 ` Eric Bischoff
2000-12-27  6:36 ` Mark Galassi
2000-12-27  6:36   ` madhu
2000-12-27  6:36 ` Jorge Godoy
2000-12-27  6:36   ` (docbook-tools) " Eric Bischoff
2000-12-27  6:36     ` Jochem Huhmann [this message]
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                 ` Jorge Godoy
2000-12-27  6:36                 ` Edward C. Bailey
2000-12-27  6:36                 ` Mark Galassi
2000-12-27  6:36                 ` Jochem Huhmann
2000-12-27  6:36           ` man page for docbook-utils scripts Eric Bischoff
2000-12-27  6:36     ` (docbook-tools) Re: db* does it serve the purpose Jorge Godoy
2000-12-27  6:36       ` Jochem Huhmann

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=m39004ojl6.fsf@nova.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).