GNOME Bugzilla – Bug 114927
more string issues
Last modified: 2004-12-22 21:47:04 UTC
I am reviewing the Swedish translation of gnumeric, and in the process I sometimes stumble upon english strings with issues. They are mostly trivial, but this kind of thing can really affect the impression users get from an application. #: plugins/derivatives/options.c:142 #, no-c-format msgid "" "@FUNCTION=CUM_BIV_NORM_DIST\n" "@SYNTAX=CUM_BIV_NORM_DIST(a,b,rho)\n" "@DESCRIPTION=CUM_BIV_NORM_DIST calculates the cumulative bivariatenormal " "distribution from parameters a, b & rho" -- Should probably be "bivariate normal" --- #: plugins/excel/ms-excel-write.c:3691 #, c-format msgid "" "Some content will be lost when saving as excel.It only supports %d rows, and " "this workbook has %d" -- "Excel" should likely be capitalized. Maybe even use "MS Excel", as that is the term used in other places. --- #: plugins/fn-complex/functions.c:506 msgid "" "@FUNCTION=IMARGUMENT\n" "@SYNTAX=IMARGUMENT(inumber)\n" "@DESCRIPTION=IMARGUMENT returns the argument theta of a complex number, i. " "e. the angle in radians from the real axis to the representation of the " "number in polar coordinates.\n" "\n" -- The "i.e." expression should likely not be split. I could be wrong, though. --- #: plugins/fn-database/functions.c:264 (and also #: plugins/fn-database/functions.c:337, #: plugins/fn-database/functions.c:409, #: plugins/fn-database/functions.c:479, #: plugins/fn-database/functions.c:561, #: plugins/fn-database/functions.c:635 #: plugins/fn-database/functions.c:706 #: plugins/fn-database/functions.c:777 #: plugins/fn-database/functions.c:849 #: plugins/fn-database/functions.c:1065 which all share the relevant parts of the text below) msgid "" "@FUNCTION=DAVERAGE\n" "@SYNTAX=DAVERAGE(database,field,criteria)\n" "@DESCRIPTION=DAVERAGE function returns the average of the values in a list " "or database that match conditions specified.\n" "\n" "@database is a range of cells in which rows of related information are " "records and columns of data are fields. The first row of a database contains " "labels for each column. \n" "\n" "@field specifies which column is used in the function. If @field is an " "integer, for example. 2, the second column is used. Field can also be the " -- Should be "for example 2, " "label of a column. For example, ``Age'' refers to the column with the label " "``Age'' in @database range. \n" "\n" "@criteria is the range of cells which contains the specified conditions. " "The first row of a @criteria should contain the labels of the fields for " "which the criterias are for. Cells below the labels specify conditions, for " "example, ``>3'' or ``<9''. Equality condition can be given simply by " -- Should be "example ``>3´´ " "specifing a value, e.g. ``3'' or ``John''. Each row in @criteria specifies " "a separate condition, i.e. if a row in @database matches with one of the " "rows in @criteria then that row is counted in (technically speaking boolean " "OR between the rows in @criteria). If @criteria specifies more than one " "columns then each of the conditions in these columns should be true that the " "row in @database matches (again technically speaking boolean AND between the " "columns in each row in @criteria). \n" -- Suggested improvement of the section: "Each row in @criteria specifies a separate condition. If a row in @database matches with any row in criteria then that row is counted (technically speaking this is a boolean OR between the rows in @criteria). If @criteria specifies more than one column, then each of the conditions in the specified columns must be true for the row in @database to match (again, technically speaking this is a boolean AND between the columns in each row in @criteria).\n" -- Also, there should be a line break ("\n") between the end of the text and the @EXAMPLES section - about half of the instances above has it, the other half doesn't. --- #: src/dialogs/mean-tests.glade.h:10 msgid "Population Variances are:" #: src/dialogs/mean-tests.glade.h:14 msgid "Unknown _Pop. Var. are:" #: src/dialogs/mean-tests.glade.h:15 msgid "Variable _1 Pop. Variance:" #: src/dialogs/mean-tests.glade.h:17 msgid "Variable _2 Pop. Variance:" -- The term "Population Variance" should probably be written the same way in all of these (there may be more that I haven't noted). My suggestion is to write it out in full. I will likely have many more as time goes by (this represents about 10% of the po-file), but if you feel these are frivolous and a waste of time I'll refrain from filing more of them.
These are good please keep filing. I've applied most of them. not the wording change on the criteria description. The docs folk can look at that, and the maintainer of the stats tools should weigh in on the population variance terminology.
With the new mean test dialog it is not necessarry anymore to try to save dialog width, so I have changed the `pop var' abbreviations to complete words. So only the criteria description remains an issue in this report.
Reporter suggests: "Each row in @criteria specifies a separate condition. If a row in @database matches with any row in criteria then that row is counted (technically speaking this is a boolean OR between the rows in @criteria). If @criteria specifies more than one column, then each of the conditions in the specified columns must be true for the row in @database to match (again, technically speaking this is a boolean AND between the columns in each row in @criteria)." That's better than the original but the sentences are a little long. You might want to change to that to 2 paragraphs: "Each row in @criteria specifies a separate condition. If a row in @database matches a row in @criteria, then that row is counted. Technically speaking, this a boolean OR operation between the rows in @criteria. If @criteria specifies more than one column, then each of the conditions in the specified columns must be true for the row in @database to match. Technically speaking, this is a boolean AND operation between the columns in @criteria." I don't know what is meant by "counting" or "matching" but I assume that those are either defined earlier, or generally known to people who use this sort of thing.
fixed in cvs