Bug 40908 - FORMATTING of endnotes lost on FILESAVE to Microsoft Word 97/2000/XP format
Summary: FORMATTING of endnotes lost on FILESAVE to Microsoft Word 97/2000/XP format
Status: RESOLVED DUPLICATE of bug 40101
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.3.3 release
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-15 06:05 UTC by Randal Clark
Modified: 2012-02-03 01:41 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Randal Clark 2011-09-15 06:05:03 UTC 
Endnotes that are set to numerals in Writer switch to roman numerals when saved as Micorosoft Word 97/2000/XP format and opened in Microsoft Word 2007.  After being changed back numerals in Word 2007 and saved as Word 97/2000/XP and then reopened in Writer, the endnotes are again changed to roman numerals.  When saved as roman numerals in Writer, they open as roman numerals in Microsoft Word.
Comment 1 Björn Michaelsen 2011-12-23 12:35:00 UTC 
[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
Comment 2 sasha.libreoffice 2012-02-03 01:40:04 UTC 
reproducible in LibO 3.6.0 master
but this bug is duplictate of some another bug
Comment 3 sasha.libreoffice 2012-02-03 01:41:56 UTC 

*** This bug has been marked as a duplicate of bug 40101 ***