From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105])
	by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id q1FBKxsw007825
	for <caml-list@sympa-roc.inria.fr>; Wed, 15 Feb 2012 12:20:59 +0100
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQDAPaTO09KN1ZKnGdsb2JhbAApGoURq10BAQEBAQgLEhQngXMBBSNmCxoCGA4CAj0KECGHegYppyuRcYEvijoCBAMFAgcEBAQBDRMHAgIGEAkGCwwDg0UJKQItggczYwSbAI0f
X-IronPort-AV: E=Sophos;i="4.73,422,1325458800"; 
   d="scan'208";a="131442997"
Received: from mail6.webfaction.com (HELO smtp.webfaction.com) ([74.55.86.74])
  by mail4-smtp-sop.national.inria.fr with ESMTP; 15 Feb 2012 12:20:53 +0100
Received: from heyho.local (77-234.197-178.cust.bluewin.ch [178.197.234.77])
	by smtp.webfaction.com (Postfix) with ESMTP id DA7C220992B6
	for <caml-list@yquem.inria.fr>; Wed, 15 Feb 2012 05:20:51 -0600 (CST)
Date: Wed, 15 Feb 2012 12:20:48 +0100
From: =?utf-8?Q?Daniel_B=C3=BCnzli?= <daniel.buenzli@erratique.ch>
To: caml-list@yquem.inria.fr
Message-ID: <3961491BF6F748AC8601E4D2DD9DE6CD@erratique.ch>
In-Reply-To: <6c53ae25faf6983cd38954f8d5309179.squirrel@gps.dynxs.de>
References: <4F3B65B9.5010704@riken.jp>
 <6c53ae25faf6983cd38954f8d5309179.squirrel@gps.dynxs.de>
X-Mailer: sparrow 1.5 (build 1043.1)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by walapai.inria.fr id q1FBKxsw007825
Subject: Re: [Caml-list] Fwd: Re: [Batteries-devel] browsing the code
 while reading the doc

Le mercredi, 15 février 2012 à 10:55, Gerd Stolpmann a écrit :
> Before you start writing a total new custom formatter (which probably
> breaks with every major OCaml version because of new syntactic elements),
> consider to extend/override the standard formatter.  

It seems then that the best option for everyone would be to have a good standard formatter in the distribution per se. These days css is on the verge of becoming Turing complete (if not already) and if the right data's here a little bit of javascript may cater most needs.  

However currently, the html generated by the standard formatter is invalid and the content littered with presentational elements (e.g. br) or inconsistent markup which makes it a nightmare to process and style with css.

Best,

Daniel

P.S.  
With respect to the original request, I once asked to turn ocamldoc into a full html code browser. But the wish was not granted :
http://caml.inria.fr/mantis/view.php?id=4443