|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | Errors in the original strings | ||
|---|---|---|---|
| Product: | Internationalization | Reporter: | clytie |
| Component: | code | Assignee: | AOO issues mailing list <issues> |
| Status: | CONFIRMED --- | QA Contact: | |
| Severity: | Trivial | ||
| Priority: | P3 | CC: | issues |
| Version: | current | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Latest Confirmation in: | --- |
| Developer Difficulty: | --- | ||
Sorry, but there is no way to handle 25 issues in one issue. I have to identify the person for each and every fix. There is no way to assign 25 issues separately. I have to give it back to you, sorry. How is a translator supposed to know the module owning each string? "source", "sd", "src" or even "wizards" doesn't help. I would have reported each string against its own module, however time-wasting a process that might be, if I had been able to identify them. This it yet another barrier to translator participation. It is _not_ a straightforward process to report errors in the original strings. :( Reset assignee on issues not touched by assignee in more than 1000 days. |
While translating and reviewing the current SDF file, I have encountered quite a few errors, which devalue the appearance of the OpenOffice.org interface. 1. Split strings which should be replaced by a single string containing a placeholder (split strings are bad practice in localization, and also cause multiple errors when checking translations): (a) sd source\ui\app\strings.src 0 string STR_EXPORT_PATH_NOT_FOUND1 1 en-US The directory ' sd source\ui\app\strings.src 0 string STR_EXPORT_PATH_NOT_FOUND2 1 en-US ' does not exist. (b) svx source\dialog\impgrf.src 0 string RID_SVXRES_IMPORTGRAPHIC STR_PATH_NOT_FOUND1 0 en-US The directory ' svx source\dialog\impgrf.src 0 string RID_SVXRES_IMPORTGRAPHIC STR_PATH_NOT_FOUND2 0 en-US ' does not exist (c) sw source\ui\dialog\dialog.src 0 string STR_PATH_NOT_FOUND1 0 en-US The directory ' sw source\ui\dialog\dialog.src 0 string STR_PATH_NOT_FOUND2 0 en-US ' does not exist. (d) sw source\ui\dochdl\dochdl.src 0 string STR_NOGLOS1 0 en-US AutoText for Shortcut ' sw source\ui\dochdl\dochdl.src 0 string STR_NOGLOS2 0 en-US ' not found. (e) sw source\ui\uiview\view.src 0 string STR_NOGLOS1 0 en-US AutoText for Shortcut ' sw source\ui\uiview\view.src 0 string STR_NOGLOS2 0 en-US ' not found. 2. Double spaces (indicated by boxes). In the case of the gaps between sentences, this may have been an older typsetting behaviour. Some people still like to use it, but unfortunately, it causes "double-space" errors when checking translations, so each string formatted in this way wastes our time when we want to check our translation and get it submitted. So please avoid this formatting if possible. :) (a) Create a query by specifying the filters, input tables, field names,[][]and[][]properties for sorting or grouping. app.src#RID_STR_QUERIES_HELP_TEXT.string.text (b) Create a query[][]entering an SQL statement directly. app.src#RID_STR_QUERIES_HELP_TEXT_SQL.string.text (c) ~Confirm[][] password UserAdmin.src#DLG_PASSWORD.FT_PASSWORD_REPEAT.fixedtext.text (d) Note: When deleted, and thus inactive, records are[][] displayed, you will not be able to delete records from the data source. dbadmin.src#PAGE_DBASE.FT_SPECIAL_MESSAGE.fixedtext.text (e) The name for[][] the user interface '%s1' is already used by the XML filter '%s2'. Please enter a different name. xmlfilterdialogstrings.src#STR_ERROR_TYPE_NAME_EXISTS.string.text (f) File: [1],[][] Section: [2],[][]Key: [3], Value: [4] ActionTe.ulf#OOO_ACTIONTEXT_78.LngText.text ActionTe.ulf#OOO_ACTIONTEXT_122.LngText.text (g) Enter the network location or click Change to browse to a location.[][]Click Install to create a server image of [ProductName] at the specified network location or click Cancel to exit the wizard. Control.ulf#OOO_CONTROL_20.LngText.text (h) The Installation Wizard will install the Patch for [ProductName] on your computer.[][] To continue, click Update. Control.ulf#OOO_CONTROL_162.LngText.text (i) [ProductName] Setup is preparing the Installation Wizard which will guide you through the program setup process.[][]Please wait. Control.ulf#OOO_CONTROL_218.LngText.text (j) Error reading from file: [2]. {{ System error [3].}}[][]Verify that the file exists and that you can access it. Error.ulf#OOO_ERROR_25.LngText.text (k) Cannot create the file [3]. [][]A directory with this name already exists.[][] Cancel the installation and try installing to a different location. Error.ulf#OOO_ERROR_26.LngText.text (l) Another application has exclusive access to the file [2].[][] Please shut down all other applications, then click Retry. Error.ulf#OOO_ERROR_31.LngText.text (m) Source file not found: [2].[][] Verify that the file exists and that you can access it. Error.ulf#OOO_ERROR_33.LngText.text (n) Error applying patch to file [2].[][] It has probably been updated by other means, and can no longer be modified by this patch.[][]For more information contact your patch vendor.[][] {{System Error: [3]}} Error.ulf#OOO_ERROR_53.LngText.text (o) User [2] has previously initiated an installation for product [3].[][]. That user will need to run that installation again before using that product.[][] Your current installation will now continue. Error.ulf#OOO_ERROR_66.LngText.text (p) User [2] has previously initiated an installation for product [3].[][]That user will need to run that installation again before using that product. Error.ulf#OOO_ERROR_67.LngText.text (q) Out of disk space -- Volume: '[2]'; required space: [3] KB; available space: [4] KB.[][]Free some disk space and retry. Error.ulf#OOO_ERROR_68.LngText.text (r) Out of disk space -- Volume: [2]; required space: [3] KB; available space: [4] KB.[][]If rollback is disabled, enough space is available. Click Cancel to quit, Retry to check available disk space again, or Ignore to continue without rollback. Error.ulf#OOO_ERROR_72.LngText.text (s) No valid source could be found for product [2].[][]The Windows Installer cannot continue. Error.ulf#OOO_ERROR_81.LngText.text (t) One or more of the files required to restore your computer to its previous state could not be found.[][] Restoration will not be possible. Error.ulf#OOO_ERROR_87.LngText.text (u) Could not schedule file [2] to replace file [3] on reboot.[][] Verify that you have write permissions to file [3]. Error.ulf#OOO_ERROR_110.LngText.text (v) The Mozilla address book driver requires the SUNWzlib package. This package is not part of the minimum Solaris operating system[][] installation. If you require access to the Mozilla address book, then add this package to your Solaris operating system using the command "pkgadd" from the installation CD. readme.xrm#ooo_readme.Netscape.E33.sdcc32asrc.readmeitem.text (w) Value 1, value 2,[][]are 1 to 30 arguments whose largest value is to be determined. scfuncs.src#RID_SC_FUNCTION_DESCRIPTIONS2.SC_OPCODE_MAX_A.3.string.text (x) %PRODUCTNAME could not find a web browser on your system. Please check your Desktop Preferences or install a web browser (for example, Mozilla) in the default[][]location requested during the browser installation. app.src#MSG_ERR_NO_WEBBROWSER_FOUND.errorbox.text (y) StarCalc[][] 4.0 object formats.src#STR_FORMAT_ID_STARCALC_40.string.text (z) %PRODUCTNAME requires a Java runtime environment (JRE) to perform this task. The selected JRE is defective. Please select another version or install a new JRE and select[][] it under Tools - Options - % PRODUCTNAME - Java. javaerror.src#ERRORBOX_JVMCREATIONFAILED.errorbox.text patchjavaerror.src#ERRORBOX_JVMCREATIONFAILED.errorbox.text (aa) Page numbers cannot be applied to the current page.[][]Even numbers can be used on left pages, odd numbers on right pages. chrdlg.src#MSG_ILLEGAL_PAGENUM.infobox.text (Sorry, I ran out of time to chase up these strings. There are more.) 2. Inconsistent formatting: (a) %PRODUCTNAME searches automatically at regular intervals for new versions.\n In doing so online update does not transfer personal data.\n As soon as a new version is available, you will be notified.\n \n You can configure this feature at Tools / Options... / %PRODUCTNAME / Online Update. wizard.src#TP_UPDATE_CHECK.FT_UPDATE_CHECK_BODY.fixedtext.text Preferences paths are formatted differently elsewhere in the OpenOffice.org file: - Tools / Options... / %PRODUCTNAME / Online Update + Tools - Options... - %PRODUCTNAME - Online Update (although I find that inadequate, and format my translations like this: Công cụ > Tùy chọn... > %PRODUCTNAME > Cập nhật trực tuyến because I think the > delimits better and indicates forward progress. I'd prefer a genuine right-arrow character, but you can't be sure everyone is using a font that supports that character.) Also: - In doing so online update does not transfer personal data. + In doing so, the online update doesn't transfer any of your personal data. 3. Problematic formatting: (a) strings which cause errors in multiple categories when checking translations: please format them differently if possible (i) apparent variables merged with text: Replace "standard" quotes with %1custom%2 quotes autocdlg.src#RID_OFAPAGE_AUTOFMT_APPLY.ST_TYPO.string.text utlui.src#RID_SHELLRES_AUTOFMTSTRS.STR_AUTOFMTREDL_TYPO_1.string.text Please find another way to create this string: it causes a lot of errors. (ii) Please don't use angle brackets with placeholders, because they trip the XML error checks: crashrep source\all\crashrep.ulf 0 LngText %MSG_PARAM_PROCESSID% 0 en-US -p <process ID> " instsetoo_native inc_openoffice\windows\msi_languages\Control.ulf 0 LngText OOO_CONTROL_206 0 en-US <error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here><error text goes here> (iii) Square brackets interpreted as variables: extensions source\bibliography\bib.src 0 string RID_BIB_STR_TABWIN_PREFIX 1 en-US Table;Query;Sql;Sql [Native] If this is not a placeholder, please use round brackets. 4. Typos: (a) You are about to delete the resources for the selected language(s). All user interface strings for this language(s) will be deleted.\n \n Do you want to delete the resources of the selected language(s)? 08080000.xhp#par_id3151172.2.help.text This is a pseudo-plurals string which doesn't work. - this language(s) + this language or these languages which is clumsy. I suggest using a genuine plurals expression: (gettext example) msgid "You are about to delete the resources for the selected language. All user interface strings for this language will be deleted.\n \n Do you want to delete the resources of the selected language?" msgid_plural "You are about to delete the resources for the selected languages. All user interface strings for these languages will be deleted.\n \n Do you want to delete the resources of the selected languages?" It is also important to remember, when creating plural strings, that some languages don't have plurals, and yet other languages have up to five plural cases. The gettext plurals feature manages all this. XLIFF does it even better. (b) Do you want to delete the macro XX ? basidesh.src#RID_STR_QUERYDELMACRO.string.text - XX ? + XX? There is no need to delimit final punctuation in English. (c) _: WriterCommands.xcu#..WriterCommands.UserInterface.Commands.. uno_InsertFootnoteDialog.Label.value.text\n Footnote~... _: WriterCommands.xcu#..WriterCommands.UserInterface.Commands.. uno_EditFootnote.Label.value.text\n Footnote~... Should the accelerator be _after_ the word? (d) _: convert.src#DLG_CONV_TEXT_TABLE.FT_REPEAT_HEADER.fixedtext.text\n The first%POSITION_OF_CONTROLrows _: instable.src#DLG_INSERT_TABLE.FT_REPEAT_HEADER.fixedtext.text\n The first%POSITION_OF_CONTROLrows _: tabledlg.src#TP_TABLE_TEXTFLOW.FT_REPEAT_HEADER.fixedtext.text\n The first%POSITION_OF_CONTROLrows Shouldn't there be a space at each end of the placeholder? The placeholder not being delimited by spaces causes multiple errors when checking translations. (f) desktop win32\source\setup\setup.ulf 0 LngText %UNKNOWN_ERROR% 0 en-US An Unknown Error occured! - occurred + occurred This same typo also occurs (sic) in the following strings: connectivity source\resource\conn_shared_res.src 0 string STR_COULD_NOT_RETRIEVE_AB_ENTRY 1 en-US An address book entry could not be retrieved, an unknown error occured. connectivity source\resource\conn_shared_res.src 0 string STR_COULD_NOT_GET_DIRECTORY_NAME 1 en-US An address book directory name could not be retrieved, an unknown error occured. connectivity source\resource\conn_shared_res.src 0 string STR_ERR_EXECUTING_QUERY 1 en-US An error occured while executing the query. desktop win32\source\setup\setup.ulf 0 LngText %UNKNOWN_ERROR% 0 en-US An Unknown Error occured! reportdesign source\ui\report\report.src 0 string RID_STR_COULD_NOT_CREATE_REPORT 1 en-US An error occured while creating the report. sw source\ui\dbui\mailmergechildwindow.src 0 fixedtext DLG_MM_SENDWARNING FI_WARNING 170 en-US The following error occured: (g) wizards source\euro\euro.src 0 string MESSAGES + 4 0 en-US non-existant - existant + existent (h) sc source\ui\src\globstr.src 0 string RID_GLOBSTR STR_ERROR_STR 13691 en-US Err: In the Function Wizard, in the Results field, there is no space after the colon, so the error number is not delmited. (screenshot: calc/58929_2) (i) sw source\ui\table\insrc.src 0 fixedtext DLG_INS_ROW_COL FT_COUNT 30 en-US ~Amount This is used in the context of "How many columns/rows do you want to insert?" So it should be: - ~Amount + ~Number A useful guide here is to ask yourself if something is countable or uncountable. If you can count it, use "number" and "many"; if you can't count it, use "amount" and "much": How many litres of petrol do you want? How much petrol do you want? Insert the number of litres. Insert the amount of petrol. (j) filter source\xsltdialog\xmlfiltertabpagebasic.src 0 fixedtext RID_XML_FILTER_TABPAGE_BASIC FT_XML_INTERFACE_NAME 0 en-US Name of\nfile type 2002-02-02 02:02:02 You don't need a line break here. The other strings in this area of the dialogue are longer than this one, and have plenty of space. In this case, breaking the line looks messy. I hope these are useful.