From: Peter Jolly <peter@jollys.org>
To: Jonathan Roewen <jonathan.roewen@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Supporting unicode in ocaml...
Date: Sat, 19 Aug 2006 13:41:46 +0100 [thread overview]
Message-ID: <44E7070A.40704@jollys.org> (raw)
In-Reply-To: <ad8cfe7e0608190402p5588899fvb73f1af0fe943eab@mail.gmail.com>
Jonathan Roewen wrote:
> Yes I did (as if you read closer, I did mention). But being able to
> use actual utf8 rather than manually encoding characters in the string
> is what would be nice. Maybe I just need a script to preprocess
> sources in utf8...
AFAIK, all you need to do is get rid of the BOM, which is redundant in
UTF-8 anyway. I have no problems at all using UTF-8 encoded string
constants in OCaml, and Camomile's UTF8 module then handles them
seamlessly. YMMV.
(There is one minor issue, which is that there are legal OCaml
identifiers which become illegal when the file is encoded in UTF-8 --
namely those that use accented letters.)
prev parent reply other threads:[~2006-08-19 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 23:37 Jonathan Roewen
2006-08-19 9:05 ` Richard Jones
2006-08-19 11:02 ` Jonathan Roewen
2006-08-19 12:41 ` Peter Jolly [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=44E7070A.40704@jollys.org \
--to=peter@jollys.org \
--cc=caml-list@yquem.inria.fr \
--cc=jonathan.roewen@gmail.com \
/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).