After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 698389 - incorrect axis label angle in chart imported from ods
incorrect axis label angle in chart imported from ods
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: import/export OOo / OASIS
git master
Other Linux
: Normal normal
: ---
Assigned To: Andreas J. Guelzow
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2013-04-19 18:28 UTC by Andreas J. Guelzow
Modified: 2013-04-22 00:51 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
sample file (339.84 KB, application/vnd.oasis.opendocument.spreadsheet)
2013-04-19 18:28 UTC, Andreas J. Guelzow 		Details

Description Andreas J. Guelzow 2013-04-19 18:28:44 UTC 
Created attachment 241944 [details]
sample file

When importing the attached file, the text labels for th horizontal axes are rotated 180 degrees while in LO they are only rotated 90 degreed.

We should investigate whether we or LO are following the ODF standard or whether the ODF standard is underspecified.
Comment 1 Andreas J. Guelzow 2013-04-22 00:35:11 UTC 
In mstyle.h we have:

/* -1 == vertical, 0..359 == rotation */
void		 gnm_style_set_rotation	   (GnmStyle *style, int r);

When we are reading the ods file we encounter an angle of 270 degrees, and set the angle to 270.

I note that the angle selection interface on in the graph properties dialog on the other hand implies angles from -180 to +180.

Are we enforcing one of these ranges??
Comment 2 Andreas J. Guelzow 2013-04-22 00:44:09 UTC 
I am looking in the wrong place. We are using for this attribute
go_style_set_text_angle
which is clearly documented to require -180.0 to +180.0.
Comment 3 Andreas J. Guelzow 2013-04-22 00:51:18 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.