Bug 55721 - FILESAVE: Gradient colored charts looks striped in WORD
Summary: FILESAVE: Gradient colored charts looks striped in WORD
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version: 3.6.1.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-07 09:22 UTC by szz
Modified: 2013-03-04 21:36 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments
zipped odt,ods used for creating doc file (step1-2) plus saved doc file (step3) and as they seems on my machine on jpg-s (178.68 KB, application/zip)
2012-10-07 09:22 UTC, szz
Details

Description szz 2012-10-07 09:22:37 UTC
Created attachment 68196 [details]
zipped odt,ods used for creating doc file (step1-2) plus saved doc file (step3) and as they seems on my machine on jpg-s

Problem description: 
When I want to create a (97/2000/XP/2003)DOC file by Writer with charts that looks nice and gradient fill us used on them. The chart looks OK in LO but looks ugly in Word. 
( LO 3.6.1.2 Portable;MS Off 2003 Word). (strange but this is not a problem in case of CALC->EXCEL )

Steps to reproduce:
1. create chart in CALC and fill bars with gradient color
2. copy -paste chart to a new WRITER text document
3. save as 97/2000/XP/2003 Word DOC file
4. open it in Word

Current behavior:
While chart looks nice in LO in Word bars seems striped

Expected behavior:
should be shown in WORD as in LO

Platform (if different from the browser): 
XP prof. EN
              
Browser: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20100101 Firefox/15.0.1
Comment 1 A (Andy) 2013-03-02 13:57:48 UTC
reproducible with LO 4.0.0.3 (Win7 Home, 64bit)

This issue (as reported) can be reproduced for many, but not for all gradient color combinations.  But in all cases a thin buggy border around the bars can be found.

I could reproduce it for the following combinations:
- Gradient 1
- Gradient 2
- Linear Blue/White
- Radial Red/Yellow
- Axial Light Red/White
- Linear Magenta/Green
- Linear Yellow/Brown

I could not reproduce it for the following combinations:
- Gradient 3
- Gradient 4
- Gradient 5
- Gradient 6
- Radial Green/Black
- Rectangular Red/White
- Square Yellow/White
- Ellipsoid Blue Gray/Light Blue

@Miklós: Could this maybe be an issue for you?
Comment 2 szz 2013-03-02 20:04:07 UTC
(In reply to comment #1)
> reproducible with LO 4.0.0.3 (Win7 Home, 64bit)

Hi,
In that case shouldn't be changed the version to 4.0.0.3? 
Because it seems nobody (else) cares about it. But I think without solving such chart and compatibility issues LO is not the thing which can be the replacement of MSO.  :(  
Zoltan
Comment 3 A (Andy) 2013-03-02 20:44:41 UTC
I would propose to keep 3.6.1.2, even if I have reproduced it only now with LO 4.0.0.3, because this is the release, where it was reported the first time.  We should keep in this field the first release with the problem, so that programmers have the information about a regression and that they can track it back to the maybe last change before that bug was reported.
We have several other bugs, where we have the same situation and the many LO programmers are working hard to solve them, but of course it can take some time.
Comment 4 Miklos Vajna 2013-03-04 08:50:30 UTC
If this is a 3.6 -> 4.0 regression, please bibisect it:

https://wiki.documentfoundation.org/Bibisect

Thanks!
Comment 5 szz 2013-03-04 21:36:54 UTC
(In reply to comment #4)
> If this is a 3.6 -> 4.0 regression, please bibisect it:
> 
> https://wiki.documentfoundation.org/Bibisect
> 
> Thanks!


Hi,
From the link you have given:
"The bibisect is only possible for Bugs which are reproducible under Linux,"

Unfortunately I don't know if it is coming on Linux or not. I am afraid I cannot do it. Both of us use LO Win version as you see.

Could anyone else help us with this from this list, please?
BR Zoltan


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.