caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jun P. FURUSE" <Jun.Furuse@inria.fr>
To: shoh@duonix.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Q: multibyte encoding for CJK
Date: Tue, 11 Sep 2001 11:13:29 +0200 (CEST)	[thread overview]
Message-ID: <20010911.111329.35007088.Jun.Furuse@inria.fr> (raw)
In-Reply-To: <002801c13a77$cc751930$1e01a8c0@hama>

Hi,

> When I tested mutibyte variables in caml-light,
> it showed "Illegal character".
> 
> Do you have any Idea
> how to use multibyte variable for Chinese, Japan, Korean
> in caml-light or ocaml?

Camllight (and O'Caml) is not designed for multibyte Asian languages.
In Camllight, the identifiers (variables) must begin with 
an "alphabet" followed by alphabets, numbers, _, or '.

The "alphabets" are A-Z, a-z and the accented characters like
&aacute; &ccedil; (in the HTML encoding).

However, if you have enough luck, you can still use your Asian
keywords. The condition is: you must use EUC (= extended unix code) 
encoding, and your identifier cannot contain any character code except
0xc0-0xd6 0xd8-0xf6 0xf8-0xff in Unix... (The legal upper-byte
characters for identifiers are restricted to the European accented
alphabets.)

Well, as far as I know, this means that the use of Japanese
identifiers is practically impossible. I am not an expert of Asian
encodings, but I am afraid that so do Chinese and Korean.

BTW, the use of your language inside strings "..." has no problem, 
if you use EUC encoding. But of course you will have trouble with 
string_length, sub_string, etc... 

Hope this helps,
--
JPF
-------------------
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


      reply	other threads:[~2001-09-11  9:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-11  4:11 SooHyoung Oh
2001-09-11  9:13 ` Jun P. FURUSE [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=20010911.111329.35007088.Jun.Furuse@inria.fr \
    --to=jun.furuse@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=shoh@duonix.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).