Apache OpenOffice (AOO) Bugzilla – Issue 67312
extension manager: localize error messages
Last modified: 2013-02-07 21:50:55 UTC
There are some error messages which should be localized: For example: a) $FILE contains data which cannot be parsed. b) $FILE does not contain the root element <description>. c) $FILE contains a root element with an unsupported namespace. d) Cannot find a localized license text or default license text. e) [When a licence-text file is missing] Adding Package(s): $FILE does not exist. The last error should not containg Adding Packages. All messages should also refer to the name of the extension and maybe not show the path into the package cache direcory. See code ExtensionDescription::ExtensionDescription() (desktop/source/deployment/registry/package/dp_description.cxx and checkLicense (desktop/source/deployment/registry/package/dp_package.cxx
.
While I doubt the necessity of having localized message boxes in theses cases there is one that may be importent. The message box comes up when the namespace of the description.xml was not recognized. This could mean that the extension uses newer features which is not recognized by an old office. This should be clearly stated in the the message box.
I have just received "Cannot find a localized license text or default license text." To reproduce: - install to-be-m3 in cs language - try to install Sun Report Builder. That's all. Please re-consider target.
set target to 3.x according to http://wiki.services.openoffice.org/wiki/Target_3x
This type of error is actually not relevant to users - they did not cause it nor can they fix it. It occurs because the extension contains a bug. I am against localizing every possible error message. However, a useful error message, in case the name space of the description.xml is not recognized, could be useful.