[Pkg-isocodes-devel] [SCM] ISO language, territory, currency, script codes and their translations branch, master, updated. iso-codes/3.10.1-21-g836d21e

[Christian Perrier]

Quoting LI Daobing (lidaobing at gmail.com):
> The following commit has been merged in the master branch:
> commit 836d21e90f3b94b8d379894fbfc24bdac2a852a4
> Author: LI Daobing <lidaobing at gmail.com>
> Date:   Sat Aug 1 12:04:34 2009 +0800
> 
>     ISO 3166: new Bengali (India) by Runa Bhattacharjee (TP)

> diff --git a/iso_3166/bn.po b/iso_3166/bn_IN.po
> similarity index 66%
> copy from iso_3166/bn.po
> copy to iso_3166/bn_IN.po
> index 61ad07e..8d292ae 100644
> --- a/iso_3166/bn.po
> +++ b/iso_3166/bn_IN.po
> @@ -1,24 +1,23 @@
> -# Translation of ISO-3166 (country names) to Bengali
> +# Translation of ISO 3166 (country names) to Bengali India


Is there *really* a reason to have a different translation for bn and
bn_IN?

I am personnally *very strongly* opposed to software localization
being different because of country variations. In most of my
experiences with multi-country languages, the *written* language is
mostly standardized between the various countries and, eventually with
some compromises being made, it is possible to have the same
translations and avoid splitting out the work.

I *do* work for l10n on a language that's used in many countries and
we mostly never end up with fr_FR and fr_CA, fr_CH, fr_BE,
etc. translations (except in few cases where people don't understand
anything to gettext).

I would really like to see this split between bn and bn_IN
disappear. Is there *really* a reason to name countries differently in
India and Bangladesh.

Runa, Jamil, I know both of you and have respect for both your
activities in l10n. I would very much welcome to see some agreement,
here.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-isocodes-devel/attachments/20090802/1e532f0e/attachment.pgp>