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 624559 - Comments about FOURIER and CP1252 help texts and po-functions/README.translators
Comments about FOURIER and CP1252 help texts and po-functions/README.translators
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: General
git master
Other Linux
: Normal trivial
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2010-07-16 18:27 UTC by tokul
Modified: 2010-07-16 22:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description tokul 2010-07-16 18:27:39 UTC
#../plugins/fn-string/functions.c:62
#../plugins/fn-string/functions.c:135
"CP1252 (Windows-1252) is based on an early draft of ISO-8859-1, and contains all of its printable characters (but partially at different positions.)"

According to wikipedia CP1252 is superset of ISO-8859-1 and it matches all printable ISO-8859-1 characters. Without "partially at different positions". I think "different position" is when symbol uses x1 codepoint in charset1 and x2 codepoint in charset2. 0x00-0x7F codepoints match in US-ASCII, CP1252 and ISO-8859-1. 0xA0-0xFF codepoints match in CP1252 and in ISO-8859-1. The only difference is in 0x80-0x9F range. ISO-8859-1 has non-printable control characters there and CP1252 uses range for printable characters. ISO-8859-1 does not have printable characters that use different codepoints in CP1252.

http://en.wikipedia.org/w/index.php?title=Windows-1252&oldid=372527241


#../plugins/fn-tsa/functions.c:871
"Inverse:if false, the inverse Fourier transform is calculated. Defaults to false"

This does not sound right to me. If function defaults to inverse Fourier, then it should not be called FOURIER. Argument is boolean and boolean FALSE in programming means that something is not done that way. "Inverse = FALSE" - not inverse.


po-functions/README.translators says
"Argument names that appear in other strings are surrounded by @{} and you must translate the content of @{} exactly like you translated the argument name when it preceded the colon separator."

is it exactly the same or I can use different grammatical case. In some languages nominative case differs from other cases and translator might have to use complex language constructs to keep @{something} in nominative case.

Can you keep sane line length limits in po-functions/README.translators? It is supposed to be human readable and it is hardly readable in http://git.gnome.org/browse/gnumeric/tree/po-functions/README.translators.
Comment 1 Andreas J. Guelzow 2010-07-16 22:38:18 UTC
#../plugins/fn-tsa/functions.c:871 has been fixed.

You should think of the text surrounded by @{...} as the _names_ of the argument. So if we have:
Sequence: the data sequence to be transformed
we write:
If @{Sequence} is neither an n by 1 nor 1 by n array, this function returns #NUM!
rather than 
If the @{sequence} is ...

Of course, if in your language modification are done to proper names, you should probably apply the same modifications here too.
Comment 2 Andreas J. Guelzow 2010-07-16 22:53:39 UTC
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.