From: Fabrice Le Fessant <fabrice.le_fessant@inria.fr>
To: Patrick M Doane <patrick@watson.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] CDK binary release
Date: Fri, 11 May 2001 13:58:48 +0200 (CEST) [thread overview]
Message-ID: <15099.54264.965247.51247@cremant.inria.fr> (raw)
In-Reply-To: <Pine.BSF.3.96.1010510110446.4898A-100000@fledge.watson.org>
> On Thu, 10 May 2001, Fabrice Le Fessant wrote:
>
> > The CDK documentation tool has still many problems, but it is
> > currently the only tool which produces man pages for Ocaml modules and
> > functions.
>
> Out of curiosity, who wants to be reading Ocaml documentation through man
> pages? I would think HTML and texinfo would both be nicer formats to work
> with. Is there some advantage that I'm missing?
You mean that, because you don't like man pages, nobody like them ?
HTML is already supported, I have nothing against texinfo. But, do you
know a tool to generate it from all the mli files from the CDK (that
use different formatting conventions) ? Can you send me a patch to the
CDK to use it ? Are you sure it is installed on all computers that
will compile the CDK documentation ?
For LaTeX, we will not force people to use LaTeX to document their
interfaces: most comments are simple text lines including some pieces
of code (in cdk_doc, they simply have to be between brackets). Only
section titles have to be handled differently. cdk_doc is enough for
that. New output formats have to be added, and all interfaces have to
be completely translated to the input format ... We are not writting a
book, but only a reference manual, thus, we don't need SGML or
complicated formatting tool for that !
- Fabrice
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-05-11 11:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 9:06 Fabrice Le Fessant
2001-05-07 16:09 ` Miles Egan
2001-05-07 17:17 ` John Max Skaller
2001-05-09 10:58 ` Markus Mottl
2001-05-09 12:01 ` [Caml-list] About documentation tools David Mentre
2001-05-09 13:18 ` [Caml-list] " Markus Mottl
2001-05-09 18:17 ` John Max Skaller
2001-05-09 17:58 ` [Caml-list] CDK binary release John Max Skaller
2001-05-09 22:40 ` Markus Mottl
2001-05-09 23:19 ` John Max Skaller
2001-05-10 9:19 ` Fabrice Le Fessant
2001-05-10 10:34 ` [Caml-list] CDK Documentation format Dave Mason
2001-05-13 21:26 ` Stefan Monnier
2001-05-10 11:16 ` [Caml-list] CDK binary release Sven LUTHER
2001-05-10 13:18 ` Markus Mottl
2001-05-10 15:42 ` Jean-Christophe Filliatre
2001-05-10 16:08 ` Thorsten Ohl
2001-05-10 22:53 ` Markus Mottl
2001-05-10 20:36 ` John Max Skaller
2001-05-10 14:01 ` David Mentre
2001-05-10 15:09 ` Patrick M Doane
2001-05-10 15:06 ` Patrick M Doane
2001-05-11 11:58 ` Fabrice Le Fessant [this message]
2001-05-11 15:31 ` John Max Skaller
2001-05-11 15:44 ` Fabrice Le Fessant
2001-05-13 21:33 ` Stefan Monnier
2001-05-11 17:30 ` Patrick M Doane
2001-05-12 7:46 ` Fabrice Le Fessant
2001-05-11 23:24 ` Brian Rogoff
2001-05-10 15:49 ` John Max Skaller
2001-05-14 8:21 ` Olivier Andrieu
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=15099.54264.965247.51247@cremant.inria.fr \
--to=fabrice.le_fessant@inria.fr \
--cc=caml-list@inria.fr \
--cc=patrick@watson.org \
/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