caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: "Richard W.M. Jones" <rich@annexia.org>
Cc: Tao Stein <taostein@gmail.com>, OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] error messages in multiple languages ?
Date: Tue, 11 Apr 2017 10:18:09 -0400	[thread overview]
Message-ID: <CAPFanBG+4vkBcUYcdbiexzp3NVSq9HUV4+pQpPnHLO74LxNSug@mail.gmail.com> (raw)
In-Reply-To: <20170411140512.GK28111@annexia.org>

[-- Attachment #1: Type: text/plain, Size: 1700 bytes --]

> I find that it makes it considerably easier to search for error messages

On this specific topic, I would be interested in having OCaml compiler
error messages numbered, just as warnings already are, precisely because it
makes it much easier to reference them (is robust to change of wording),
and for example look up a specific error in the manual for further
explanations -- we recently started doing this for warnings, see
http://caml.inria.fr/pub/docs/manual-ocaml/comp.html#sec270 .



On Tue, Apr 11, 2017 at 10:05 AM, Richard W.M. Jones <rich@annexia.org>
wrote:

> It looks like people have already mentioned getttext.
>
> I want to add that OCaml already has an excellent gettext
> implementation.  No need to reinvent any wheels.
>
>   https://forge.ocamlcore.org/projects/ocaml-gettext/
>
> We use it every day in libguestfs, an example picked at random
> (there are thousands more):
>
>   https://github.com/libguestfs/libguestfs/blob/master/v2v/
> input_libvirt.ml#L39
>
> Therefore you might think I'd be very exciting about having the OCaml
> compiler messages being localized.  That not so much.  I find that it
> makes it considerably easier to search for error messages, and also to
> help people, if they are in a single language.  It's for this reason
> that we don't translate debugging and other internal messages in our
> tools.  (But being an English native speaker it's a lot easier for me,
> so take this with a pinch of salt.)
>
> Rich.
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>

[-- Attachment #2: Type: text/html, Size: 2784 bytes --]

  reply	other threads:[~2017-04-11 14:18 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
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 [this message]
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=CAPFanBG+4vkBcUYcdbiexzp3NVSq9HUV4+pQpPnHLO74LxNSug@mail.gmail.com \
    --to=gabriel.scherer@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=rich@annexia.org \
    --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).