docs: definition of "fully supported language translation"

Christian Stimming stimming at tuhh.de
Thu Aug 7 18:10:20 CDT 2003


Jon Lapham schrieb:
> "A language translation in GnuCash is considered fully supported when it 
> has reached greater than 90% translated strings, not counting the 
> strings from some country-specific features"

ok

> Also, I'm going to use the latest .pot file to determine the maximium 
> possible number of strings to translate.  So, actually, some 
> translations will get lower % done over time, if they don't keep up to 
> date.

Absolutely agreed. This is what the Translation Project also shows: 
http://www.iro.umontreal.ca/contrib/po/HTML/domain-gnucash.html The 
numbers there always run a "msgmerge" of the up-to-date .pot file. This 
is different from what we have in gnucash's CVS, where we do *not* run 
msgmerge but instead only the translators do this.

>> You could count the number of strings that came *only* from the 
>> import-export/hbci directory and subtract that from the total number 
>> of strings. However, you should make sure that de.po doesn't end up 
>> with a percentage larger than 100 :-)
> 
> German and (unfortunately) Brazilian Portuguese.  I didn't notice the 
> "no need to translate outside of Germany" message until I was nearly 
> finished translating all the HBCI strings.  :)

Oops :-)

> I plan on running each .po file through a filter that will strip any 
> msgids that have "hbci" in the comments or msgstr, and make a temp file. 

Nah, not quite. Many many strings show up at more than one place in the 
code. You should only strip msgids that have *only* "hbci" in the 
comment or msgstr. I thought it will probably be easier to count the 
msgids that have only "hbci" in the comment or msgstr.

Christian



More information about the gnucash-devel mailing list