Issue 37741 - table in .doc extends beyond the end of the page
Summary: table in .doc extends beyond the end of the page
Status: CLOSED DUPLICATE of issue 13791
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: OOo 1.0.3
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-24 00:44 UTC by mfedyk
Modified: 2004-11-24 09:32 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description mfedyk 2004-11-24 00:44:10 UTC 
I can reproduce this in OOo 1.1.3 and 1.9.m62.

The improper column wrapping is issue 37737.

The table placed on page two is issue 37738.

Look at the attachments on issue 37738 for PDFs and the origional .doc file.

Issue 37739 and issue 37740 are the table erases data and undo fails for OOo
1.1.3 and OOo 1.9.m62 respectively.

This issue is for the table that extends beyond the end of the page.

Steps to reproduce:
1. Open the .doc file in issue 37738 (the rows are double height because of the
second column wrapping)
2. Notice the table extends beyond the end of the page, and is unviewable.

Work-around:
resize right column to keep the columns from being double height.

I'm not sure what the correct action should be.  Should the table be split so it
shows on the second page or something else?
Comment 1 michael.ruess 2004-11-24 09:30:37 UTC 
The tabe in this case is stuck in a frame ("floating" tables, means: tables
having a wrapping style, are imported in frames to emulate the wrapping; Writers
table are currently not capable of being wrapped by text) and it is not possible
to break the frame.
There already exist an enhancement request to implement wrapping styles for
tables in OO Writer, so this will be imported much better. See issue 13791.

*** This issue has been marked as a duplicate of 13791 ***
Comment 2 michael.ruess 2004-11-24 09:32:13 UTC 
Closing duplicate.