PO file typos, the more difficult ones

[Christian Stimming]

Hi Clytie,

here's the list of those typos where I don't see how they can be fixed easily.

Am Mittwoch, 19. Dezember 2007 07:23 schrieb Clytie Siddall:
> 5. A LOT of explanatory sentences don't have full stops at the end, e.g.
>
> #: ../src/gnome/glade/register.glade.h:11
> #: ../src/gnome/gnc-plugin-page-register.c:249
> msgid ""
> "Create a Scheduled Transaction with the current transaction as a
> template"
>
> #: ../src/gnome/glade/register.glade.h:29
> #: ../src/gnome/gnc-plugin-page-register.c:246
> msgid "Jump to the corresponding transaction in the other account"

Many of those sentences are supposed to show up in a tooltip. IIRC Tooltips by 
convention don't end with a full stop, so those should stay this way.

Many others of those sentences show up in the status bar. I'm not so sure 
whether there is a convention about status bar sentences. Gnucash tries to 
follow the GNOME Human Interface Guide (HIG) in those matters. Anyone to look 
this up?

> 8.
> #: ../src/gnome-utils/glade/preferences.glade.h:108
> msgid "Show all transactions on one line. (Two in double line mode.)"
>
> - Show all transactions on one line.
> + Show each transaction on a separate line.
>
> unless you really mean "Show all the transactions together on only one
> line", which would be impossible to read, wouldn't it?

I think this choice (out of several possible viewing choices) means "Show a 
transaction on one line, and use this viewing setting for all transactions." 
I don't have a proposal for a nicer wording.

> 9.
> #.Translators: This string should not have shown up in
> #.gnucash.pot as it is looked up in the "gtk20" translation
> #.domain. You can safely ignore this string and leave it
> #.untranslated.
> #: ../src/gnome-utils/gnc-dense-cal.c:443
> msgid "calendar:week_start:0"
>
> If this is obsolete, please remove it. Otherwise, it will confuse
> translators.

Well, as Derek said: The string is looked up in gtk20's translation domain. If 
you look into the source file, you'll notice the dgettext() call around it. 
In a way, the fact that it shows up in gnucash.pot is a technical deficiency 
of the xgettext program. We can't do anything about that.

> 15. Please clarify the problem with these strings. Currently, we are
> unlikely to be able to translate them usefully.
>
> #.Translators FIXME: It is unclear whether these strings should
> #.really be translated, and if yes, into which translation.
> #: ../src/import-export/qif/qif-parse.c:102
> msgid "type:bank"
> msgstr ""
> 
> #: ../src/import-export/qif/qif-parse.c:103
> msgid "type:cash"
> msgstr ""
> (...)

The whole program part in the directory import-export/qif/* is a 
not-yet-completed feature and unusued currently. We will probably try to 
exclude the files from that directory from xgettext extraction, but it will 
take some time to set this up correctly. For now, just leave those 
untranslated.

> 18. Your estimated tax quarters are incorrect. They should each be
> three months, but two of them are two months, and four months:
>
> (...)
> #.src/report/locale-specific/us/taxtxf.scm
> #.src/report/locale-specific/us/taxtxf-de_DE.scm
> #: ../intl-scm/guile-strings.c:272
> #: ../intl-scm/guile-strings.c:362
> msgid "Apr 1 - May 31"
>
> This is only two months. It should be:
>
> + "Apr 1 - Jun 30"

This file is *not* a general tax-related report. Instead, it implements and 
shows *only* some US tax-relevant information. You may or may not believe 
this, but apparently in the US the tax quarters are indeed different from the 
normal calendar quarters. At least that's what I understand from the comment 
at taxtxf.scm:100.  (The taxtxf-de_DE.scm file is an even more experimental 
file that is invisible to normal users anyway.)

I've added some comments to those strings in the Scheme source code, but 
unfortunately due to our way of extracting the translation strings from 
Scheme, the comments will not show up in the pot file.

> 20.
> #.src/report/locale-specific/us/taxtxf.scm
> #: ../intl-scm/guile-strings.c:330
> msgid "Taxable Income / Deductible Expenses / Export to .TXF file"
>
> - Deductible
> + Deductable

Derek said the current form is currect.

> 21.
> #.src/report/standard-reports/trial-balance.scm
> #: ../intl-scm/guile-strings.c:524
> msgid ""
> "Do not net, but show gross debit/credit adjustments to these
> accounts. "
> "Merchandising businesses will normally select their inventory
> accounts here."
>
> "net" is not a verb. I suggest:
>
> + "Do not calculate net value: show..."

The trial-balance.scm is still a more or less experimental file, too, but I 
also don't know what this means. Anyone?

> 22.
> #.src/report/standard-reports/category-barchart.scm
> #: ../intl-scm/guile-strings.c:626
> msgid "Income Barchart"
>
> - Barchart
> + Bar chart
>
> (This error occurs in several strings in the PO file)

Well, we've been calling those graphical report "Barchart" and "Piechart" for 
years now. Could someone enlighten me whether this has been wrong all the way 
since we added them back in 2000? If yes, then indeed this should turn 
into "Bar chart", "Scatter plot", "Pie chart", or rather the capitalized "Bar 
Chart" etc.

> 24.
> #.src/report/standard-reports/income-statement.scm
> #.src/report/standard-reports/balance-sheet.scm
> #: ../intl-scm/guile-strings.c:890
> #: ../intl-scm/guile-strings.c:2048
> msgid "Displays accounts which exceed the depth limit at the depth
> limit"
>
> ??
>
> "the depth limit at the depth limit" seems unnecessary. Please clarify.

Some accounts exceed the depth limit (of the account tree) and for that reason 
they would not be shown. When checking this checkbox, those accounts will be 
shown, just not at their actual depth but instead at the depth limit's depth.

Maybe this option is stupid, but that's what it does. Any proposals for a 
better wording?

> 26.
> #.src/report/standard-reports/cash-flow.scm
> #: ../intl-scm/guile-strings.c:1352
> #, c-format
> msgid "%s - %s to %s for"
>
> Please include a msgctxt string or comment explaining what the
> placeholders stand for. In other languages, "to" and "for" aren't
> necessarily translated the same in different circumstances. We need to
> know the meaning of the string, in order to translate it correctly.

I've just looked up for myself in the source: This is the title string of the 
report page. The first %s is the report name (usually "Cash Flow"). The 
second and third %s is the starting and ending date of the period covered by 
this report.

I have no idea why this string ends with "for" and what is supposed to show up 
after this. Anyone who has used this report?

Again, unfortunately we cannot add a translator's comment here in the Scheme 
source that will show up in the pot file. We might change that string into 
something more obvious, though. Probably having the "%s to %s" as a separate 
translation and then building the rest from this.

> 29.
> #.src/business/business-reports/fancy-invoice.scm
> #.src/business/business-reports/easy-invoice.scm
> #.src/business/business-reports/invoice.scm
> #: ../intl-scm/guile-strings.c:3256
> #: ../intl-scm/guile-strings.c:3462
> #: ../intl-scm/guile-strings.c:3660
> msgid "Display each entry's total total tax"
>
> Do we need "total total" ?

Derek needs to comment on this.