Bug 69824 - Other: copying chart to writer with data series in rows will corrupt the chart
Summary: Other: copying chart to writer with data series in rows will corrupt the chart
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
Version:
(earliest affected)
4.1.2.3 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-25 20:17 UTC by Tohotom
Modified: 2013-12-22 20:38 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Spreadsheet file (12.68 KB, application/vnd.oasis.opendocument.spreadsheet)
2013-12-14 17:00 UTC, Tohotom
Details
ODT file with graphs (16.35 KB, application/vnd.oasis.opendocument.text)
2013-12-14 17:01 UTC, Tohotom
Details
PDF for illustration (39.49 KB, application/pdf)
2013-12-14 17:02 UTC, Tohotom
Details
same example but working (31.94 KB, application/vnd.oasis.opendocument.text)
2013-12-21 14:23 UTC, Jean-Baptiste Faure
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tohotom 2013-09-25 20:17:04 UTC
Problem description: 

Copying charts (as Star Object Descriptor XML)  with data series in rows to a Writer file will make the chart loose almost all of it's data (except for one random cell). Text documents containing charts, created with earlier versions of LO will be also affected. 

Charts with data series in columns worked just fine.
Copying charts in GDI metafile format behaved as expected.

I'm using Debian 7 (64-bit).

Steps to reproduce:
1. Create a chart with data series in rows.
2. Paste it into a writer document as a Star Object Descriptor (XML)

Current behavior:
Chart gets corrupted after copied to Writer document.

Expected behavior:
Chart should look the same as in Calc. 

              
Operating System: Debian
Version: 4.1.1.2 release
Comment 1 Tohotom 2013-10-04 15:54:28 UTC
This is still present in the latest stable release (4.1.2). Linux (64bit) and win (32bit) version too. 

Files created with older versions (thus with working charts) will permanently break inserted charts in the odt file.
Comment 2 ign_christian 2013-10-11 10:11:45 UTC
Using Column 'Normal' chart, I can't reproduce with LO 3.6.7.2 (Ubuntu 12.04 32bit)

@Tohotom, could you attach sample file with that problem?
Comment 3 ign_christian 2013-10-11 13:14:21 UTC
Hi Tohotom, please see also Bug 68948. Perhaps you reported same problem?
Comment 4 Jean-Baptiste Faure 2013-11-23 18:21:14 UTC
Dear reporter: please could you answer the question in comment #3 ?

We need to know what kind of corruption affects the chart when it is copied in a text document.

Best regards. JBF
Comment 5 Tohotom 2013-12-14 16:59:08 UTC
Hi,

Sorry for this late response. I created a few samples with he latest stable of LO (4.1.3) but the behavior is the same. If i copy a graph with data series in rows to writer the graph will not be rendered correctly, also opening the .odt file created in 4.1.3 with an earlier version of LO (4.0.6) will produce the same rendering even if pasteing the chart into text files in this version (4.0.6) works as expected.

I will attach the ods and odt files created in LO 4.1.3 and the odt file as a pdf too, to illustrate the graph what i get.

Best regards,
Tohotom
Comment 6 Tohotom 2013-12-14 17:00:23 UTC
Created attachment 90775 [details]
Spreadsheet file
Comment 7 Tohotom 2013-12-14 17:01:21 UTC
Created attachment 90776 [details]
ODT file with graphs
Comment 8 Tohotom 2013-12-14 17:02:03 UTC
Created attachment 90777 [details]
PDF for illustration
Comment 9 Jean-Baptiste Faure 2013-12-21 14:23:15 UTC
Created attachment 91085 [details]
same example but working

I tested your procedure with the generic Linux version 4.1.4.2 (current stable version released on 2013-12-18, built by TDF) and my home built versions 4.1.5.0+ and 4.2.0.1+. With each of these versions it works as expected as shown by my attachment.
So closing this bug report as resolved/worksforme (worksforme instead of fixed because I do not know which commit fixed the problem).

Please, upgrade your version to the 4.1.4 and try again. Feel free to reopen if it does not work for you.

Best regards. JBF
Comment 10 Tohotom 2013-12-22 20:38:03 UTC
Thanks, upgrading to version 4.1.4.2 solved the problem.

Best regards,
T.