From: Jorge Godoy <godoy@conectiva.com.br>
To: madhu <b_maddy_016@yahoo.com>
Cc: Eric Bischoff <ebisch@cybercable.tm.fr>,
docbook-tools-discuss@sourceware.cygnus.com,
docbook-tools@bazar.conectiva.com.br
Subject: Re: --parser and --nochunks are available
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <20000229121744.J15571@conectiva.com.br> (raw)
In-Reply-To: <00022920513400.00904@localhost.localdomain>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]
On Tue, Feb 29, 2000 at 08:39:41PM +0530, madhu wrote:
> hi
> On Tue, 29 Feb 2000, you wrote:
>
> > Since the scripts are becoming more complicated, it is worth
> > starting to write a man page for them. Does someone know how
> > to write that ? I can give an unformatted text to be
> > reworked.
> 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 &
> 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 .
http://www.metalab.unc.edu/godoy -- there's a starting --- needing
_many_ english corrections --- DocBook HOWTO.
We can write the man page in docbook... It has support on that. ;-)
> > But it would be nice if db2html and friends could operate on
> > XML docbook. In docbook-utils version 0.3 ? ;-)
> should it take as it is in the mail ;-) that should be nice
It wouldn't be nice. It will be needed. DocBook V5.0 is going to be
XML only...
--
Godoy. <godoy@conectiva.com.br>
Setor de Publicações
Publishing Department Conectiva S.A.
next prev 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 db* does it serve the purpose madhu
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Jorge Godoy
2000-12-27 6:36 ` (docbook-tools) " Eric Bischoff
2000-12-27 6:36 ` Jorge Godoy
2000-12-27 6:36 ` Jochem Huhmann
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 ` man page for docbook-utils scripts Eric Bischoff
2000-12-27 6:36 ` Jorge Godoy [this message]
2000-12-27 6:36 ` --parser and --nochunks are available Jochem Huhmann
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Edward C. Bailey
2000-12-27 6:36 ` Jorge Godoy
2000-12-27 6:36 ` Jochem Huhmann
2000-12-27 6:36 ` Mark Galassi
2000-12-27 6:36 ` db* does it serve the purpose Mark Galassi
2000-12-27 6:36 ` madhu
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=20000229121744.J15571@conectiva.com.br \
--to=godoy@conectiva.com.br \
--cc=b_maddy_016@yahoo.com \
--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).