using LO 3.4.3 on Windows 7 x64
Clean (initial) install of LibreOffice.
In Language settings of Tools/Options/Language Settings/Languages.
The install correctly detects my user interface as English (USA). However, it incorrectly fills in Locale as English (Zimbabwe) and Language for Documents (Western) also as English (Zimbabwe).
I think that the language/locale default setup is using either the last index for a given language or a +1 index. In the case of English, there are about 15 locales, Australia to Zimbabwe. USA is listed as 14, Zimbabwe as 15.
If an index search for UI system setting English (USA) matches a locale in LibreOffice, it may be counting 1 as the first entry rather than 0. This could cause a 1 off index return.
After setting the locale to English (USA) and document language to the same, the options are correctly maintained.
But setting the locale does not change the measurements for margins and tabs like it does for currency. Changing to English (USA) should switch to measurements customary for the locale. In this case: Inches.
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Problem persists using LibreOffice 3.4.4 and 3.5.0 beta 2
Additionally using 3.5.0 beta 2, the default currency defaults to ZWD (Zimbabwe dollars) and not USD. System Locale is US english.
*** This bug has been marked as a duplicate of bug 55083 ***
I think this is the same issue as bug 55083.
I know you reported this earlier than that one but expert developers are already on CC list over there. I pasted your useful informations in that bug report and added you to CC list.
I'm not sure it's a duplicate anymore...
so I reopen and change status to NEEDINFO.
what I need to know is if your bug still present with recent 4.0.5 or 4.1.1 releases.
thanks and sorry for the noise.
P.S. change version field to 3.4.3 since it's first version where the bug is reported. you should always indicate earlier version not last versione where the bug in present.
Dear Bug Submitter,
Please read the entire message before proceeding.
This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.
For more information about our NEEDINFO policy please read the wiki located here:
If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):
a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue.
Please do not:
a) respond via email
b) update the version field in the bug or any of the other details on the top section of FDO