To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=100366
                 Issue #|100366
                 Summary|Problem with .doc export on second level lexical index
                        | entries
               Component|Word processor
                 Version|OOo 3.0
                Platform|Unknown
                     URL|
              OS/Version|Windows XP
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|save-export
             Assigned to|writerneedsconfirm
             Reported by|ihurbain





------- Additional comments from [email protected] Thu Mar 19 14:45:34 
+0000 2009 -------
The second level lexical index entries are not saved correctly when exporting a
.doc document.

To reproduce:
1/ create a new document in Writer
2/ create an index entry with two keys
3/ save the document as .doc file
4/ close and reopen document.
Expected result: the index entry and both its keys are saved.
Observed result: the index entry has lost its second key.

It's not a display issue : when opened in MS Word, the second key is also
non-existing.

We have confirmed that bug on ArchLinux x86_64 (OpenOffice.org 3.0.1, 300m15,
build 9379), Mandriva x86 and x86_64 (3.0.0 build 9358) and Windows XP (3.0.0
build 9358).

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to