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 675000 - Errors in example's functions
Errors in example's functions
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Documentation
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Andreas J. Guelzow
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2012-04-27 22:27 UTC by Juan Matías Olmos
Modified: 2012-05-01 17:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Juan Matías Olmos 2012-04-27 22:27:45 UTC
All strings from 85 to 125 with examples of functions says:

function (argument, argument, argument)

and should be:

function (argument; argument; argument)

The arguments must be separated by semicolons. Current form return a "Invalid Expression" message when you try to put the example in Gnumeric.
Comment 1 Jean Bréfort 2012-04-28 05:20:08 UTC
This is a localization issue.
Comment 2 Andreas J. Guelzow 2012-04-28 06:02:01 UTC
In locale C 
function (argument, argument, argument)
is the correct invocation, in some other locales you need
function (argument; argument; argument).

In which locale are you working?

For which specific function are you seeing 
function (argument, argument, argument)?

What specifically do you mean with "all strings from 85 to 125"?
Comment 3 Juan Matías Olmos 2012-04-28 10:29:37 UTC
I speack spanish. I'm working on spanish localization.
I try to say, strings #85 to #125, as you can see en Gtranslator.
If "function (argument, argument, argument)" work fine, I believe you.
Comment 4 Jean Bréfort 2012-04-28 12:26:01 UTC
The english version is function(argument,argument,argument) (no spaces). In the spanish version, you need to replace commas by semicolons.
Comment 5 Jean Bréfort 2012-04-28 12:31:46 UTC
I was wrong, you can have spaces after the commas (or semicolon), but not betwwen the function name and the bracket.
Comment 6 Jean Bréfort 2012-04-28 12:33:59 UTC
In po-functions/es.po we have things like:

#: ../plugins/fn-database/functions.c:577
msgid "DSTDEV(A1:C7, \"Age\", A9:B11) equals 9.89949."
msgstr "DSTDEV(A1:C7; \"Edad\"; A9:B11) equivale a 9.89949."

This is correct for both languages.
Comment 7 Daniel Mustieles 2012-04-29 17:04:55 UTC
Could you please add some comments to these strings?

Since it is a very specific format, adding some comments to these strings would help translators to avoid mistakes.

Many thanks for your help
Comment 8 Juan Matías Olmos 2012-04-30 11:40:48 UTC
By the way, can I translate the names of the arguments for each function?
i.e.
#: ../plugins/fn-date/functions.c:426
msgid "second:second within the minute"
msgstr "segundo: segundo en el minuto"

#: ../plugins/fn-date/functions.c:427
msgid ""
"The TIME function computes the fractional day between midnight at the time "
"given by @{hour}, @{minute}, and @{second}."
msgstr ""
"La función TIME calcula la hora completa entre la medianoche y el tiempo "
"dado por @{hora}, @{minuto} y @{segundo}."
Comment 9 Jean Bréfort 2012-04-30 12:16:55 UTC
yes, you can.
Comment 10 Morten Welinder 2012-04-30 17:58:40 UTC
I don't see us adding comments to a large number of strings.  We can do
it to one if someone has a suggestion about what to put there.

Personally, I think we're mostly seeing a case where the normal "the
translator doesn't need to know the program being translated" assumption
breaks down.  We have already minimized the impact by taking 95% of the
expression samples out of the text that needs to be translated.

> msgid "second:second within the minute"
> msgstr "segundo: segundo en el minuto"

That wasn't meant to have a space after the colon.  But since I don't believe
we can document our way out of that, we should make sure that it doesn't
matter.
Comment 11 Morten Welinder 2012-04-30 18:08:02 UTC
> we should make sure that it doesn't matter.

Done.
Comment 12 Daniel Mustieles 2012-04-30 19:06:24 UTC
Morten, I've seen your commit... thanks! :)

About the comments in the string, I agree with you it is a hard job, but if it would be easy to "protect" your code from mistakes in translated string (like you've done with whitespaces) it could be the best solution.

Thanks again for your help
Comment 13 Andreas J. Guelzow 2012-04-30 22:40:36 UTC
We do have a gnumeric/po-functions/README.translators file. I guess we should add some comment regarding the 
function (argument, argument, argument)
--->
function (argument; argument; argument).
translation to it. The issue with the spaces not surrounding the colon is already described there.
Comment 14 Andreas J. Guelzow 2012-05-01 17:10:11 UTC
I have added the appropriate information to README.translators file.
Comment 15 Daniel Mustieles 2012-05-01 17:17:24 UTC
Many thanks Andreas :)