From: "SooHyoung Oh" <shoh@duonix.com>
To: "caml-list" <caml-list@inria.fr>
Subject: [Caml-list] Unicode support?
Date: Wed, 12 Sep 2001 10:18:38 +0900 [thread overview]
Message-ID: <007f01c13b28$da1897e0$1e01a8c0@hama> (raw)
Hi!
I'm very interesed to use Caml for educational purpose
in multibyte environment such as CJK.
So I'd like to know whether Caml supoprt Unicode or not?
(Unicode (ISO 10646) is the character coding (or character set) standard.)
Many people forsee that Unicode is going to replace all older lagcy
encodings in a few years
and many languages such as C, Java, Perl, Tcl, C# and Python support it
already.
If Caml doesn't support unicode, could you give me any clue
from which part in caml source I should start in order to support unicode?
More question,
Which form is better for processing unicode in Caml, UTF-8 or UCS-2 (or
UCS-4)?
--- SooHyoung Oh
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next reply other threads:[~2001-09-12 1:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-12 1:18 SooHyoung Oh [this message]
2001-09-14 20:30 ` Gerd Stolpmann
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='007f01c13b28$da1897e0$1e01a8c0@hama' \
--to=shoh@duonix.com \
--cc=caml-list@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).