Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Received-SPF: neutral (nike.apache.org: 69.147.107.20 is neither permitted nor
 denied by domain of eric14@yahoo-inc.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: =?iso-8859-1?Q?Re=3A_Hadoop=B4s_Internationalization?=
From: Eric Baldeschwieler <eric14@yahoo-inc.com>
In-Reply-To: <4E0DE9EC.8040407@apache.org>
Date: Fri, 1 Jul 2011 09:23:16 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <48D4BEA4-9B60-4BCF-A770-64488A5F46A9@yahoo-inc.com>
References: <CA2A4ABD.1C55C%sureshms@yahoo-inc.com>
 <41D837D5-97C3-48BB-9F95-01720DFB769C@yahoo-inc.com>
 <4E054E1A.2090809@uci.cu>
 <BANLkTik5iE_y8FM8nUVJqdcS8tnBpx+Bvg@mail.gmail.com>
 <67CCDC04-7B42-4B1F-96A5-DD617B3905CF@yahoo-inc.com>
 <BANLkTikrt24C-D6kf3HTYRbYqKuJe56Wbw@mail.gmail.com>
 <4E0DE9EC.8040407@apache.org>
To: "general@hadoop.apache.org" <general@hadoop.apache.org>

Unique error codes sounds like a very good place to start!

Freezing the code while a hypothetical group of volunteers localizes =
sounds premature to me.

Are there good examples of projects with lazy localization that work =
well?  EG The project is released in english, but there are sub-trees =
where additional localized content can be populated based on index =
numbers and such?

E14

On Jul 1, 2011, at 8:38 AM, Steve Loughran wrote:

> On 01/07/2011 06:44, Owen O'Malley wrote:
>> On Thu, Jun 30, 2011 at 9:06 AM, Eric Baldeschwieler
>> <eric14@yahoo-inc.com>wrote:
>>=20
>>> Do other apache projects have a good localization framework for =
error
>>> messages?
>>>=20
>>=20
>> Java has very good localization capabilities. However, it is a huge
>> pervasive change if we want to get each and every user-facing string
>> localizable.
>>=20
>> -- Owen
>>=20
> Let's be precise: Internationalisation (note the spelling) is a=20
> maintenance mess too. It's not so much a "one off event" as something=20=

> you have to do every time anyone adds an error message, or you =
gradually=20
> let the percentage of i18n'd messages drop over time. Given a =
limitation=20
> of Hadoop now is that when you get near the fringes of the valid=20
> configuration space the messages aren't that helpful, I'd focus on =
those.
>=20
> I say "I" literally here, as it tends to me that hits these problems.
>=20
> In a concession to the US installed base, I will spell words like=20
> "datacentre" and "normalised" incorrectly for EN_GB. This is not just=20=

> politeness, it's self interest: I added a message to Ant about an=20
> unknown task that said "your task is spelt wrong", and we kept on=20
> getting bugreps saying "you have spelled spelled wrong" that I'd close=20=

> as "workforme, you can't spell the past tense of spelled correctly",=20=

> until I got bored and changed it to a present-tense form that was =
valid=20
> everywhere.
>=20
> I18n getting started docs are good, and examples, but error messages =
may=20
> be best left as is. One possibility though is to add a unique error =
code=20
> to each one that could be indexed in each document, wiki, etc.
>=20
> -steve
>=20
>=20
>=20