public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <ebisch@cybercable.tm.fr>
To: "David C. Mason" <dcm@redhat.com>,
	docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: docbook2* vs db2*
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <3992AABF.96141A1D@cybercable.tm.fr> (raw)
In-Reply-To: <ybbzomm1im9.fsf@chelseafc.labs.redhat.com>

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

"David C. Mason" wrote:
> 
> Is there any reason why all of a sudden the tools are using docbook2*
> instead of db2*?

Yes:
- confusion and possible conflicts with IBM's DB2
- if you want a really short name, use "jw" (Jade Wrapper).
- if you want a name that is "speaking", use "docbook2*"
- if you really miss the old name, you can always wrap it in
your own shell script
- with Tab auto-completion, having an explicit name isn't
really a problem

jw foo.docbook == docbook2html foo.docbook
jw -b ps foo.docbook == docbook2ps foo.docbook
etc...

> Wouldn't it be *much* easier if it remained db2* so
> that people who have been using the DB Tools for a long time will
> understand how to use the new set of tools 'out of the box'?

Well, with such an explanation, it shouldn't be *too*
difficult to adapt ;-).

> Did I miss a thread about this already?

No, you didn't.

If there is really strong popular pressure for db2* names,
we can move back, but having both docbook2* and db2* would
be bloating /usr/bin, according to me.

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

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-27  6:36 David C. Mason
2000-12-27  6:36 ` Mark Galassi
2000-12-27  6:36   ` Eric Bischoff
2000-12-27  6:36   ` David C. Mason
2000-12-27  6:36     ` ANNOUNCEMENT: New docbook-tools packages Eric Bischoff
2000-12-27  6:36     ` docbook2* vs db2* Mark Galassi
2000-12-27  6:36     ` Eric Bischoff
2000-12-27  6:36 ` Eric Bischoff [this message]
2000-12-27  6:36 Gregory Leblanc

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=3992AABF.96141A1D@cybercable.tm.fr \
    --to=ebisch@cybercable.tm.fr \
    --cc=dcm@redhat.com \
    --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).