Issue 20193 - Q-PCD MSInteroperability-19
Summary: Q-PCD MSInteroperability-19
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: All All
: P2 Trivial with 2 votes (vote)
Target Milestone: OOo 2.0
Assignee: andreas.martens
QA Contact: issues@framework
URL:
Keywords:
: 5097 9713 19770 24265 25713 36031 (view as issue list)
Depends on:
Blocks:
 
Reported: 2003-09-26 15:09 UTC by andreas.martens
Modified: 2006-09-23 12:54 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description andreas.martens 2003-09-26 15:09:41 UTC
Source
Users, Enterprises

Category
Improve Writer Filters

Product Requirement 
Better Interoperability with Microsoft Tables 

Customer Need/Problem
Improved im-/export of tables:
1. Improved graphic positioning in tables. 
2. Table inside tables.
3. Cells or rows which are able to break at the page border.
4. More line styles
5. Patterns as cell background

Comment
-

Eng Effort
HI

Eng Owner
Andreas Martens

Product Concept
1. As part of the Writer 'Frame/Drawing object unification' specification
support for frames that are located outside a cell or column will be added (Page
wrapping will not be supported for these frames).  In addition to this,
frames/drawing objects that are anchored as character might get wider than the
page area. 
2. As part of  the 'Table enhancements' specification tables within tables will
be supported. 
3. Automatic page and column breaks within table cells will be implemented ->
issue 20187
4. Additional line styles for borders will be created
5. Patterns as background will be added. 
6. The maximal count of cells in Writer tables (65535 cells in OOo 1.1) will be
enhanced.
7. The capabilities for merging cells will be improved.

Functional Specification
'Writer frame/drawing object unification' specification
'Table enhancements' specification
Comment 1 andreas.martens 2003-09-26 15:17:10 UTC
Specs will follow.
Comment 2 lutz.hoeger 2003-10-23 07:43:41 UTC
added keyword Q-PCD
Comment 3 bettina.haberer 2003-10-23 12:03:33 UTC
*** Issue 9713 has been marked as a duplicate of this issue. ***
Comment 4 bettina.haberer 2003-10-23 16:29:53 UTC
*** Issue 5097 has been marked as a duplicate of this issue. ***
Comment 5 lamarcbr 2003-10-25 21:55:31 UTC
Thank you for documenting planned improvement to the software. Can
please consider the following:

"Allow the adjustment of row height through the use of the mouse." 

Column width for tables can be adjusted through the use of the mouse
already. This is would make the operation consistent.
Comment 6 mci 2003-11-27 10:47:57 UTC
*** Issue 19770 has been marked as a duplicate of this issue. ***
Comment 7 askoning 2004-01-10 14:03:24 UTC
*** Issue 24265 has been marked as a duplicate of this issue. ***
Comment 8 michael.ruess 2004-02-27 13:29:12 UTC
*** Issue 25713 has been marked as a duplicate of this issue. ***
Comment 9 frank.meies 2004-05-19 08:26:20 UTC
For 'tables in tables' see issue 25676.
Comment 11 lokillo 2004-10-13 19:50:13 UTC
just to clarify, as of OpenOffice.org 1.9.56 we still cannot merge cells in
slightly complex tables, frustrating, to say the least. Is it planned for 2.0 ?
keep up the good work though.
Comment 12 andreas.martens 2004-10-15 12:54:19 UTC
No, it was not planned to change our table model for OOo2.0 completely. And our
plan to improve the merge algorithmn to allow merging in more situations without
changing ou table model is unfortunately waiting for free resources which we
don't have at the moment. We did a lot of work in table improvement but the
merging of cells will be an open issue :-(
Comment 13 lohmaier 2004-10-24 16:27:38 UTC
*** Issue 36031 has been marked as a duplicate of this issue. ***
Comment 14 megatux 2004-11-25 23:48:22 UTC
The table cell merge issue is probably one of the most annoying things about
Writer at this point.  It's a show-stopper.  It's one of those things that
touches real world users and generates a huge number of real world complaints. 
Frankly, this needs fixed by 2.0.  It is much more important than some of the
nice fluffy extras being prioritized at this point -- which really *could* wait.

If this is a matter of designing a new table model, why not get it over with? 
More importantly, if this is going to affect the new OASIS file formats then
this is even more important to fix now -- even if it were to push back the final
release another week.
Comment 15 bombjack 2005-02-04 00:48:52 UTC
Merging vertically overlapping cells isn't even slightly possible in 1.9.74 so
why is this issue marked as fixed?

There are surely many people angry about that.
This IS a REAL LIFE PROBLEM!

This is not even possible:

     1     2
 +-----+
1|     |
 +     +-----+
2|     |     |
 +-----+     +
3      |     |
       +-----+

What's that?
Comment 16 andreas.martens 2006-03-29 14:43:46 UTC
There will be a follow-up task with a specification when we will implement a new
table model.
This one can be closed.
Comment 17 ace_dent 2006-09-23 12:54:48 UTC
>'ama'... follow-up task?...

The problem of merging cells in a row of varying cell heights / adjusting
individual row heights, is covered by Issue 4032. Regards, Andrew.