Issue 25680 - Word import/export for 'Tables in tables'
Summary: Word import/export for 'Tables in tables'
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: All All
: P3 Trivial with 32 votes (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords: ms_interoperability, oooqa
: 29075 31957 43048 47032 48561 51112 54736 55268 57003 57162 57268 57485 62787 64092 64215 65402 66274 68632 69134 74900 75018 76200 78806 84131 85440 93059 94168 95851 96060 98409 (view as issue list)
Depends on:
Blocks: 59023
  Show dependency tree
 
Reported: 2004-02-19 12:33 UTC by frank.meies
Modified: 2013-08-07 14:44 UTC (History)
13 users (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 frank.meies 2004-02-19 12:33:23 UTC 
*** autogenerated child task for Issue 25676 ***
Comment 1 caolanm 2004-03-01 13:33:12 UTC 
cmc->mmaher: This is the big feature that we discussed last week. It has the
complexity of the level properties for cell. Note that 0x7 should be export as
0xD for embedded table cell and row ends. The normal 0x2416/0x2417 cell/row
properties on these one char end mark paragraphs have different versions for
higher row and cell levels, and it *might* be the case that the pMagicTables are
required to be correct for true export. Though that might not be the case.
Clearly import is easier than export as we have the current ability to import
these tables inside tables through introducing a containing frame which doesn't
appear in the original. We should remove this frame, but only for non-floating
tables, it should remain for tables which have explicit floating properties.

I guess coordinate with fme/hbrinkmann if necessary
Comment 2 martin_maher 2004-03-11 11:43:35 UTC 
mmaher: started
Comment 3 michael.ruess 2004-05-12 11:38:33 UTC 
*** Issue 29075 has been marked as a duplicate of this issue. ***
Comment 4 michael.ruess 2004-07-23 07:55:45 UTC 
*** Issue 31957 has been marked as a duplicate of this issue. ***
Comment 5 andreas.martens 2004-07-30 10:52:59 UTC 
The feature "table in tables" is already implemented. Now it's a defect that the
import and export doesn't use our new featrue ;-)
Comment 6 martin_maher 2005-01-27 16:27:30 UTC 
mmaher->flr: Maybe you can have more luck with this
Comment 7 andreas.martens 2005-02-18 10:22:11 UTC 
If it's not fixed in time for OOo2.0, it should be fixed for OOo2.0.1.
Comment 8 michael.ruess 2005-02-18 12:30:52 UTC 
*** Issue 43048 has been marked as a duplicate of this issue. ***
Comment 9 michael.ruess 2005-04-18 12:59:54 UTC 
*** Issue 47032 has been marked as a duplicate of this issue. ***
Comment 10 michael.ruess 2005-05-03 08:58:26 UTC 
*** Issue 48561 has been marked as a duplicate of this issue. ***
Comment 11 michael.ruess 2005-06-22 15:50:56 UTC 
*** Issue 51112 has been marked as a duplicate of this issue. ***
Comment 12 andreas.martens 2005-08-18 12:49:46 UTC 
Considering the effort, the priority, the risk and our resource planning I've to
retarget this issue to OOo Later.
Comment 13 michael.ruess 2005-10-06 10:55:08 UTC 
*** Issue 55268 has been marked as a duplicate of this issue. ***
Comment 14 michael.ruess 2005-10-13 15:33:42 UTC 
*** Issue 54736 has been marked as a duplicate of this issue. ***
Comment 15 michael.ruess 2005-10-31 07:49:44 UTC 
*** Issue 57003 has been marked as a duplicate of this issue. ***
Comment 16 michael.ruess 2005-11-02 06:31:43 UTC 
*** Issue 57162 has been marked as a duplicate of this issue. ***
Comment 17 michael.ruess 2005-11-03 06:12:20 UTC 
*** Issue 57268 has been marked as a duplicate of this issue. ***
Comment 18 michael.ruess 2005-11-08 07:32:21 UTC 
*** Issue 57485 has been marked as a duplicate of this issue. ***
Comment 19 michael.ruess 2006-01-11 10:16:17 UTC 
*** Issue 60346 has been marked as a duplicate of this issue. ***
Comment 20 lars 2006-03-05 17:49:16 UTC 
*** Issue 62787 has been marked as a duplicate of this issue. ***
Comment 21 ajung01 2006-03-06 10:30:14 UTC 
Is there a chance that this issue will be fixed in the near future. Obviously
this bug is pending since two years.....
Comment 22 michael.ruess 2006-04-07 05:42:38 UTC 
*** Issue 64092 has been marked as a duplicate of this issue. ***
Comment 23 michael.ruess 2006-04-18 14:16:51 UTC 
*** Issue 64215 has been marked as a duplicate of this issue. ***
Comment 24 danhorwood 2006-04-28 03:55:10 UTC 
I'd also like to see this fixed at some stage - as ajung01 said, it's been
pending for 2 years, and there is obvious interest in the bug considering the
amount of dupes (i was very close to filing another dupe...)
Comment 25 flr 2006-04-28 14:34:21 UTC 
flr:
I would like to see this fixed myself asap. However some fundamental research
regarding the binary structure is required here. Do not expect this research to
be sucessfull soon... Damn binary formats...
Comment 26 michael.ruess 2006-05-16 07:35:57 UTC 
*** Issue 65402 has been marked as a duplicate of this issue. ***
Comment 27 michael.ruess 2006-06-09 13:00:55 UTC 
*** Issue 66274 has been marked as a duplicate of this issue. ***
Comment 28 michael.ruess 2006-08-15 15:13:49 UTC 
*** Issue 68632 has been marked as a duplicate of this issue. ***
Comment 29 xaliger 2006-08-21 09:52:06 UTC 
Please, do not forget to RTF ("open" format) import/export filter. Its nested 
tables are broken as well (some duplicates are desribing it)
Comment 30 Mathias_Bauer 2006-08-30 15:30:49 UTC 
assigning to hbrinkm
Comment 31 michael.ruess 2006-08-31 13:20:15 UTC 
*** Issue 69134 has been marked as a duplicate of this issue. ***
Comment 32 kjpetrie 2006-09-24 00:20:39 UTC 
Is this summarised correctly? I get the problem when saving and opening 
in .odt format, not just Word. I can send a file if that helps but maybe some 
of the dupes have already done that (I'm not wading through them all to see). 
 
It's not good it's remained unfixed for so long. Is there a workaround?
Comment 33 utomo99 2006-10-31 10:07:32 UTC 
is there any chance that this issue targeted for OOo 2.2 ? Please consider.
as this issue more than  2 years old and have many duplicate ? 

Thanks
Comment 34 michael.ruess 2007-02-27 09:05:39 UTC 
*** Issue 74900 has been marked as a duplicate of this issue. ***
Comment 35 michael.ruess 2007-03-01 13:11:39 UTC 
*** Issue 75018 has been marked as a duplicate of this issue. ***
Comment 36 alistairmann 2007-03-02 18:31:17 UTC 
This is exactly the kind of issue that has made it hard for me to introduce OOo
into office environments, as only discovering the lack of support for
tables-in-tables once the document has been closed, and their changes lost, 
reduces user confidence that anything else will save properly.

Suggested workaround:

Given no realistic expectation of near term fix, I suggest that if Writer can be
made to merely detect user creation of tables-in-tables, then it could
A) Reform the outside table so as to accomodate the second table as additional cells
B) Inform the user that tables-in-tables is not yet supported, perhaps with
offer to reform the table as in A above.

A) example: With an outside table of 2x2, on detection of an inside table of
2x2, the outside table could be reformed to be 3x3 wide.

Suggested workaround would stop the duplicate defect reports; would be more
easily achieved than the binary structure research and so be bought forward in
terms of milestones; and would increase user confidence by virtue of clueing
them into a OOo skill (larger tables rather than nested tables) they can reuse.

Cheers,
Comment 37 michael.ruess 2007-04-10 11:28:06 UTC 
*** Issue 76200 has been marked as a duplicate of this issue. ***
Comment 38 richlv 2007-05-03 13:37:24 UTC 
if a nested table is changing the position after saving as .doc and re-opening, is that a subset of 
this issue ? when this is considered fixed, should that problem also be fixed ?
Comment 39 jitin_21 2007-07-27 10:35:53 UTC 
it is not only when we reopen a file after saving as .doc, table also gets 
disturbed when we open an existing MSOffice file.
Comment 40 Rainer Bielefeld 2007-12-01 07:28:54 UTC 
*** Issue 84131 has been marked as a duplicate of this issue. ***
Comment 41 eric.savary 2008-01-22 08:17:13 UTC 
*** Issue 85440 has been marked as a duplicate of this issue. ***
Comment 42 pkidwell 2008-07-22 20:16:51 UTC 
If it helps, seems that nested tables import much more cleanly from DOCX (MS
Word XML format) than from DOC (binary format).  (Other things, such as
graphics, don't import as cleanly, but the tables look fine.)
Comment 43 openoffice 2008-08-15 15:07:42 UTC 
started
Comment 44 Rainer Bielefeld 2008-08-24 08:51:00 UTC 
*** Issue 93059 has been marked as a duplicate of this issue. ***
Comment 45 openoffice 2008-08-27 15:41:17 UTC 
fixed in hb11
Comment 46 michael.ruess 2008-09-23 13:21:55 UTC 
*** Issue 94168 has been marked as a duplicate of this issue. ***
Comment 47 openoffice 2008-09-24 12:22:51 UTC 
ready for QA
Comment 48 michael.ruess 2008-11-11 08:24:03 UTC 
*** Issue 96060 has been marked as a duplicate of this issue. ***
Comment 49 michael.ruess 2008-11-14 11:19:37 UTC 
Verified in CWS hb11for301.
Comment 50 michael.ruess 2008-12-01 10:36:05 UTC 
*** Issue 95851 has been marked as a duplicate of this issue. ***
Comment 51 michael.ruess 2009-01-09 11:02:26 UTC 
Checked this in OOO300m14 build for OO 3.0.1 branch and in DEV300m38 for OO 3.1
branch.
Comment 52 michael.ruess 2009-01-23 15:27:48 UTC 
*** Issue 98409 has been marked as a duplicate of this issue. ***
Comment 53 openoffice 2009-03-05 08:52:28 UTC 
*** Issue 78806 has been marked as a duplicate of this issue. ***