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>
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: docbook2* vs db2*
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <3992AC56.B7CD37C1@cybercable.tm.fr> (raw)
In-Reply-To: <ybbn1im1f0x.fsf@chelseafc.labs.redhat.com>

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

"David C. Mason" wrote:
> 
> Mark Galassi <rosalia@galassi.org> writes:
> 
> > Dude, you missed a thread in which I asked people if they would like
> > such a change, which had been suggested.  I'll privately mail you the
> > thread.
> 
> Thanks - I have been traveling. By the way, here was my reply to the
> thread which I sent to Mark privately:
> 
> I understand the database connection and the idea that you can alias,
> tab complete, or rename even... but I am thinking of the writer who,
> may not be very Linux/UNIX savvy who has finally learned DB Tools and
> now finds that db2html does nothing. Its a small learning curve yes -
> but it *is* usability.... and that concerns me as I am one of those
> people who have to answer that question over and over again.

This kind of guy would be more at ease with an explict name,
probably.

And to be very honest, the DocBook-tools aren't really for a
guy allergical to the command line yet. We need an IDE.

> Oh, another thing. There have been some developers who insist on
> having the docs build with the source... "what is db2html?" being the

I added man pages to the DocBook utils. Try "man
docbook2html". BTW we could put them online, technically
they are docbook refentries, so we could generate HTML
easily out of them.

Regarding the crash-course, I had the same idea, but it's a
*bad* idea to bundle it into the docbook-utils package. Just
because the crash-course explains you how to get this
package and install it. So if you bundle it, it becomes a
chicken-and-egg problem.

> questions asked most often.... these developers probably do not follow
> DB Tools too closely and as long as their db2html works they will
> expect everyone who downloads their sources to as well... another
> source of problems.

A good entry for a FAQ, according to me.

> Just some thoughts on it.

You're perfectly right.

-- 
 É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 ` Eric Bischoff
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     ` Eric Bischoff [this message]
2000-12-27  6:36     ` docbook2* vs db2* Mark Galassi
  -- strict thread matches above, loose matches on Subject: below --
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=3992AC56.B7CD37C1@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).