We must not export label position properties for doughnut charts, else
MS Office would think the file is corrupt.
Change-Id: Icfab257ffb6da945b8add661e6455aa66cc475ab
"Automatic" fill in docx and xlsx should be solid white, whereas in
pptx it is no fill (transparent).
Change-Id: I7e64f2f895e4c4ed072a234e622a348599456f37
Originally it was a pptx document, but switched to docx because reloading
an impress document in cppunit currently mysteriously crashes.
Change-Id: I3e9ba6b9a4dc7d3c0ca1d59a073dc8a4cca4008c
It needs to be set, so that the chart has colors. It was grey before.
The bug was fixed already in aacfd5038d05a02f8b1eade3a5896d3d7e959f3d,
which got pushed sooner, so this commit only changes
the property name from 'INVALID' to 'FillTransparenceGradientName'.
Change-Id: If06899258a4307d583480538338480ba5bb830b9
Right now, we skip hidden data series when importing OOXML charts into
our internal data table. This of course means that if/when we add support
for hidden columns in the internal data table, we may want to change this.
Change-Id: Ida1b77821fbc2f8f937244576b52521b59d6ab89
Not a direct test for the reported bug, but to ensure that the reworked
properties survive import and export.
Change-Id: I6c5a4c98eca5180251f04a24346290dedc44447a
Ideally now all testcases handle both cases during DOCX import:
- current situation, when shape with text is imported as a Writer
TextFrame
- future situation, when shape with text will be imported as shape with
an assicated TextBox
Change-Id: I5b95ff4672cecf39eb744f8557f967ade73404c0
I've switched from using a Draw document to Writer document due to some
instability with Draw instance in our cppunit run. The bug is reproducible
either way.
The test is disabled for now, since the bug has yet to be fixed.
Change-Id: I49e0417e1ecbc70f40aab8531237ae98ae58bdd3
Problem Description: Docx file containing a chart (line chart / scatter chart)which has used a builtin
marker'x' gets corrupted when we save it in LO.The reason was that while exporting LO was writing the
marker information 'x' as 'X' which MS Word doesn't recognize.‒<c:marker><c:symbol val="X" />. Also
the size of the marker was coming 1 less than the actual value. Ex: if size is 7 then it was being
written as 6.
Solution: During export I have made changes so that now LO writes 'x' in the tag information
‒<c:marker> <c:symbol val="x" />. Now the size of the marker is also being correctly exported.
Change-Id: I26b747f9576625bf3acb941322ae418a0bbc6b64
Reviewed-on: https://gerrit.libreoffice.org/9273
Tested-by: Miklos Vajna <vmiklos@collabora.co.uk>
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
Tested-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
