[l10n-issues] [Issue 54721] Installers for languages not supported by Windows should force startup locale to be in their own language

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=54721 --- Additional comments from [EMAIL PROTECTED] Sun Sep 18 01:20:35 -0700 2005 --- javiersola: So what the user has to do to get all in Khmer? Can you please

[l10n-issues] [Issue 54721] Installers for languages not supported by Windows should force startup locale to be in their own language

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=54721 --- Additional comments from [EMAIL PROTECTED] Sun Sep 18 03:07:54 -0700 2005 --- The amount of work to be done by the user/installer is ridiculously small:

[l10n-issues] [Issue 54721] Installers for languages not supported by Windows should force startup locale to be in their own language

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=54721 User pjanik changed the following: What|Old value |New value

[l10n-issues] [Issue 54721] Installers for languages not supported by Windows should force startup locale to be in their own language

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=54721 --- Additional comments from [EMAIL PROTECTED] Sat Sep 17 11:39:28 -0700 2005 --- javiersola: do I understand that if you have dual language instset, like en_US-km,

[l10n-issues] [Issue 54721] Installers for languages not supported by Windows should force startup locale to be in their own language

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=54721 --- Additional comments from [EMAIL PROTECTED] Sat Sep 17 19:17:44 -0700 2005 --- No, the run is in Khmer, but with en_US locale values (such as number format).