public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jorge Godoy <godoy@conectiva.com.br>
To: Eric Bischoff <ebisch@cybercable.tm.fr>
Cc: docbook-tools-discuss@sourceware.cygnus.com,
	docbook-tools@bazar.conectiva.com.br
Subject: Re: (docbook-tools) Re: db* does it serve the purpose
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <20000228171457.C4093@conectiva.com.br> (raw)
In-Reply-To: <38BAFD7A.9D78AF96@cybercable.tm.fr>

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

On Mon, Feb 28, 2000 at 05:58:02PM -0500, Eric Bischoff wrote:
> Jorge Godoy wrote:
> > But it asks too many questions. We'd also to have GNU syntax:
> > 
> > $ DB --format=html --converter=openjade --nochunk everybody.sgml
> 
> This is the philosophy I'm trying to implement. db2html
> already has 5 different conversion flags. Most of them use
> defaults that you don't need to redefine for a normal basic
> use, so usually "db2html mydoc.sgml" is enough.

It's the best way. Having defaults that are usually correct is the
best thing that can happen with a tool. :-)

> 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 :-(.

Again you can use the other calls as wrappers... Nothing is broken,
then. 

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

Usually only one is installed. Openjade's options are exactly the same
as Jade's but it supports more output formats (such as MIF, whatever
it is). 

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

I don't see why having another stylesheet just to avoid chunks. In
jade you can say: jade ... -V nochunks ... and it will be interpreted
the same way as having (define nochunks #t) on your stylesheet. It can
only be true or false... 

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

:-)

--
Godoy.	<godoy@conectiva.com.br> 

Setor de Publicações
Publishing Department                   Conectiva S.A.

  parent 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     ` 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
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     ` Jorge Godoy [this message]
2000-12-27  6:36       ` (docbook-tools) Re: db* does it serve the purpose 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=20000228171457.C4093@conectiva.com.br \
    --to=godoy@conectiva.com.br \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=docbook-tools@bazar.conectiva.com.br \
    --cc=ebisch@cybercable.tm.fr \
    /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).