Description: When I converted MS word document to PDF with command line below: xxxxxx/program/soffice.bin --convert-to pdf:writer_pdf_Export xxxxxxxx Then I found half of a orange line in a graph disappeared (page3), which exists when I produced PDF with LO5.3.4. I also opened this document with LO6.0(Ubuntu18.04) and found the same result. Steps to Reproduce: There are two ways to reproduce it. [1] 1. Open attached word document with LO6.0 2. Half of orange line in a graph (page 3) is disappeared. [2] 1. Convert attached word document with LO6.3.1 xxxxxx/program/soffice.bin --convert-to pdf:writer_pdf_Export xxxxxxxx 2. Open a generated pdf You can find this does not happen when you use LO5.3.4. Actual Results: Half of orange line in a graph (page 3) is disappeared. Expected Results: Orange line in a graph (page 3) is rendered correctly. Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 154208 [details] Original document
Created attachment 154209 [details] Produced PDF by LO6.3.1
Created attachment 154210 [details] Produced PDF by LO5.3.4
Reproduced in Version: 6.4.0.0.alpha0+ Build ID: c9336bfb6bbf6d73d3f23c124262ade30133448d CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-US (ca_ES.UTF-8); UI-Language: en-US Calc: threaded in Version: 5.2.0.0.alpha1+ Build ID: 5b168b3fa568e48e795234dc5fa454bf24c9805e CPU Threads: 4; OS Version: Linux 4.15; UI Render: default; Locale: ca-ES (ca_ES.UTF-8) the graph line is shifted to the left...
actually this is a regression from author Jean-Tiare Le Bigot <admin@jtlebi.fr> 2016-10-13 21:43:41 (GMT) committer Markus Mohrhard <markus.mohrhard@googlemail.com> 2016-11-06 06:02:27 (GMT) commit 4bcf1872bbe9db1388769485a7e4c0cbcce3d53c (patch) tree 0110875cf6db25b7208099e9394995254111b221 parent 17e9dc436bc6ad8d3a5bbde15d4d47262650aa2c (diff) chartx: fix sparse chart import Adding CC: to Jean-Tiare Le Bigot
@Balazs Varga, I thought you might be interested in this issue... regression from the same commit as bug 103963
Still reproducible in Version: 6.4.0.0.alpha0+ Build ID: 9b5dad13b56bdde7c40970351af3da3a2c3c9350 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded
Created attachment 155602 [details] Screenshot of the original document side by side in Word and Writer master In current Writer master this yellow line looks like in Word: Version: 6.4.0.0.alpha1+ (x86) Build ID: 80109586e6cb6d3e2e0a53a9079c3125ec9b8368 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; Locale: hu-HU (hu_HU); UI-Language: en-US Calc: CL So half of it being gone can be considered normal. If that is not desired, one can change the Data Series - Options - Plot Options to Assume Zero. There are some other problems with this chart, like positioning / text wrapping (bug #104703 and its friends) and no option for legend not overlap the chart (bug #75330). Also the data series represented by the grey area chart has different name in Word than in Writer (I'll file a new one about that).
So what is this bug report covering now? (In reply to NISZ LibreOffice Team from comment #8) > In current Writer master this yellow line looks like in Word: Yeah, the entire bug report is a bit strange because even in Word 2003 the yellow line never dropped to the bottom, so why was the report created in the first place. NISZ usually uses a fairly recent version of Word, so I assume this has been true for modern Word as well. > legend not overlapping the chart (bug #75330). I guess we can leave this report open to take care of this. Although the legend now is not overlapping the last line, a large portion is still overlapped.
repro 24.2+
Dear mitsutakasato, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
repro 26.2+: the legend is still overlapping the graph.
Created attachment 205073 [details] tdf127586-1_bad.docx: round-tripped file reported as corrupt by MS Word Although no one has mentioned it here, when LO saves this file, it is no longer able to be opened in MS Word. That has been true ever since the chart has been showing - since LO 4.2 Somewhere between git log 1a4258667ecd76cebc823994fd..862766d569e51d91c111 the chart1.xml started showing up, and since then it is reported as corrupt.
Created attachment 205074 [details] tdf127586-1_good.docx: for comparison - the file round-tripped before the chart could be seen