To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=48123
------- Additional comments from [EMAIL PROTECTED] Thu May 19 10:03:16 -0700 2005 ------- My feature request is that auto-enabling of CTL support is somehow enhanced so that on Windows it is automatically enabled in a situation where - the Thai language group is supported and installed, - the user locale is US, - the system locale is Thai, and - there is no Thai interface pack installed. The reason for this request is that this is a very common situation in Thailand. I am not sufficiently familiar with the internals of OOo to be sure what the right way to do this is. I don't think you analysis of the current behaviour is correct. If the user locale is Thai and there is no Thai language pack, then CTL support is enabled (and the option to disable it is greyed out). On Windows, the System Locale is a completely different thing from the User Locale; it's not like on Linux, where it's a default locale which can be overridden for each user. There's a separate Default User Locale which provides the default for a new user's User Locale. There's a good summary here: http://www.microsoft.com/globaldev/DrIntl/faqs/Locales.mspx Making the system locale be Thai allows that non-Unicode Thai applications to work on that system. The IsValidLanguageGroup function is documented here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/nls_001c.asp Note that having a particular language group installed is a prerequisite for having a language in that group as a system or user locale. I can see two possible approaches: a) If any CTL language group is installed, enable CTL support b) If the system locale is a CTL language (which is only possible if a CTL language group is installed), enable CTL support These are both platform dependent, but I think determining whether to auto-enable CTL support is something that is inherently platform dependent. However, I don't see anything fragile: they are both accessible using officially documented APIs. The consequences of failing to enable CTL support when it is needed are much worse than those of enabling CTL support when it is not needed, so I would say that in a situation where it is uncertain whether CTL support is needed it is better by default to enable it (and allow the user to disable it if they do not in fact need it). That would lead to (a) rather than (b): if IsValidLanguageGroup() says that no CTL language group is installed, then it is 100% certain that the user cannot use a CTL language. (b) would be a more conservative change. I find it very hard to think of a situation where a user would not want CTL support enabled on a machine with a system locale that was a CTL language. --------------------------------------------------------------------- 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]
