From: Andrej Bauer <Andrej.Bauer@andrej.com>
To: Maxence Guesdon <maxence.guesdon@inria.fr>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ocamldoc charset specification?
Date: Mon, 07 Nov 2005 18:02:26 +0100 [thread overview]
Message-ID: <436F88A2.5000206@andrej.com> (raw)
In-Reply-To: <20051107145047.4e6971cb@tintin.inria.fr>
Maxence Guesdon wrote:
>> Note: I am not asking for ocamldoc to recode from one charset to
>> another, just to put information about the encoding in the html file.
>
> Two solutions:
> 1) make a string replacement after the generation of html files.
This is (a) ugly and (b) as I said I am not recoding anything, I just
need to put info in the document HEAD. I suppose I could use string
relpacement for that...
> 2) create a custom ocamldoc generator with a geenrator class inheriting from
> the standard html generator and change the part where the encoding is
> generated.
Ah, this sounds like an option. Thanks for the idea, I will look into it.
Andrej
prev parent reply other threads:[~2005-11-07 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 10:43 Andrej Bauer
2005-11-07 13:50 ` [Caml-list] " Maxence Guesdon
2005-11-07 17:02 ` Andrej Bauer [this message]
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=436F88A2.5000206@andrej.com \
--to=andrej.bauer@andrej.com \
--cc=caml-list@yquem.inria.fr \
--cc=maxence.guesdon@inria.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 NNTP newsgroup(s).