It may be a bit hard to describe but in essence since LO 3.3 I've severe compatibility problem. When I create an (alphabetical) index for the book and then save the document as doc or docx (which is needed because, sadly, Indesign just does not acknowledge OD formats...), it opens in MS Word not correctly: the words or parts of them what were marked for indexing are gone and can be seen only if "hidden text" is enabled (and then, of course, you can see not only the "eaten" text but also index terms).
(I can provide the document if really needed but for developers eyes only - it's not published yet and the terms do not allow me to distribute it freely...)
[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
Well, it seems to be somehow different but maybe eve worse in 3.5. My editor (for different text, though) says when he opened my .doc, he saw quite a messy layout - his words were "index marks were ecploding", meaning mostly the index marks messed up tables. Also the layout of the text was messy, he said, but it may be different problem.
(and as before, if the developer needs the text in question I may send it to him/her personally as it is not published yet and so "confidential")
Please do this to remove confidential data:
After attaching that file here please mark this bug UNCONFIRMED to let someone check that problem.
Well, that is not applicable - as I said it concerns ALL the document, well like a news item with mark DO NOT PUBLISH BEFORE, but in my case it extends also some years after the publication. So I can't provide (attach here) document publicly but can send it to a specific person if required.
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!
I'm really disappointed in - I've clearly stated that I'm ready to provide the text to the person who intends to fix possible bug but not openly, and now it seems as there is no such person, the BR is just closed?
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