caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Adrien Nader <adrien@notk.org>
To: Xavier Leroy <Xavier.Leroy@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] error messages in multiple languages ?
Date: Sun, 9 Apr 2017 21:50:59 +0200	[thread overview]
Message-ID: <20170409195059.GA3385@notk.org> (raw)
In-Reply-To: <8261755f-fb74-c363-a764-08623c06ce3a@inria.fr>

On Sat, Apr 08, 2017, Xavier Leroy wrote:
> On 04/08/2017 06:51 PM, Sébastien Hinderer wrote:
> 
> >> This implementation was pretty short and sweet, if I may say so myself, and
> >> possibly easier to use than gettext because by construction the english
> >> message was always available, even if translations were missing by
> >> mistake.
> > 
> > I am not following you here. Isn't that exactly the behaviour gettext
> > provides?
> 
> Oops, yes, you're probably right.  I was confusing gettext with the (early?)
> Java i18n library where every message was to be given a unique, short
> identifier, then be looked up in a resource file.

As far as I know this is also similar to catgets(3) which is the
i18n facility standardized in POSIX. The gettext documentation gives an
overview of it:
  http://gnu.huihoo.org/gettext-0.10.35/html_chapter/gettext_8.html

Unsurprisingly, pretty much everyone uses gettext rather than catgets.

Personally I've enjoyed using gettext and I've found that it provided
the features needed for a proper translation in a pretty good way.

I know that several large projects do translation updates during feature
freezes and bug fix periods (i.e. during release candidates). There are
also some (web) platforms to open the translation process to more people
(LibreOffice, XFCE and many others use transifex).

-- 
Adrien Nader

  reply	other threads:[~2017-04-09 19:51 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 [this message]
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=20170409195059.GA3385@notk.org \
    --to=adrien@notk.org \
    --cc=Xavier.Leroy@inria.fr \
    --cc=caml-list@inria.fr \
    /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).