Translate and/or adapt currency names? (Re: Could you make currency's names are shown in local language?)

[Dancefire]

[Sorry for forgot click "reply all", so resend it]

2010/4/23 Christian Stimming <stimming at tuhh.de>:
> HOWEVER, as it turns out, the "official" currency name is quite often
> different from what we used as a string in our iso-4217-currencies.scm list.
> See
> http://git.debian.org/?p=iso-codes/iso-
> codes.git;a=blob;f=iso_4217/iso_4217.xml;h=0176ff9c50e5f8cc685a03366aecbdf63f4ddd13;hb=HEAD
> for the "official" names. Examples:
>
> We: "British Pound"; iso-codes: "Pound Sterling"
> "CFP Franc Pacifique" vs. "CFP Franc"
> "Chinese Yuan Renminbi" vs. "Yuan Renminbi"
>
> Should we adapt to the names in iso-codes so that we can benefit from their
> translations? Or just ignore the ready-made translations for 30 languages
> there and insist on our own currency names? Well...
>

I think we should to use iso-codes name, which is ISO standard and it
is easier for translators to matching existing translations of
iso-4217's name. And the localized name for iso-codes are not strange
anymore. So, those difference is not problem for other languages
users. And if anyone think the localized name is not familiar with him
in their language, they can commit the change to pkg-iso-codes's
translation project, which will finally make the string changed in
gnucash.

BTW, I found iso_4217.mo in /usr/share/locale/zh_CN/LC_MESSAGES on my
ubuntu 8.04 system, which is belong to package "iso-codes". Which
means, iso_4217 translations already installed in the system(maybe by
default for some distributions). Should we use them directly by add
the dependence to "iso-codes"? rather than import them into current
po, and catching their updates by translators.

--
Tao Wang