From: Gregory Leblanc <GLeblanc@cu-portland.edu>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: RE: docbook2* vs db2*
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <025836EFF856D411A6660090272811E61D05B8@EMAIL> (raw)
> -----Original Message-----
> From: Mark Galassi [ mailto:rosalia@galassi.org ]
> Sent: Wednesday, August 09, 2000 3:34 PM
> To: docbook-tools-discuss@sourceware.cygnus.com
> Subject: Re: docbook2* vs db2*
>
> David> Thanks - I have been traveling. By the way, here was my
> David> reply to the thread which I sent to Mark privately:
>
> David> I understand the database connection and the idea that you
> David> can alias, tab complete, or rename even... but I am
> David> thinking of the writer who, may not be very Linux/UNIX
> David> savvy who has finally learned DB Tools and now finds that
> David> db2html does nothing. Its a small learning curve yes - but
> David> it *is* usability.... and that concerns me as I am one of
> David> those people who have to answer that question over and over
> David> again.
>
> I kind of agree with you, which is why I plan for it to be an
> extremely slow phase-out of the old names.
>
> I guess that as long as we find packages in remote places that still
> directly invoke db2html we will continue to carry the old script
> names.
I understand this argument, but I figure it's not worthwhile, especially
after the total screw up that got Cees into trouble with "SGML tools". I'd
rather make it as un-ambiguous as possible, and avoid things like trying to
use it to convert a db2 table into html (or using sgmltools to convert
MathML into HTML).
next reply other threads:[~2000-12-27 6:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 6:36 Gregory Leblanc [this message]
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 ` Mark Galassi
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=025836EFF856D411A6660090272811E61D05B8@EMAIL \
--to=gleblanc@cu-portland.edu \
--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).