In v3.3.2 release, .doc saves the table correctly.
In v3.4 beta2, .doc drops the table and saves unformatted text.
In v3.4 beta2, .docx didn't get column widths right.
In v3.3.2 release, .docx didn't get column widths right.
The table feature is important for careerbuilder.com where tabs are drop.
Confirmed. I created a 3 column 2 row document and saved it in .odt, .doc, and .docx.
The .odt file displays everything correctly. Both .doc and .docx screw up the table pretty badly. I'll upload all three files.
Created attachment 46133 [details]
Correct table save
Created attachment 46134 [details]
Incorrect .doc save
Created attachment 46135 [details]
Incorrect .docx save
v3.3.2 routine saved tables using .doc files
v3.3.2 routine refused to do correct column width
v.34 beta 2 routines crashed tables using .doc and .docx files
Seems like a minor problem unless the app is worring about legal boundries?
These tables are popular on monster.com and careerbuilder.com (don't use tabs).
For the .doc problem this one is a DUP of of
"Bug 36903 - export of tables (.doc) produces corrupted document"
what itself is a DUP of
"Bug 35805 - Tables corrupted in exported doc-files"
So here we should concentrate on the .docx problem, what seems different to me.
That is [Reproducible] with "LibreOffice 3.4Beta3 – WIN7 Home Premium (64bit) German UI [DEV300m103 (Build:3)]", with Tack's sample and also my own newly created sample documents.
It's really strange that that's only a problem with 3 column tables, 4 column tables will be saved correctly. Number of rows seems to be irrelevant?
Seems to be a combined FILEOPEN / FILESAFE problem.
FILESAFE: MS WORD Viewer will show correctly 3 columns, but with different column width. That's a minor problem.
FILEOPEN: Exsisting third column will not be shown. That's serious and should be subject of this bug. We will see whether the export problem still will exist when the import problem will have been fixed, please feel free to file a separate bug for that problem.
It's serious, but is it a 3.4 blocker? I don't think so.
@Brian OSullivan, Zack:
I'm pretty sure that it's an all OS problem, but can you please contribute information concerning your OS?
Please feel free to reassign if it's not your area!
I can try have a look at this
Table column problem exists in v3.4 b1-4 for .doc & .docx.
I use .rtf in the mean time.
My PC has Win7 Home Premium, 64bit.
Improper saves are different between betas and formats.
In v3.3, the .doc worked right.
It could be converted to .docx by third party software.
LibO 3.4-beta5 improved over 3.4-beta4 saving .doc & .docx tables.
Column width is still not right though.
Routine to convert Table <==> Text would be nice.
Please do not comment to problems from other reports here.
There is no improvement concerning the 3 columns problem with 3.4Beta5
fixed on master with
removing the regression keyword, the regression in this case is to do with the binary(doc) export problem. Lets keep this bug for the docx specific issue
the files are displaying as per comment 1
Build ID: 066665644b398a882e6cded98af5bb060af41d76
TinderBox: Android-ARM@24-Bytemark-Hosting, Branch: Master, Time: 2017-06-01 00:30:43