To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=115386





------- Additional comments from [email protected] Tue Nov 16 14:08:56 +0000 
2010 -------
Have found the true reason for problems (1) and (2) now.  In both cases
(gdocs_2.3.0.oxt and Linguist-1.4.oxt) the contained Addons.xcu files contain
localized properties that contain property values for some specific xml:lang
attribute values as well as for the empty, default xml:lang attribute value
(which can be denoted by completely leaving out the xml:lang="..." attribute), 
like

<prop oor:name="Title" oor:type="xs:string">
  <value/>
  <value xml:lang="en-US">Statistics</value>
  <value xml:lang="da">Statistik</value>
  <value xml:lang="fr">Statistiques</value>
</prop>

If the OOo UI locale ("Tools - Options... - Language Settings - Languages -
Language of - User interface") matches one of the given xml:lang attribute
values (one of en-US, en, da, fr in the above example), the corresponding
property value will be used.  However, if the locale does not match, the empty
default xml:lang attribute value will be used instead (leading to an empty
property value, which then causes the problem of not displaying menu entries),
even taking priority over an "en-US" fallback.  (This has probably changed
slightly from OOo 3.2, which may have preferred the "en-US" fallback over the
empty locale fallback.)

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to