Could you make currency's names are shown in local language?

[Christian Stimming]

Thanks for the follow-up on the discussion - I've answered (and  
continue the discussion) in bugzilla,  
https://bugzilla.gnome.org/show_bug.cgi?id=118391

Zitat von Dancefire <dancefire at gmail.com>:

> [Resend, since forgot "reply all" last time]
>
> Hi,
>
> Is that possible let iso-4217-currencies.scm belong to seperate .po
> file? just like "gnucash-glossary", it's "gnucash-currencies", but it
> will be used during the runtime. I don't know whether it is possible a
> program can use 2 po file at same time.
>
> If we can treat the iso-4217 currencies' name seperately, we can write
> a simple script to convert existing iso-4217 po files to gnucash
> project, and use them, without translators of gnucash involved in. And
> it will not broke "string freeze".
>
> And, actually, iso-4217 currencies is very different from the strings
> in the existing po file. It's a set of string which belong to a
> standard, and there is a seperate translators working on it. And
> translators of gnucash actually can do nothing but merge them. For
> each time iso-4217 translations updated, all translators have to
> update there po. It should not let translators do it. It should be
> done automatically. To do that, make iso-4217 to a seperate po file,
> will make everything much easier. Just copy existing iso-4217
> translations to a specific location, such as po/currencies, And use a
> script to manipulate those file to gnucash, or maybe there is not even
> necessary to do the manipulate.
>