After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 312986 - Errors in main gnumeric .po file
Errors in main gnumeric .po file
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: General
unspecified
Other All
: Normal minor
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks: 381564
 
 
Reported: 2005-08-09 10:07 UTC by Clytie Siddall
Modified: 2009-05-16 17:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Clytie Siddall 2005-08-09 10:07:01 UTC
1.
#: ../plugins/fn-r/plugin.xml.in.h:2
msgid ""
"Statistical Functions with naming a calling conventions from The R Project"

??

"with naming and calling conventions from The R Project"?

"with naming/calling conventions from The R Project"?


2.
#: ../plugins/paradox/paradox.c:73 ../plugins/paradox/paradox.c:122
msgid "Error while opening paradox file."

"paradox" turns out to be the name of a type of file, so leaving it without the capital letter here, means 
we try to translate it. If it's a name, we probably shouldn't. What do you want us to do, here?


3.
#: ../plugins/perl-func/plugin.xml.in.h:3
msgid "Sample Perl plugin providing some (useless) functions."

Um, would you like to expound? Is this a useful statement?

also here:

#: ../plugins/py-func/plugin.xml.in.h:3
msgid "Sample Python plugin providing some (useless) functions."


4.
#: ../schemas/gnumeric-dialogs.schemas.in.h:1
msgid ""
">This value determines the default setting in the Print Setup dialog whether "
"print grid lines. Please use the Print Setup dialog to edit this value."

This needs one or two extra words:

#: ../schemas/gnumeric-dialogs.schemas.in.h:1
msgid ""
">This value determines the default setting in the Print Setup dialog: whether to"
"print grid lines or not. Please use the Print Setup dialog to edit this value."

 
5.
These just don't work:

#: ../schemas/gnumeric-dialogs.schemas.in.h:66
msgid ""
"This value determines the default number of pages a printout of the current "
"sheet is suppposed to be high. 0 disables scaling. Please use the Print "
"Setup dialog to edit this value."

#: ../schemas/gnumeric-dialogs.schemas.in.h:67
msgid ""
"This value determines the default number of pages a printout of the current "
"sheet is suppposed to be wide. 0 disables scaling. Please use the Print "
"Setup dialog to edit this value."

I'd suggest:

"This value determines the default number of pages that make up the height of a printout of the 
current "
"sheet."

and

"This value determines the default number of pages that make up the width of a printout of the current 
"
"sheet."


6.
Then you have a series of strings with this structure:

#: ../schemas/gnumeric-dialogs.schemas.in.h:68
msgid ""
"This value determines the default setting in the Print Setup dialog whether "
"to center pages horizontally. Please use the Print Setup dialog to edit this "
"value."

which is unclear.

I suggest this structure instead (for all the strings of this type):

"This value determines whether the default setting in the Print Setup dialog is to center pages 
horizontally or not."

which is correct English and communicates what you are trying to say.


7.
#: ../schemas/gnumeric-general.schemas.in.h:14
msgid ""
"If `lag' is 0, gnumeric recalculates all auto expressions immediately after "
"every change. Non-zero values of `lag' allow gnumeric to acumulate more "
"changes before each recalculation. I

"accumulate"


8.
#: ../src/dialogs/autocorrect.glade.h:10
msgid "INitial CApitals"

If only the initial letter is capitalized, why are two letters capitalized in each word?


9.
In this string, all the listed items are names of functions. Should they be translated?

#: ../src/dialogs/consolidate.glade.h:9
msgid ""
"SUM\n"
"MIN\n"
"MAX\n"
"AVERAGE\n"
"COUNT\n"
"PRODUCT\n"
"STDEV\n"
"STDEVP\n"
"VAR\n"
"VARP"


10.
#: ../src/dialogs/dialog-about.c:111
msgid "UI Polish and all round bug fixer"

Do you mean "polish" as in refining something, or "Polish" as in the language of Poland?


11.
#: ../src/dialogs/dialog-analysis-tools.c:1046
msgid "No statistics is selected."

"Statistics" is a mass noun, already plural. You need:

msgid "No statistics are selected."


12. What is the purpose of this string??

#: ../src/dialogs/dialog-stf-export.glade.h:1
msgid ""
"\"\n"
"'\n"
"`\n"


13.
#: ../src/dialogs/dialog-stf-export.glade.h:17
msgid ""
"Move the selected sheet to the end of the list of to be _exported exported_ "
"sheets to be exported last."

Do you really need the double "exported" in there? Other similar strings don't have it.



14.
#: ../src/dialogs/histogram.glade.h:3
msgid "Bin _range:"

What do you mean when you use "bin" like this? I'm assuming it's not a rubbish bin. Binary?


15.
#: ../src/tools/solver/reports-write.c:546
msgid "Maximum number of iterations exceeded: optimization interupted"

"interrupted"


16.
#: ../src/tools/solver/solver.c:494
msgid ""
"Failure _setting setting_ the maximum solving time with this solver, try a "
"different algorithm."

Only one "setting" needed.


17. Strings of this kind:

#: ../src/cmd-edit.c:422
#, c-format
msgid "Shift rows %s"

#: ../src/cmd-edit.c:423
#, c-format
msgid "Shift row %s"

assume that other languages have the same number of plurals as English does. They don't. My 
language has no plurals in that sense, and some languages have several. Therefore, please use the 
gettext plurals feature when you want to differentiate singular and plural, resulting in a plurals string 
block automatically created by the plurals header for each language. The resulting file will then create 
the correct plurals pattern in each version of the program. Please see this node in the gettext manual:

http://www.gnu.org/software/gettext/manual/html_mono/gettext.html#SEC150


18.
#: ../src/gnm-plugin.c:407
#, c-format
msgid "User interface with %d action"

It's not clear whether the variable is a number or a descriptor. This would determine the position in the 
translation (if a number, before the word "action", if a descriptor, after). A translator-comment would 
help here.


19.
Do you really want any part of this translated?

#: ../src/mathfunc.c:3844 ../src/mathfunc.c:4314
msgid "): ncalc (=%ld) != nb (=%ld); alpha=%"

or this?

#: ../src/mathfunc.c:3847 ../src/mathfunc.c:4317
msgid ",nu=%"


20.
#: ../src/sheet.c:619
msgid "Control whether outlines symbols are shown below."

"outline symbols" ?

"outlines' symbols" ?

but not

"outlines symbols"

and in following strings.


21. Should I translate these errors?

#: ../src/value.c:54
msgid "#NULL!"

#: ../src/value.c:55
msgid "#DIV/0!"

#: ../src/value.c:56
msgid "#VALUE!"

#: ../src/value.c:57
msgid "#REF!"

#: ../src/value.c:58
msgid "#NAME?"

#: ../src/value.c:59
msgid "#NUM!"

#: ../src/value.c:60
msgid "#N/A"

#: ../src/value.c:61
msgid "#RECALC!"


22.
#: ../src/wbcg-actions.c:1704
msgid "Paste the definition a name, or names"

What does this mean?

"Paste the definition _of_ a name or names"  ?

from Clytie, Vietnamese translator
Comment 1 Morten Welinder 2005-08-25 15:37:23 UTC
1. Text is correct, but perhaps too technical.  ("Naming" refers to the name
of the function, "calling" refers to the order and meaning of the arguments.)

2. Fixed.

3. This is intentional.  This is sample code for plugin programmers, not the
spreadsheet user.

4. There is no need for "or not" in connection with "whether".  I do agree that
the colon makes it more readable, though, so I fixed that.

5. Not sure.

6. Not sure.

7. Fixed.

8. Because this string show the kind of typos this particular auto-corrector
fixes.

9. Not at this time.  We do not support translated function names yet.

10. Fixed.

11. Fixed.

12. It looks like the bug system mangled this, but I would guess that these
are line-ending choices.  I am not sure why you are asked to translate those.

13. Fixed.

14. "Bin" is correct and means something like "box" in the context of
histograms.

15. Fixed (twice).

16. Fixed.

17. This is covered by some other bug already.

18. Not sure.

19. No.  (This is tricky, generated code, so I have not fixed it yet.)

20. Fixed.

21. Not yet, I think.

22. Fixed.


Thanks!


This leaves 5, 6, 12, 18.
Comment 2 Andreas J. Guelzow 2009-05-16 17:24:35 UTC
5, 6, 12, 18 fixed

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.