Issue 80836 - Word document is truncated, tail end missing
Summary: Word document is truncated, tail end missing
Status: CLOSED DUPLICATE of issue 78808
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: OOo 2.2
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2007-08-20 04:43 UTC by lsatenstein
Modified: 2007-08-28 11:58 UTC (History)
2 users (show)

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


Attachments
File with pages being a table with header, and middle to tail end of file missing (73.00 KB, application/msword)
2007-08-20 04:46 UTC, lsatenstein
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description lsatenstein 2007-08-20 04:43:16 UTC
I have a word document that is 5 pages in Microsoft Office, but the last two
pages are lost when the file was read with OO. I switched from OO to MS so that
editing would be easier to do. There appears to be problems with OO handling
tables whose first line serves as a header. I don't see where I can attach the
file with the formatting that causes the import problem
Comment 1 lsatenstein 2007-08-20 04:46:21 UTC
Created attachment 47634 [details]
File with pages being a table with header, and middle to tail end of file missing
Comment 2 lsatenstein 2007-08-20 04:47:20 UTC
Pages 4 and 5 are missing, page 6 is there.
Comment 3 mike_hall 2007-08-20 11:31:54 UTC
Agree document is OK in Word and not OK in Writer. Tried in 2.2.1 and OOG680 m1.
The single row of text can all be seen if font size is reduced, it's just
refusing to split the table. However, the document crashes Word when I use the
right hand scroll bar to scroll down the document. Page down key is OK though.

There appears to be a fault of some kind in the document format. If I copy your
Table 2 (starting at the top of the second page) into another document, the
problem seems to be resolved (the table breaks as expected), but I haven't been
able to spot what's wrong with the original. 

Please see if you can demonstrate the problem with a simpler example, starting
from a new document.

To resolve the problem for your own document, you could reconstruct a new
version with copy and paste to a new document and see if that fixes it. 

A  problem with the design of the document as you currently have it is that the
different items down the table have to be lined up manually. You might find
editing and alignment substantially easier if you used separate table rows for
each item. This might also allow Writer to break the table more easily.
Comment 4 lsatenstein 2007-08-21 17:23:32 UTC
Hi Mike
I was able to duplicate your efforts.
I also tried the option of having a separate table row for each entry. While it 
solves one problem, I have not figured out how to automatically eliminate the 
horizontal lines between the rows, while keeping the left and right most lines. 
This should be done without resorting to manually re-formating each rows cells.

The document history is as follows:  Begin with OO, when OO began to mis-
behave, port to MS-word, complete the text in ms-word and import to OO. 
That is where I encountered the problem and posted it here. So, is it OO or 
msword that introduced the corruption?

As far as I am concerned, I will help with some further tests, if need be, but 
my full document was delivered (as a pdf) to the end users. I suggest the 
option to close  to be WONTFIX, as it is a rare rare situation. Who does the 
close?

Leslie
Comment 5 michael.ruess 2007-08-28 11:46:27 UTC
The problem in this document is the use of the "Keep with next" paragraph format
property.
In MS Word this is used in table to have a table row sticking to its succeeding
row (to prevent both being split from each other when a page break is created
somehow).
In the "Table 2" select the first paragraph and disable the "Keep with next"
option in Format.Paragraph.
This problem is already handled in issue 78808 (same root cause, though it is
about RTF import. Is not a filter problem, it is in Writer core).
Comment 6 michael.ruess 2007-08-28 11:47:35 UTC
Marking as dup of 78808.

*** This issue has been marked as a duplicate of 78808 ***
Comment 7 michael.ruess 2007-08-28 11:58:38 UTC
Closing duplicate issue.