https://bugs.documentfoundation.org/show_bug.cgi?id=94804
Michael Stahl <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |[email protected], | |[email protected] Resolution|--- |FIXED Assignee|[email protected] |[email protected] |desktop.org | Whiteboard|bibisected |bibisected dataLoss --- Comment #11 from Michael Stahl <[email protected]> --- thanks Oliver for fixing the root cause. regression from commit 679faffc68bb854af0f55d0f218698e2f372f00b looks to me there are 2 problems here, firstly the merge problem above causing heading-reference to be created instead of numbering-references, second is that in 4.4.x the heading-references stopped working in this case. commit 9d0c51daea67104349cac26de9839afa8baeb099 Author: Michael Stahl <[email protected]> AuthorDate: Fri May 15 23:57:04 2015 +0200 tdf#90808: sw: fix detection of duplicate CrossRefBookmarks The check for existing bookmark positions is using the wrong position. It must use the Start of the pam, because the constructor of CrossRefBookmark only uses the Start of the pam. so the versions since 4.2.0 or so would create these documents where there can be more than one "__RefHeading__" bookmarks on a single paragraph: every time you try to insert a new CROSSREF_NUMITEM_BOOKMARK it will find that there is no CROSSREF_NUMITEM_BOOKMARK on the paragraph and then wrongly insert another CROSSREF_HEADING_BOOKMARK on it. then with the fix for bug 90808, we will import only the first of these CROSSREF_HEADING_BOOKMARK in ODF import, and throw the rest of them away because they are duplicates. if you're lucky then the bookmark that survives is the one that is referenced by all the fields; if not, then you get lots of "Error: Reference source not found" once you update fields. i'm afraid we'll have to add some horrible hack to load all these corrupted documents. i've added something sufficiently ugly on master now. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
