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

[Geert Janssens]

On Friday 23 April 2010, Frank H. Ellenberger wrote:
> Hello,
> 
> sorry for my late stepping in this discussion, but I am out of town, and
>  have only a 56k-dial-in connection.
> 
> Am Donnerstag, 22. April 2010 um 23:05:57 schrieb Christian Stimming:
> > Hi everyone,
> >
> > apparently it wasn't as difficult as I thought to actually mark all
> > currency names for translation. This means we "only" have to get the
> > translators to really translate them, and from now on they will appear in
> > the correct language.
> >
> > HOWEVER: As "Dancefire" pointed out, there is already the "pkg-isocode"
> > project http://alioth.debian.org/projects/pkg-isocodes and
> > http://git.debian.org/?p=iso-codes/iso-codes.git;a=tree that has
> > collected plenty of translations for e.g. the iso-4217 currency names. We
> > can re-use the translations from there by using the XX.po file form there
> > as "compendium" when merging our local XX.po file with the latest
> > gnucash.pot, like so:
> >
> >   make pot
> >   cd po
> >   msgmerge -C ../../iso-codes/iso_4217/de.po de.po gnucash.pot -o
> > de.new.po
> >
> > Theoretically, this would provide us with the translations for all new
> > 250 introduced currency name string.
> 
> At least for opensuse 11.0 the package iso-codes-3.3 is available. I would
> assume, the other main distros will offer somthing similar - somebody could
> check that on distrowatch.
> 
Good hint. I quickly checked the systems I have running:
Mandriva 2010.0 -> iso-codes 3.11
Centos 5.4      -> iso-codes 0.53

If it's in Centos/RHEL, I'm rather sure all distros ship it, albeit with 
widely varying versions. I'm not sure if that could cause issues.

Geert