To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=105195


User mru changed the following:

                What    |Old value                 |New value
================================================================================
             Assigned to|writerneedsconfirm        |hbrinkm
--------------------------------------------------------------------------------
          Ever confirmed|                          |1
--------------------------------------------------------------------------------
                  Status|UNCONFIRMED               |NEW
--------------------------------------------------------------------------------
                 Summary|embedded excel sheet not v|WW8: Excel OLE following a
                        |isible at all in writer   | nested table not visible 
                        |                          |at all in writer
--------------------------------------------------------------------------------
        Target milestone|---                       |OOo 3.3
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Tue Sep 22 14:18:39 +0000 
2009 -------
MRU->HBRINKM: see attached document. There, an OLE object directly follows a
nested table. Our import fully ignores this object since the import of nested
tables has been reworked in OOo 3.0.1.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to