Issue 23343 - Invalid section definition which prevents file loading
Summary: Invalid section definition which prevents file loading
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2003-12-09 13:05 UTC by cyrille.moureaux
Modified: 2013-08-07 14:38 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Unloadable file mentioned in the issue. (97.13 KB, application/vnd.sun.xml.writer)
2003-12-09 13:07 UTC, cyrille.moureaux
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description cyrille.moureaux 2003-12-09 13:05:29 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
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.
Comment 1 cyrille.moureaux 2003-12-09 13:08:03 UTC
Created attachment 11826 [details]
Unloadable file mentioned in the issue.
Comment 2 openoffice 2003-12-09 18:07:37 UTC
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

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.
Comment 3 cyrille.moureaux 2003-12-09 18:17:50 UTC
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.
Comment 4 jogi 2003-12-10 14:03:54 UTC
JSI->MRU: Sections is your area, sorry :-)
Comment 5 jogi 2003-12-10 14:09:12 UTC
JSI: Changed component.
Comment 6 michael.ruess 2003-12-10 15:17:44 UTC
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.
Comment 7 Oliver Specht 2003-12-10 15:41:04 UTC
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.
Comment 8 andreas.martens 2005-06-28 13:57:57 UTC
Considering the effort, the priority, the risk and our resource planning I've to
retarget this issue to OOo Later.
Comment 9 andreas.martens 2005-06-28 14:01:39 UTC
Comment 10 Rob Weir 2013-07-30 02:15:25 UTC
Reset assignee on issues not touched by assignee in more than 2000 days.