GNOME Bugzilla – Bug 312746
Errors in the gnumeric-functions po file
Last modified: 2009-08-06 03:22:24 UTC
1. In this string, two lines have "is is", marked by *** #: ../plugins/derivatives/options.c:921 #, no-c-format msgid "" "@FUNCTION=OPT_MILTERSEN_SCHWARTZ\n" "@SYNTAX=OPT_MILTERSEN_SCHWARTZ(call_put_flag,p_t,f_t,x,t1,t2,v_s,v_e,v_f," "rho_se,rho_sf,rho_ef,kappa_e,kappa_f)\n" "@DESCRIPTION=OPT_MILTERSEN_SCHWARTZ models the theoretical price of options " "on commodities futures according to Miltersen & Schwartz. \n" "@call_put_flag is 'c' or 'p' to indicate whether the option is a call or a " "put.\n" "@p_t is a zero coupon bond with expiry at option maturity.\n" *** "@f_t is is the futures price.\n" *** "@x is is the strike price.\n" "@t1 is the time to maturity of the option.\n" <snip> 2. Starting with string: #: ../plugins/derivatives/options.c:1091 several strings include this line: "@rate is the risk annualized free rate of interest.\n" Do you mean: "@rate is the _annualized risk-free_ rate of interest.\n" ? 3. In this string: #: ../plugins/derivatives/options.c:1415 #, no-c-format msgid "" "@FUNCTION=OPT_FORWARD_START\n" "@SYNTAX=OPT_FORWARD_START(call_put_flag,spot,alpha,time1,time,rate," "volatility,cost_of_carry)\n" "@DESCRIPTION=OPT_FORWARD_START models the theoretical price of forward start " "options\n" " @call_put_flag is 'c' or 'p' to indicate whether the option is a call or a " "put.\n" "@spot is the spot price of the underlying asset.\n" "@alpha is a fraction that set the strike price the future date @time1.\n" <snip> The line above seems to be missing a word. Do you mean: "@alpha is a fraction that set the strike price _at_ the future date @time1.\n" ? 4. Beginning with this string, there seem to be two sentences jammed together: #: ../plugins/derivatives/options.c:1723 <snip> "@cost_of_carry is the leakage in value of the underlying asset of the " "underlying option.for common stocks, this would be the dividend yield.\n" Do you mean: "@cost_of_carry is the leakage in value of the underlying asset of the " "underlying _option. For_ common stocks, this would be the dividend yield.\n" ? or you could use a semi-colon: "underlying _option; for_ common stocks, this would be the dividend yield.\n" ? but you still need the single space. 5. In this string: #: ../plugins/derivatives/options.c:1811 <snip> "@DESCRIPTION=OPT_EXTENDIBLE_WRITER models the theoretical price of " "extendible writer options. These are options that can be exercised at an " "initial period, @time1, or their maturity extended to @time2 if the option " "is out of the money at @time1.\n" Do you mean the option can be exercised _in_ a particular time period, or _at_ a particular time? If the former, then this is correct: These are options that can be exercised _within_ an " "initial period, @time1, or their maturity extended to @time2 if the option " "is out of the money at @time1.\n" If the latter, then: These are options that can be exercised at an " "initial point in time, @time1, or their maturity extended to @time2 if the option " "is out of the money at @time1.\n" Or perhaps you mean something else? 6. In this string: #: ../plugins/derivatives/options.c:2152 "@DESCRIPTION=OPT_FIXED_STRK_LKBK models the theoretical price of an option " "where the holder of the option may exercise on expiry at the most favourable " "price observed during the options life of the underlying asset.\n" This is exactly the same description as the previous string: "@DESCRIPTION=OPT_FLOAT_STRK_LKBK Should it be? I find that a bit confusing, so please forgive my ignorance. I prefer pure maths. ;) On this line: "@strike is the strike prices at which the option is struck.\n" How many prices are there? If one: "@strike _is the strike price_ at which the option is struck.\n" If more: "@strike _are the strike prices_ at which the option is struck.\n" 7. In this string: #: ../plugins/fn-database/functions.c:269 This line: "The first row of a @criteria should contain the labels of the fields for " "which the criteria are for. could be: "The first row of a @criteria should contain the labels of the fields for " "which the criteria exist." 8. In this string: #: ../plugins/fn-database/functions.c:810 the word "populations" starts to occur. "Population" is usually a mass noun, already plural, and it fits correctly with the verb used. For example: The _populations consists_ of numbers that " "match conditions specified.\n" is incorrect, where\ The _population consists_ of numbers that " "match conditions specified.\n" or The _populations consist_ of numbers that " "match conditions specified.\n" is correct. The word "populations" also occurs in later strings. 9. In this string (and following strings): #: ../plugins/fn-date/functions.c:135 This line appears: "A unix time is the number of seconds since midnight January 1, 1970.\n" Is "a Unix time" a unit? Or do you mean: "Unix time is the number of seconds since midnight January 1, 1970.\n" which refers to it as a variable? 10. In this string: #: ../plugins/fn-date/functions.c:465 msgid "" "@FUNCTION=NOW\n" "@SYNTAX=NOW ()\n" "@DESCRIPTION=NOW returns the serial number for the date and time at the time " "it is evaluated.\n" "\n" "Serial Numbers in Gnumeric are represented as _follows:The_ integral part <snip> there is a missing space after the colon in the line above, and there should not be a capital letter after a colon. The line should read: "Serial Numbers in Gnumeric are represented as _follows: the_ integral part <snip>" 11. This string: #: ../plugins/fn-eng/functions.c:630 msgid "" "@FUNCTION=BESSELJ\n" "@SYNTAX=BESSELJ(x,y)\n" "@DESCRIPTION=BESSELJ function returns the Bessel function with @x is where " "the function is evaluated. doesn't quite make sense. BESSELJ function returns the Bessel function with @x is where " "the function is evaluated. ?? 12. This string: #: ../plugins/fn-eng/functions.c:1274 msgid "" "@FUNCTION=GESTEP\n" "@SYNTAX=GESTEP(x[,y])\n" "@DESCRIPTION=GESTEP function test for if @x is >= @y, returning 1 if it is " "so, and 0 otherwise. should perhaps say: "GESTEP function _tests if_ @x is >=y, returning 1 if so and 0 otherwise." 13. In this string: #: ../plugins/fn-financial/functions.c:453 msgid "" "@FUNCTION=INTRATE\n" "@SYNTAX=INTRATE(settlement,maturity,investment,redemption[,basis])\n" "@DESCRIPTION=INTRATE calculates and returns the interest rate of a fully " "vested security.\n" "\n" "@settlement is the settlement date of the security. @maturity is the " "maturity date of the security. @investment is the prize of the security paid " "at @settlement date and @redemption is the amount to be received at " "@maturity date.\n" Do you mean "the _prize_ of the security paid", or "the _price_ of the security paid"? 14. In this string: #: ../plugins/fn-financial/functions.c:1061 msgid "" "@FUNCTION=SYD\n" "@SYNTAX=SYD(cost,salvage_value,life,period)\n" "@DESCRIPTION=SYD function calculates the sum-of-years digits depreciation " "for an asset based on its cost, salvage value, anticipated life and a " "particular period. This method accelerates the rate of the depreciation, so " "that more depreciation expense occurs in earlier periods than in later ones. " "The depreciable cost is the actual cost minus the salvage value. The useful " "life is the number of periods (typically years) over with the asset is " "depreciated.\n" The line above should probably be: "the number of periods (typically years) _over which_ the asset is depreciated" ? 15. In this string: #: ../plugins/fn-financial/functions.c: <snip> "@EXAMPLES=\n" "For example, if you deposit $10,000 in a savings account that earns an " "interest rate of 6%. To calculate _home many years_ it will take to double " "your investment use NPER as follows:\n" it should probably say: "To calculate _how many years_ it will take to double " "your investment ..." 16. In this string: #: ../plugins/fn-financial/functions.c:2744 msgid "" "@FUNCTION=YIELDMAT\n" "@SYNTAX=YIELDMAT(settlement,maturity,issue,rate,pr[,basis])\n" "@DESCRIPTION=YIELDMAT calculates the annual yield of a security for which " "the interest is _payed_ at maturity date.\n" I think you mean "paid". 17. In this string: #: ../plugins/fn-logical/functions.c:44 msgid "" "@FUNCTION=AND\n" "@SYNTAX=AND(b1, b2, ...)\n" "@DESCRIPTION=AND implements the logical AND function: the result is TRUE if " "all of the expressions evaluate to TRUE, otherwise it returns FALSE.\n" "\n" "@b1 _trough_ @bN are expressions... " "@b1 _through_ @bN are expressions..." This error occurs in following strings. 18. In this string: #: ../plugins/fn-lookup/functions.c:627 msgid "" "@FUNCTION=HLOOKUP\n" "@SYNTAX=HLOOKUP(value,range,row[,approximate,as_index])\n" "@DESCRIPTION=HLOOKUP function finds the col in range that has a first row " "cell similar to @value. If @approximate is not true it finds the col with " "an exact equivalence. If @approximate is true, then the values must be " "sorted in order of ascending value for correct function; in this case it " "finds the col _with value less than @value it returns the value_ in the col " "found at a 1-based offset in @row rows into the @range. @as_index returns " "the 0-based offset that matched rather than the value.\n" In the preceding string, there was a full stop and capital letter separating these phrases: "sorted in order of ascending value for correct function; in this case it " "finds the col _with value less than @value. It returns the value_ in the col " "found at a 1-based offset in @row rows into the @range." 19. In this string: #: ../plugins/fn-math/functions.c:146 msgid "" <snip> "@EXAMPLES=\n" "LCM(2,13) equals to 26.\n" "LCM(4,7,5) equals to 140.\n" "equals"? not "equals to" also in following strings 20. In these two strings: #: ../plugins/fn-r/functions.c:410 ../plugins/fn-r/functions.c:435 #: ../plugins/fn-r/functions.c:462 msgid "n1:the first number of degrees of freedom of the distribution" msgstr "n1:số bậc tự do thứ nhất của phân phối." #: ../plugins/fn-r/functions.c:411 ../plugins/fn-r/functions.c:436 #: ../plugins/fn-r/functions.c:463 msgid "n2:the first number of degrees of freedom of the distribution" Should the _first_ number of degrees of freedom be both n1 and n2? (Sorry, I'm not a statistician. Just making sure.) 21. Do you want these strings translated? I could, for example, substitute the Greek letters for their names, and translate the other words, but they don't look as though they will be displayed to the user. #: ../plugins/fn-r/functions.c:1194 msgid "x,mu,sigma,give_log" #: ../plugins/fn-r/functions.c:1202 msgid "x,mu,sigma,lower_tail,log_p" #: ../plugins/fn-r/functions.c:1210 msgid "p,mu,sigma,lower_tail,log_p" #: ../plugins/fn-r/functions.c:1218 msgid "x,logmean,logsd,give_log" #: ../plugins/fn-r/functions.c:1226 ../plugins/fn-r/functions.c:1234 msgid "x,logmean,logsd,lower_tail,log_p" #: ../plugins/fn-r/functions.c:1242 ../plugins/fn-r/functions.c:1362 msgid "x,shape,scale,give_log" #: ../plugins/fn-r/functions.c:1250 ../plugins/fn-r/functions.c:1370 msgid "x,shape,scale,lower_tail,log_p" msgstr "" #: ../plugins/fn-r/functions.c:1258 ../plugins/fn-r/functions.c:1378 msgid "p,shape,scale,lower_tail,log_p" #: ../plugins/fn-r/functions.c:1266 msgid "x,a,b,give_log" #: ../plugins/fn-r/functions.c:1274 msgid "x,a,b,lower_tail,log_p" etc. 22. In this string: #: ../plugins/fn-random/functions.c:1074 msgid "" "@FUNCTION=RANDNORMTAIL\n" "@SYNTAX=RANDNORMTAIL(a,sigma)\n" "@DESCRIPTION=RANDNORMTAIL_ returns a random variates_ from the upper tail of a " "normal distribution with standard deviation @sigma. The values returned are " Do you mean "variates" plural, or "variate" singular? if the former, shouldn't it be: "_returns random variates_ from the upper tail of a " "normal distribution with standard deviation @sigma. " ? 23. In this string: #: ../plugins/fn-stat/functions.c:4077 msgid "" <snip> "If @stat is TRUE, extra statistical information will be returned. Extra " "statistical information is written bellow the regression line coefficients " "in the result array. "below" also in: #: ../plugins/fn-stat/functions.c:4853 24. In this string: #: ../plugins/gda/plugin-gda.c:203 msgid "" "@FUNCTION=READDBTABLE\n" "@SYNTAX=READDBTABLE(dsn,username,password,table)\n" "@DESCRIPTION=The READDBTABLE function lets you get the contents of a table, " "as stored in _a database.For using it,_ you need first to set up a libgda data " "source.\n" there is a missing space between two sentences. It should be: "as stored in _a database. For using it,_ you need first to set up a libgda data " "source.\n" 25. In this string: #: ../plugins/sample_datasource/sample_datasource.c:274 #, no-c-format msgid "" "@FUNCTION=atl_last\n" "@SYNTAX=ATL_LAST (tag)\n" "@DESCRIPTION=ATL_LAST is a sample implemention of a real time data source. " "It takes a string tag and monitors the named pipe /tmp/atl for changes to " "the value of that tag.\n" "\n" "* This is no intended to be generally enabled ..." "This is not intended..." from Clytie, Vietnamese translator
*** Bug 312751 has been marked as a duplicate of this bug. ***
1 fixed 2 fixed [16 times] 3 not sure 4 cannot find 5 not sure 6 not sure 7 not sure 8 fixed 9 Either would be right. Not changing. 10 fixed 11 not sure 12 fixed 13 fixed 14 fixed 15 fixed 16 fixed 17 fixed [3 times] 18 not sure 19 fixed. Similar problem in help_power. 20 fixed 21 not sure 22 not sure 23 fixed 24 fixed 25 fixed Whew! Some of these typos are quite old -- thanks for paying attention to details.
My pleasure. :) Morten, I sent some important queries on the gnumeric .po files to the bug address, jody@gnome.org. Should I send them to you? I really need them sorted out, so I can translate the files correctly and get them both in. from Clytie, Vietnamese translator.
*** Bug 312987 has been marked as a duplicate of this bug. ***
You can send them to me, to the mailing list, or file them here in bugzilla. (Jody has been busy with real life for a while.)
That real life does get in the way of essential computing, doesn't it? Fortunately, I don't have one. ;) OK, here are the questions, thanks for the offer. I've submitted the files, because they were mostly untranslated before, and what we have now is a working translation, but I want to resolve these issues, so it can be the best possible translation, the two programs working together as they should. Questions pasted in below here. from Clytie, Vietnamese translator Hi Jody :) I've just translated gnumeric-functions into Vietnamese (phew), submitted a list of typos as bugs from the .po file, and I'm now working my way through the gnumeric .po file. I need to check with you about translating the names of variables. For example, this string in gnumeric functions: #: ../plugins/derivatives/options.c:222 msgid "" "@FUNCTION=OPT_BS\n" "@SYNTAX=OPT_BS(call_put_flag,spot,strike,time,rate,volatility [," "cost_of_carry])\n" "@DESCRIPTION=OPT_BS uses the Black-Scholes model to calculate the price of a " "European option using call_put_flag, @call_put_flag, 'c' or 'p' struck at " "@strike on an asset with spot price @spot.\n" "@time is the time to maturity of the option expressed in years.\n" "@rate is the risk-free interest rate.\n" "@volatility is the annualized volatility, in percent, of the asset for the " "period through to the exercise date. \n" "@cost_of_carry is the leakage in value of the underlying asset, for common " "stocks, this would be the dividend yield.\n" "* The returned value will be expressed in the same units as @strike and " "@spot.\n" "\n" shows a list of variables or options in the syntax line. I did not translate them there. However, these lists are presented for translation in the gnumeric .po file. I'm happy to translate them, but I want to get them right. 1. I can translate all these variable names? call_put_flag,spot,strike,time,rate,volatility [," "cost_of_carry]) etc.? 2. Where there are names of Greek letters, I can use those symbols? (rho, gamma) I've used Unicode mathematical symbols wherever I can, although the .po file formatting (basic text file with UTF-8) doesn't allow for full equation-editing. 3. In the gnumeric .po file, strings start out with a space between terms, e.g. #: ../plugins/derivatives/options.c:2336 msgid "call_put_flag, spot, strike, t1, t2, rate, d, volatility" but subsequent strings have no spaces, e.g. #: ../plugins/derivatives/options.c:2386 msgid "" "call_put_flag,fut_price1,fut_price2,strike,time, rate,volatility1," "volatility2,rho" Is this OK? Do I simply follow whatever structure the msgid string has? In the second string, would it be OK to use the Greek symbol for rho? I'm probably going to have more questions as I go through, but it's better to get things right, so the translation works. I thoroughly enjoy the pure maths, but stats is not my thing. Back to the .po file... from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN
I would suggest that you do not use actual greek letters for this. It is likely to confuse more than help people who deal with options. Apart from this, for now just keep things like the space structure of args. Things are going to change -- when we get the time -- to something that looks more like the "R" plugin.
Also note that the ASC description text lists a CHAR example. The first description sentence of ASC is "ASC a compatibility function that is meaningless in Gnumeric.", it probably lacks a verb.
As far as I can tell the only item left here is: 18. In this string: #: ../plugins/fn-lookup/functions.c:627 msgid "" "@FUNCTION=HLOOKUP\n" "@SYNTAX=HLOOKUP(value,range,row[,approximate,as_index])\n" "@DESCRIPTION=HLOOKUP function finds the col in range that has a first row " "cell similar to @value. If @approximate is not true it finds the col with " "an exact equivalence. If @approximate is true, then the values must be " "sorted in order of ascending value for correct function; in this case it " "finds the col _with value less than @value it returns the value_ in the col " "found at a 1-based offset in @row rows into the @range. @as_index returns " "the 0-based offset that matched rather than the value.\n" In the preceding string, there was a full stop and capital letter separating these phrases: "sorted in order of ascending value for correct function; in this case it " "finds the col _with value less than @value. It returns the value_ in the col " "found at a 1-based offset in @row rows into the @range."
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.