Created attachment 49434 [details]
Native OOo format with simple 3 column doc.
Create OOo document with a multi-column format.
Set the separator line to "NONE".
Save in default odf format.
SaveAs Word 2007 XML format.
Separator Line should be NONE.
Separator Line of 0.05pts is set.
Going back to the odf version, the value NONE is properly recorded, but
is never properly saved/restored in .docx format.
Example files are attached.
Created attachment 49435 [details]
Same original as .odt, but stored via SaveAS in Word 2007 XML docx
Created attachment 49483 [details]
Confirmed on LibreOffice 3.4 340m1(Build:103) for OpenSuse Linux.
Here is the first attachment for what I see in LO writer.
Created attachment 49484 [details]
.doc in LO writer
I think this is the erroneous behavior described by the reporter.
[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:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
reproduced in LibO 3.6.0 master on Fedora 64 bit
when save in docx, separator style is lost,
When open in docx, column width also lost
Still there in 4.2.
1. Open Test File "Native OOo format with simple 3 column doc." with LO
2. save as docx file
3. reopen docx file with LO
Currently: separator style stays none
Expected: see currently
BUT the contents all jump to the first column!
In LO Version: 18.104.22.168.alpha1+
Build ID: 3a96d8ead86dc210085f09076fd270f247442f0a
TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2015-04-26_02:00:38
So closing this bug as WORKSFORME. For remaining issues with this document please do file new bugs (one issue per bug!) and then those can be tackled separately.
Fixed within 4.2.
Build ID: 48d50dbfc06349262c9d50868e5c1f630a573ebd