GNOME Bugzilla – Bug 134089
Non-translator-friendly strings of function description
Last modified: 2009-06-27 22:21:07 UTC
There are a lot of function descriptions. All of them are in the form of "@FUNCTION=FUNCTION\n" "@SYNTAX=FUNCTION(arg1,arg2...)\n" "@DESCRIPTION=...\n" "\n" "args explaination.\n" "\n" "@EXAMPLES=..." "\n" "@SEEALSO=..." Why not split the form out of the content? I'll provide an example to show how it will be from the translation's view.
Created attachment 24295 [details] [review] Patch to plugins/fn-complex/functions.c
Sorry, I've reversed the order of the orginal file and the modified one. Lines marked with '-' should be the modified one. Thus, the translatiors will only need to translate the actual content, rather the form itself. Of course, the better way is to introduce a new strings class/structure, which will generate descriptoins based on its members. Please note, I've singled out "* This function is Excel compatible.", because it is commonly used by a lot of functions. The same applies to the sample data of financial functions.
This has been known for a while and a proper solution is being considered for the 1.3 series.
How is this going?
We've got a design but unfortunately it is too late in the cycle to implement it. As soon as 1.4 ships we're going to start on the tools to migrate the current translations into the new format.
It seems that the situation never changed.
Actually we've taken a big step towards fixing this. There is now a design in place, and some of the functions have been converted.
what is the timeline scheduled for this change?
We're going to audit and transfer all of the function docs as soon as gnumeric branches. That should be some time this month.
Still the case in 1.7.0
Well, it is really boring work to change all those descriptions, even with appropriate use of regular expressions. I have just committed changes to all the statistics functions. So at least we are on the right track. I will try toi find someone to change some more functions.
*** Bug 125229 has been marked as a duplicate of this bug. ***
*** Bug 117655 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 587156 ***