Apache OpenOffice (AOO) Bugzilla – Issue 23343
Invalid section definition which prevents file loading
Last modified: 2013-08-07 14:38:26 UTC
OOo managed to generate a writer file which contains the declaration of a section style which prevents the file from loading with a generic Read-Error message. The file was obtained initially via an RTF import and had a few modifications, after the last save (in .sxw format) it became impossible to load it again (an error window displaying "Read-Error. Error reading file ." appears). After investigation, it turns out that removing the Sect3 declaration in the automatic styles list of the content.xml file fixes the issue. Quite interestingly, removing everything else in the content.xml but that Sect3 still produces an unloadable file (so it's not the use of that style which creates the problem but its declaration). File is attached for further investigation.
Created attachment 11826 [details] Unloadable file mentioned in the issue.
dvo: The problem apparently has to do with the column widths. With section margins, column margins all added up, there is apprently not enough space for the column. If one changes the column's margins to 1cm (instead of 1.9) in Sect3, the file loads. I haven't quite managed to reproduce this from scratch, but I have managed to crash office while attempting to do so. (Error report sent.) The critical behaviour seems to commence when you have a section with large margins, then columns with lots of column spacing, so that one column gets too thin. dvo->jsi, cyrillem: Looks like a 1.1.? candidate to me.
I'd agree (on the target). If this helps I can try and get more information on which steps led to the file in that state (especially regarding column and margin widths) from the original author.
JSI->MRU: Sections is your area, sorry :-)
JSI: Changed component.
MRU->OS: Sounds like, that the problem should better caught at its root... In the sections dialog, the co-operation between the Indents- and the Columns-TabPage should be improved. Currently it is possible to enter indents with astronomic values and the column widths are not taken in mind when the indents are changed.
os->mru: I disagree here. The user interface can never prevent illegal settings entirely. You can always change your document in a way that leads to strange settings. Import, export formatting and layout have to handle such situations. os->dvo: Please find out where the error occurs.
Considering the effort, the priority, the risk and our resource planning I've to retarget this issue to OOo Later.
Tables.
Reset assignee on issues not touched by assignee in more than 2000 days.