From: Dave Mason <dmason@sarg.Ryerson.CA>
To: caml-list@inria.fr
Cc: fabrice.le_fessant@inria.fr,
John Max Skaller <skaller@ozemail.com.au>,
Markus Mottl <mottl@miss.wu-wien.ac.at>
Subject: [Caml-list] CDK Documentation format
Date: Thu, 10 May 2001 06:34:03 -0400 [thread overview]
Message-ID: <200105101034.GAA06877@sarg.Ryerson.CA> (raw)
In-Reply-To: Your message of "Thu, 10 May 2001 11:19:40 +0200." <15098.23852.403551.65183@cremant.inria.fr>
>>>>> On Thu, 10 May 2001 11:19:40 +0200 (CEST), Fabrice Le Fessant <fabrice.le_fessant@inria.fr> said:
> The CDK documentation tool has still many problems, but it is
> currently the only tool which produces man pages for Ocaml modules
> and functions. Moreover, LaTeX is not used by all Ocaml users (some
> are using Windows
LaTeX runs fine on MS-Windows.
> and its wonderful editors).
(I don't know if this was meant as sarcastic. Probably not, although
it doesn't match my experience with MS-Windows. For me, there is only
one decent editor for MS-Windows; it's called emacs.)
> For now, I think the
> best language is a specific language, for example, a subset of HTML.
> This would have the benefit of being easily translatable to LaTex(ie
> PS), HTML and MAN (I think HTML --> LaTeX is easier than LaTeX -->
> HTML, even with HeVea).
Unless you are providing (or pointing to) a translator from HTML-->
LaTeX, this is an iffy argument. Simple LaTeX, understandable by
HeVea, isn't very difficult to write even if you never feed it to
LaTeX and only produce HTML. And as a bonus, you can get rather nice
output from LaTeX!
> Note that the current language used by cdk_doc is documented in the
> HTML documentation of the CDK (cdk_doc.html).
I haven't had a chance to look at this yet, but wanted to make the
point that there is an open-source formatting system that produces
good output (LaTeX), already available, and it would be good to use it.
> cdk_doc was not designed for being used by everybody, but to
> generate immediatly some documentation for the CDK with a minimal
> effort. Now, we have to think about how to change Sebastien's tool
> in a more general documentation tool.
It shouldn't be very difficult to have it spit out LaTeX for HeVea.
> Another approach I used a few years ago was to generate HTML
> documentation using the compiler, which can add cross-links between
> modules (and even between types in the same module). This could be
> another good idea ...
Sounds interesting, but why not generate LaTeX?
../Dave
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-05-13 20:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 9:06 [Caml-list] CDK binary release 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 ` Dave Mason [this message]
2001-05-13 21:26 ` [Caml-list] CDK Documentation format 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
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=200105101034.GAA06877@sarg.Ryerson.CA \
--to=dmason@sarg.ryerson.ca \
--cc=caml-list@inria.fr \
--cc=fabrice.le_fessant@inria.fr \
--cc=mottl@miss.wu-wien.ac.at \
--cc=skaller@ozemail.com.au \
/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