Issue 513 - WW9: obsolete additional lines in table imported
Summary: WW9: obsolete additional lines in table imported
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: 619
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-03-06 09:56 UTC by michael.ruess
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

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


Attachments
Issue513.doc (51.50 KB, application/msword)
2001-08-03 08:16 UTC, michael.ruess
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description michael.ruess 2001-03-06 09:56:48 UTC
Bugdoc: the second table originally consists of only one line/two cells; the 
import adds empty lines

CMC: This is odd, if the second table is moved down it all works ok. Its seems 
to be the vertical anchoring to a character thats at fault. If its anchored to 
the paragraph mark after the previous table then there is a problem
Comment 1 michael.ruess 2001-03-06 09:58:04 UTC
Created attachment 94 [details]
Issue513.doc
Comment 2 caolanm 2001-03-12 12:12:25 UTC
Word has no real "tables" only rows that happen to be under eachother and look
like a table to the user. So when the filters sees one set of table rows
following another set but the second set has attributes that will cause them to
be set into a seperate floating table then we need to not count those rows as
part of the first table's row count.

The existance of attributes causing a new frame to be inserted should be a
sufficient test, in the case that Im mistaken, then a test for the existance of
absolute positioning attributes on the toublesome table rows can be substituted
instead.

"Moving the table down" some space, placed some elements between the two tables
so as to make the original table end algorithm work correctly.

Fix checked in.
Comment 3 caolanm 2001-03-16 16:39:00 UTC
Works for me in 625b1
Comment 4 michael.ruess 2001-03-19 16:12:41 UTC
OK in 625b
Comment 5 michael.ruess 2001-04-25 10:19:11 UTC
Closed, because fixed already.