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 19:15:14 -0700 2005 ------- The scenario we are talking about is one in which we are tryng to obtain an OOo package that will install in English and then behave like a native target-language package which does not have to be reconfigured to be used in that language. We have the following situation - Target language is not supported by Windows. - Bilingual packages are created, English+target - The user's Windows computer interface and locale are en-US, as the target language is not supported. - en-US language is available in the OOo installation. With all these variables, the system will most normally choose en-US as the OOo locale. If, for these bi-lingual packages that are automatically generated, for languages that are not supported by Windows, the OOolocale was the one of the target language, then no post-installation reconfiguration would be necessary. This would be desired behaviour for us. Note: We also change the file picker to native OOo picker, as the Windows picker cannot handle the desired script, but I do not want to include this here, not to make this a mutating issue. --------------------------------------------------------------------- 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]
