caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Adrien Nader <adrien@notk.org>
To: Tao Stein <taostein@gmail.com>
Cc: Evgeny Roubinchtein <zhenya1007@gmail.com>,
	OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] error messages in multiple languages ?
Date: Mon, 10 Apr 2017 20:07:14 +0200	[thread overview]
Message-ID: <20170410180714.GA6391@notk.org> (raw)
In-Reply-To: <CABs4Tj+JewSW-Uu44G9RLsVO9SK9sx3trtR8c2eLYtw6k2fLbA@mail.gmail.com>

On Mon, Apr 10, 2017, Tao Stein wrote:
> I'm not sure one would have to be able to read all the languages for there
> to be some win. There may be some similarity between subsets of the
> languages -- within the Latin languages, Traditional and Simplified
> Chinese, for example. If I were putting in Traditional Chinese messages,
> I'd want them to be consistent with the Simplified Chinese messages, and I
> need not be able to read Spanish. Anyways, I'm not convinced this is a big
> win. Maybe just something to think about. Any thoughts on using UTF-8 for
> the file(s)?
> 
> And thoughts on the other points?

Just think about the fact that some languages such as Polish have
several plurals (*) yet can be understood a bit by French speakers.
There are reasons translations need to be done by people knowledgeable
about both languages involved in a translation.

It is also worth pointing out that gettext's update-po task gives
statistics about the translations: number of translated strings, number
of untranslated strings, number of "fuzzy" translations (and maybe
others). It also seems to be able to perform some simple updates
automatically (was quite astonished to find out about this). The
workflow itself is really simple and usually amounts to "make
update-po", edit po/$LANG.po, update the translation which are marked
"fuzzy" and remove that keyword when you're done.

Without saying anything about the likelihood of such a change being
integrated, linking against libgettext would have to be optional and
note that there's also ocaml-gettext to take a look at. There are also
many many places that would need changes so any evolution would need
some plan and would also probably need to be done in steps.

(*) hopefully I didn't get that one wrong :P 

-- 
Adrien Nader

  reply	other threads:[~2017-04-10 18:07 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 [this message]
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=20170410180714.GA6391@notk.org \
    --to=adrien@notk.org \
    --cc=caml-list@inria.fr \
    --cc=taostein@gmail.com \
    --cc=zhenya1007@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).