Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||References in headers aren't automatically updated when importing a SXW document|
|Component:||code||Assignee:||AOO issues mailing list <issues>|
|Status:||CONFIRMED ---||QA Contact:|
|Issue Type:||DEFECT||Latest Confirmation in:||---|
Description gnustavo 2006-04-20 13:12:20 UTC
Create a text document with OOo 1.1. (I use 1.1.2, Brazilian Portuguese edition.) Define a reference over a word and insert it in two places: somewhere in the page and in a header. Save it. When I open it with OOo 1.1.2, both references are automatically updated. However, when I open it with OOo 2.0.2, the reference in the header isn't updated. I have to press F9 to force it to be updated. Even if I convert the document to the OpenDocument format the problem persists. Whenever I open it I have to press F9 to have the reference in the header updated. However, if I create the file originally with OOo 2.0.2 (instead of converting it from the SXW) the problem doesn't happen. I'm going to attach two files. The first one (re.sxw) I created with OOo 1.1.2. The second one (re.odt) I created with OOo 2.0.2. Open re.sxw with OOo 2.0.2 to see that the reference in the header isn't automatically updated. You have to press F9 to make it so. Gustavo.
Comment 1 gnustavo 2006-04-20 13:13:16 UTC
Created attachment 35845 [details] File created with OOo 1.1.2
Comment 2 gnustavo 2006-04-20 13:13:57 UTC
Created attachment 35846 [details] File created with OOo 2.0.2
Comment 3 michael.ruess 2006-04-20 14:07:15 UTC
Reassigned to ES.
Comment 4 eric.savary 2006-04-20 16:35:24 UTC
ES->OS: I think we have a duplicate for this, don't we?
Comment 5 gnustavo 2007-07-05 20:54:50 UTC
The problem seems to be solved in version 2.2.1.
Comment 6 cno 2007-10-01 15:15:30 UTC
@ gnustavo: still ok for you in 2.3? When I open your re.sxw, the ref in the header isn't automatically updated...
Comment 7 gnustavo 2007-10-01 17:51:54 UTC
I haven't installed 2.3 yet. But I just openned re.sxw with my 2.2.1 version and the problem persisted. I don't remember what led me to make the observation, last July, that the problem seemed to be solved. It's still there with version 2.2.1. I'm sorry.