public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <ebisch@cybercable.tm.fr>
To: Jochem Huhmann <joh@gmx.net>
Cc: 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: <38BC15A7.C7C61D2F@cybercable.tm.fr> (raw)
In-Reply-To: <m39004ojl6.fsf@nova.revier.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1615 bytes --]

Jochem Huhmann wrote:
> 
> 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.

being discussed on the list.

> 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?

same thing. We added --nochunk, but it doesn't call another
stylesheet.

> 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

No, thank you, not as long as they are not accepted by Mark.
And if they are accepted, they would be put at ordinary
docbook tools ftp site.

Just subscribe to the discussion list, I resend them each
time they get improved.

-- 
 Éric Bischoff   -   mailto:ebisch@cybercable.tm.fr
 __________________________________________________
                                           \^o~_.
     .~.                           ______  /( __ )
     /V\         Toys story         \__  \/  (  V
   //   \\                            \__| (__=v
  /(     )\                        |\___/     )
    ^^-^^                           \_____(  )
     Tux                        Konqui     \__=v
 __________________________________________________

  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 ` Jorge Godoy
2000-12-27  6:36   ` (docbook-tools) " Eric Bischoff
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                 ` Edward C. Bailey
2000-12-27  6:36                 ` Jorge Godoy
2000-12-27  6:36                 ` Jochem Huhmann
2000-12-27  6:36                 ` Mark Galassi
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 Jochem Huhmann
2000-12-27  6:36       ` Eric Bischoff [this message]
2000-12-27  6:36         ` Jochem Huhmann
2000-12-27  6:36     ` Jorge Godoy
2000-12-27  6:36       ` Jochem Huhmann
2000-12-27  6:36 ` 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=38BC15A7.C7C61D2F@cybercable.tm.fr \
    --to=ebisch@cybercable.tm.fr \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=joh@gmx.net \
    /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).