Bug 73820 - Cells merging is lost when copied Calc-range is pasted to Writer as formatted text (RTF)
Summary: Cells merging is lost when copied Calc-range is pasted to Writer as formatted...
Status: RESOLVED DUPLICATE of bug 65090
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.4.2 release
Hardware: x86-64 (AMD64) All
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-20 07:46 UTC by vlhown
Modified: 2015-01-24 12:37 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Illustration (37.44 KB, image/png)
2014-01-20 07:46 UTC, vlhown 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description vlhown 2014-01-20 07:46:05 UTC 
Created attachment 92425 [details]
Illustration

Bug modelling:
1. In Calc copy arbitrary range with merged cells.
2. Paste it as formatted text (RTF) to Writer - mergings are lost.

Tested on LO 4.1.4.2, 4.2.0.2 rc Ubuntu 13.10, LO 4.1.3.2 Windows XP.
LO 3.x pastes correctly.

The severity is assigned to critical becаuse pasting as formatted text is the only way to transfer formatted tables from Calc to Writer not as OLE-object.
Comment 1 Miklos Vajna 2014-01-20 07:53:15 UTC 
Isn't this a duplicate of bug 65090?
Comment 2 vlhown 2014-01-20 08:49:08 UTC 
(In reply to comment #1)
> Isn't this a duplicate of bug 65090?

yes, sorry, but that is marked as RESOLVED,FIXED
Patch is not included in 4.2.0.2rc?
Comment 3 Dominique Boutry 2014-01-29 13:03:33 UTC 
What I see in LibO 4.2.0.3 on Win7, when pasting in Writer as RTF a Calc range with merged cells :
- the merging is correctly pasted, into a Writer table
- but the borders are not copied (no matter what border I set in Calc, the copied table in Writer always show no borders).
Comment 4 Björn Michaelsen 2014-03-06 17:20:29 UTC 
marking as dupe as per comment 2.

The behaviour in comment 3 should probably be reported in a separate bug report if it persists.

*** This bug has been marked as a duplicate of bug 65090 ***