To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=49581
------- Additional comments from [EMAIL PROTECTED] Mon Jul 11 07:45:57 -0700 2005 ------- Javier, Sorry, but org.openoffice.Setup/L10N/ooLocale isn't the right setting either. That setting is the old UI locale setting from OOo 1.x and is still being used by client code to find out the current UI locale. But in OOo 2 this isn't really a preference any more: The startup code (in desktop/source/app/langselect.cxx) reads the UI locale preference from org.openoffice.Office.Linguistic/General/DefaultUILocale and validates it against the installed UI languages. If if the preference isn't valid some fallback sequnce is used to find a valid/installed languge. When finally a valid language is found, that language is written to the Setup/L10N/ooLocale key, so that it will be used as the chosen UI languge at runtime. Effectively this is a transient value. That same startup code also writes the UI locale to the DefaultLocale[_CJK|_CTL] preference, if reading the chosen key yields an empty value. The choice of key depends on the classification of the UI language as asian/complex/neither. Static settings should only ever be used for scenarios that don't work with these automatisms - and if the reason why it fails is understood. HTH, Joerg --------------------------------------------------------------------- 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]
