public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <ebisch@cybercable.tm.fr>
To: madhu <b_maddy_016@yahoo.com>
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: man page for docbook-utils scripts
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <38BC4E59.FCF3D04@cybercable.tm.fr> (raw)
In-Reply-To: <00022920513400.00904@localhost.localdomain>

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

madhu wrote:
> i cant help you with Manpage though i had a different approach in mind.why not
> a manual in docbook format for all these scripts and we can continue Mark's
> tradition by having a Turial on Docbook usage .he has done a very fine &

Well, we can have both, but a manual page seems more urgent
to me.

I've already been writing such a guide for the KDE project.
It's called
"Crash course to DocBook". And such starter guides are
really many across
the internet. So I'm not very enthusiastic at the idea of
making a new one.

> wonderful job ,atleast my starting point was his tutorial. but i think that  it
> is a half finished and half hearted attempt but again understandable since we
> all know how busy he is .by the by is he back  form his numerous conferrences or
> some such thing.in fact it can have much more details on dsssl with hopefully
> norman's input. i would like to be part of this intiative if everybody likes
> it.here's hoping for the best .

Yes, we could also finish Mark's work. But still, I would
insist on having a man page for db2*. I can write the text
but I don't want to spend some time in learning the markup.

-- 
 É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 db* does it serve the purpose madhu
2000-12-27  6:36 ` Eric Bischoff
2000-12-27  6:36 ` Mark Galassi
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           ` Eric Bischoff [this message]
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     ` (docbook-tools) Re: db* does it serve the purpose Jorge Godoy
2000-12-27  6:36       ` Jochem Huhmann

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=38BC4E59.FCF3D04@cybercable.tm.fr \
    --to=ebisch@cybercable.tm.fr \
    --cc=b_maddy_016@yahoo.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).