From: Francis Dupont <Francis.Dupont@inria.fr>
To: skaller <skaller@maxtal.com.au>
Cc: STARYNKEVITCH Basile <Basile.Starynkevitch@cea.fr>, caml-list@inria.fr
Subject: Re: localization, internationalization and Caml
Date: Fri, 15 Oct 1999 10:26:12 +0200 [thread overview]
Message-ID: <199910150826.KAA12903@givry.inria.fr> (raw)
In-Reply-To: Your message of Fri, 15 Oct 1999 08:20:20 +1000. <38065724.1CEC055F@maxtal.com.au>
In your previous mail you wrote:
The current 'support' for 8 bit characters in ocaml should be
deprecated immediately. It is an extremely bad thing to have, since
Latin-1 et al are archaic 8 bit standards incompatible with the
international standard for ISO10646 communication, namely
the UTF-8 encoding.
=> there is a rather strong opposition against UTF-8 in France
because it is not a natural encoding (ie. if ASCII maps to ASCII
it is not the case for ISO 8859-* characters, imagine a new UTF-X
encoding maps ASCII to strange things and you'd be able to understand
our concern).
Yes, I know Latin-1 is useful now for French.
=> it is more than useful, Latin-1 (soon ISO IS 8859-15) is necessary
if you need really readable texts in French.
The way forward may well be to provide an input filter to convert
Latin-1 (or any other encoding) to UTF8, and have ocaml process that.
=> my problem is the output of the filter will be no more readable when
I've put too much French in the program (in comments for instance).
This requires almost no changes to the compiler: the design should
open the set of characters acceptable in identifiers, probably
to some subset of the set recommended in one of the ISO10646 related
documents; the other change required is to accept \uXXXX and \UXXXXXXXX
escapes in strings. String processing functions should generally
continue to be 8 bit [per octet]: full internationalisation of client
string handling functions is a very complex, non-trivial, task]
=> I believe internationalization should not be done by countries
where English is the only used language: this is at least awkward...
Regards
Francis.Dupont@inria.fr
next prev parent reply other threads:[~1999-10-15 10:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-13 12:12 STARYNKEVITCH Basile
1999-10-14 22:20 ` skaller
1999-10-15 8:26 ` Francis Dupont [this message]
1999-10-17 11:27 ` skaller
1999-10-17 15:54 ` Francis Dupont
1999-10-19 18:48 ` skaller
1999-10-15 13:53 Gerard Huet
1999-10-15 20:28 ` Gerd Stolpmann
1999-10-19 18:06 ` skaller
1999-10-20 21:05 ` Gerd Stolpmann
1999-10-21 4:42 ` skaller
1999-10-21 12:05 ` Matías Giovannini
1999-10-21 15:35 ` skaller
1999-10-21 16:27 ` Matías Giovannini
1999-10-21 16:36 ` skaller
1999-10-21 17:21 ` Matías Giovannini
1999-10-23 9:53 ` Benoit Deboursetty
1999-10-25 21:06 ` Jan Skibinski
1999-10-26 18:02 ` skaller
1999-10-17 14:29 ` Xavier Leroy
1999-10-19 18:36 ` skaller
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=199910150826.KAA12903@givry.inria.fr \
--to=francis.dupont@inria.fr \
--cc=Basile.Starynkevitch@cea.fr \
--cc=caml-list@inria.fr \
--cc=skaller@maxtal.com.au \
/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).