From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Tao Stein <taostein@gmail.com>
Cc: OCaml Mailing List <caml-list@inria.fr>,
Alexis Irlande <nexinexi@msn.com>
Subject: Re: [Caml-list] error messages in multiple languages ?
Date: Sat, 8 Apr 2017 10:43:03 -0400 [thread overview]
Message-ID: <CAPFanBF1UNnjX_aXq7Rz35wa=2FZ1GQSYcT-1aQUdwhqXU6HXw@mail.gmail.com> (raw)
In-Reply-To: <CABs4TjKhD-3odzvWcMeHEtn7PTpTf-qTENY9xFq0yoBDJDHOYQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1671 bytes --]
Hi,
This is an interesting question and the issue was discussed in 2012 on the
list:
https://sympa.inria.fr/sympa/arc/caml-list/2012-11/msg00100.html
Currently there is no mechanism in the compiler codebase to have
multi-language strings in the compiler. Alexis Irland proposed a patch in
the above thread ( https://sympa.inria.fr/sympa/arc/caml-list/2012-11/
msg00152.html ) that certainly enabled some kind of parametrization, but
unfortunately the patch files (which were hosted on a personal dropbox)
seem lost today. (What I have at hand is a French translation of the
compiler messages made by Jacques-Henri Jourdan, but without a
parametrization mechanism.)
I think that this is an interesting idea and I would personally be willing
to support a well-engineered patch providing the feature (the question of
whether the internationalized messages should be hardcoded in a source file
or use a sort of gettext-like mechanism is delicate), but I don't know the
opinion of the compiler maintainers.
On Sat, Apr 8, 2017 at 10:22 AM, Tao Stein <taostein@gmail.com> wrote:
>
> I've been teaching OCaml to university students in Beijing. I believe
> they'd feel more comfortable if the error messages were in Chinese. Has
> anyone thought of implementing multi-language strings in the compiler? So,
> say with the setting of an environment variable, the compiler user could
> receive errors and warnings in their preferred language. I know it would
> require a lot of translation work (crowd sourced?), but the internal
> language abstraction mechanism would need to be there too.
>
> Tao Stein / 石涛 / تاو شتاين
>
>
[-- Attachment #2: Type: text/html, Size: 2526 bytes --]
next prev parent reply other threads:[~2017-04-08 14:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 14:22 Tao Stein
2017-04-08 14:43 ` Gabriel Scherer [this message]
2017-04-08 15:03 ` Sébastien Hinderer
2017-04-08 16:38 ` Xavier Leroy
2017-04-08 16:51 ` Sébastien Hinderer
2017-04-08 16:56 ` Xavier Leroy
2017-04-09 19:50 ` Adrien Nader
2017-04-10 6:14 ` Ian Zimmerman
2017-04-10 13:20 ` Tao Stein
2017-04-10 13:45 ` Evgeny Roubinchtein
2017-04-10 14:04 ` Tao Stein
2017-04-10 18:07 ` Adrien Nader
2017-04-10 19:45 ` Hendrik Boom
2017-04-10 19:49 ` Dušan Kolář
2017-04-11 0:38 ` Tao Stein
2017-04-11 14:05 ` Richard W.M. Jones
2017-04-11 14:18 ` Gabriel Scherer
2017-04-11 14:59 ` Tao Stein
2017-04-11 17:17 ` Allan Wegan
2017-04-11 19:07 ` Glen Mével
2017-04-11 23:04 ` Allan Wegan
2017-04-12 0:12 ` Tao Stein
2017-04-16 22:37 ` Evgeny Roubinchtein
2017-04-09 17:15 Андрей Бергман
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='CAPFanBF1UNnjX_aXq7Rz35wa=2FZ1GQSYcT-1aQUdwhqXU6HXw@mail.gmail.com' \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=nexinexi@msn.com \
--cc=taostein@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).