I am a developer adding support for generating OpenDocument Text files from within Emacs/Orgmode [1]. My exporter generates the odt files by dumping xml directly to the various xml files (i.e, it doesn't rely on any API as such) I am seeing regressions in behaviour between OpenOffice-3.2.1 and LibreOffice-3.4.2 wrt cross reference. I am attaching the following files: 1. reference.org - This file is for my own reference. Please ignore this file. 2. reference.odt - This is the file created by the exporter. 3. odt-file-as-viewed-with-OOo-3.2.1.bmp - Screenshot of reference.odt in OOo-3.2.1. Pay attention to the region circled in red. 4. odt-file-as-viewed-with-LO-3.4.2.bmp - Screenshot of the SAME reference.odt as seen with LibreOffice 3.4.2. Pay attention to the region circled in red. Note that there is a regression in behaviour wrt treating of cross references which corresponds to the following region in content.xml ,---- | <text:bookmark-ref text:reference-format="text" | text:ref-name="OrgXref.sec-1-1-1"> | Fuzzy Target | </text:bookmark-ref>. `---- Footnotes: [1] Orgmode defines a structured markup for text files (very similar to markdown or rst)
Created attachment 50437 [details] reference.org (Please ignore this file)
Created attachment 50438 [details] reference.odt (odt file generated by my own exporter)
Created attachment 50439 [details] screenshot of reference.odt in OOo-3.2.1. This is OK.
Created attachment 50440 [details] screenshot of reference.odt in LO-3.4.2. This is NOT OK.
Toggling my View->Field Names gets me the desired behaviour. I have lowered the priority of the bug. I am taken by surprise by the difference in the default settings between 3.2.1 and 3.4.2. A user will always like to see the behaviour seen in 3.2.1 and it should be the default one. Furthermore, if the user has indeed changed the default settings then LibreOffice should try to migrate these settings from OpenOffice environment.
[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