Apache OpenOffice (AOO) Bugzilla – Issue 89736
Errors in the original strings (basctl)
Last modified: 2013-02-24 21:00:48 UTC
While translating the interface, I found these errors. I thought you would want to fix them, as they detract from the overall quality of the program. I am not sure against which module to report each string: I notice clicking on "officecfg" brings me to "utilities", so I may be reporting in separate places strings belonging together. However, I have tried reporting them altogether, and that isn't OK either. So this is my effort. I hope it is useful. 1. Incorrect plurals usage, grammatic error basctl source\dlged\managelang.src 0 querybox RID_QRYBOX_LANGUAGE 0 en-US You are about to delete the resources for the selected language(s). All user interface strings for this language(s) will be deleted.\n\nDo you want to delete the resources of the selected language(s)? Delete Language Resources 2002-02-02 02:02:02 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. 2. Typo basctl source\basicide\basidesh.src 0 string RID_STR_QUERYDELMACRO 1 en-US Do you want to delete the macro XX ? 2002-02-02 02:02:02 - XX ? + XX? Question marks are not spaced in English. Clytie Vietnamese Free-Software Translation Team
Andreas, please have a look ...
ab->clytie: Thanks for the hints STARTED, unfortunately it's too late for 3.0 as UI freeze is already gone, -> 3.1
Also missed 3.1 feature freeze -> 3.2
ab->clytie: I've talked to Rafaella concerning 1. and she told me that duplicating strings due to this problem is undesired in general. She proposed to ask User Experience to think about another text in this case that could avoid the problem. I will try to address this. 2. is ok, I will add it to i89740 / cws ab72 as it does not need to wait for a solution for 1.
ab->andba: Rafaella suggested that maybe someone of the OOo ux community team could have a look at this and find another phrase for problem 1. avoiding the problem. But I don't know how to address this. Are you the right one to deal with this? Anyway, I doubt this issue has a very high priority.
This issues requires a string review. I will try to direct it to the appropriate resource.