unfortunatly I have to save some files in .doc-format. I created the file in LO and enabled the automatic chapternumbering (I am using german version, so I don't know how the exact menu-point in extras is called). I also entered some seperator-after for some layers of the chapters. e.g. 1. First Chapter 1. 1. First subchapter ... 3. 2. 5 and so on... for this to appear correctly I have set ". " as an after-seperator between the single chapternumbers. Now if I save as a .doc and reload in LO, the seperators become all mixed up. The ". " is no set as seperetor-afer AND seperator-before, making my TOC look like this: .1First Chapter .1.1. First subchapter ... .3..2..5. and so on.... I have to manually delete all seperator-before entries in the chapternumber-config-dialog everytime I reopen my document in LO. Then it looks ok, until closed and reloaded. This behaviour also occurred in previous versions of LO and even OpenOffice. I think it is a bug and it would save me a lot of time, it could be fixed. Thanks in advance.
minimize the effort needed to debug this and attach a small sample .odt which when saved to .doc causes this to happen
[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: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian