Re: Localization filenames

I also think we need to keep the second character string. In addition
to the examples given, there are numerous countries which speak French
and Spanish and may also have their country-specific localizations.

To say nothing of the totally different localization of Swiss-German :-)

Cheers

martin

2011/1/5 Kathiravelu Pradeeban <kk.pradeeban@gmail.com>:
>
> I am not sure about how useful this change will be. For instance,
> though some language may remain with one locale[1] at the moment,
> later other locales may also be implemented, hence LL_CC remains the
> natural choice.
>
> For eg, if you take Tamil (ta), currently it remains as ta-IN
> (Tamil-India), where I can see a possibility of ta-LK (Tamil-Sri
> Lanka) localization too at some point (I initially started working on
> it, but couldn't make a considerable progress on it).
>
> Most of the languages are translated considering the locale in mind.
> Hence removing the country code from the files will just drop that
> information off.
>
> [1] http://en.wikipedia.org/wiki/Locale
>
> Regards,
> Pradeeban.
>
> On Wed, Jan 5, 2011 at 3:51 PM, Алекс <eskaer_spamsink@ngs.ru> wrote:
>>
>> I think that most localization filenames should be shortened to include only language code (from ll_CC.strings form they are now). There's only 2 cases (en and pt) where language/country defines unique language, for other ones country field can be arbitrary and not needed to be specified.
>>
>>
>
>
> --
> Kathiravelu Pradeeban.
> Software Engineer.
> WSO2 Inc.
>
> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
>
Received on Thu Jan 6 00:42:30 2011