Issue 59288 - Fileformat Violation when saving manual scales for percent charts
Summary: Fileformat Violation when saving manual scales for percent charts
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: chart (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: jogi
QA Contact: issues@graphics
URL:
Keywords: oooqa
: 65523 (view as issue list)
Depends on:
Blocks:
 
Reported: 2005-12-13 13:37 UTC by IngridvdM
Modified: 2013-02-24 21:22 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Example File (23.47 KB, application/vnd.oasis.opendocument.spreadsheet)
2005-12-13 13:41 UTC, IngridvdM 		no flags Details
test case (6.42 KB, text/html)
2007-05-08 08:54 UTC, jogi 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description IngridvdM 2005-12-13 13:37:58 UTC 
Create a percent stacked chart (e.g. an percent stacked area chart).
Change the scale of the y axis from automatic values to manual values.
For example: Minimum 12 Percent, Maximum 160 Percent, Major Interval 18 Percent
and Axis at 15 Percent.
The number format is percent ( 0,00% ).
Saving the chart you get following result in the content.xml:

chart:minimum="12" chart:maximum="160" chart:origin="15" chart:interval-major="18"
and a percent numberformat.

These values are wrong. It should be:
chart:minimum="0.12" chart:maximum="1.6" chart:origin="0.15"
chart:interval-major="0.18" and a percent numberformat.
Comment 1 IngridvdM 2005-12-13 13:41:39 UTC 
Created attachment 32345 [details]
Example File
Comment 2 IngridvdM 2005-12-13 13:44:17 UTC 
The attached File containes the percent stacked area chart from the example and
a not stacked column chart with same scale values where the number format was
changed manually to percent. In the column chart example the values are exported
correctly to the file.

After the export is fixed, the import also has to be fixed. The old wrong format
and the new corrected format both have to be imported properly.
Comment 3 bjoern.milcke 2005-12-14 09:30:21 UTC 
accepted
Comment 4 bjoern.milcke 2005-12-20 12:40:19 UTC 
Files created with OOo 2.0 or OOo 2.0.1 and saved with OOo 2.0.2 will get
corrupted due to a missing working fileformat versioning.  When a file is
created with OOo 2.0 and loaded with a version containing these fixes and saved
again, the files will get corrupted, because the OLE objects are just copied as
they are (saved with OOo 2.0), but the parent document is re-saved with the new
version.  As OLE objects have no own meta information, they inherit it from
their parent which in this case (the default) is wrong.
Comment 5 bjoern.milcke 2006-05-19 13:08:46 UTC 
This issue depends on the existence of Meta information for OLE objects (Issue
60323).
Comment 6 bjoern.milcke 2006-05-19 13:15:56 UTC 
*** Issue 65523 has been marked as a duplicate of this issue. ***
Comment 7 bjoern.milcke 2006-06-23 14:04:29 UTC 
Changed Target to 2.x
Comment 8 IngridvdM 2006-11-30 15:39:27 UTC 
I'll take over.
Comment 9 IngridvdM 2006-11-30 15:41:33 UTC 
fixed in CWS chart2mst3.
Comment 10 IngridvdM 2006-12-13 21:28:58 UTC 
@Thomas: Fixed in CWS chart2mst3 milestone10, please verify.
Comment 11 kla 2007-01-02 10:12:42 UTC 
*** Issue 72978 has been marked as a duplicate of this issue. ***
Comment 12 IngridvdM 2007-01-18 11:49:06 UTC 
changed target to 2.3
Comment 13 kla 2007-05-07 09:19:15 UTC 
@Jsi: pls verify this issue
Comment 14 jogi 2007-05-08 08:54:17 UTC 
Created attachment 44923 [details]
test case
Comment 15 jogi 2007-05-08 08:56:59 UTC 
The issue has been fixed but the Object 1/content.xml is invalid against ODF 1.1
because of #76130# which also has been fixed in that build.

@mib: We don't distinguish in the UI of the application that we write now
different versions of ODF. Would be nice to know what we want to do to make that
more transparent.
Comment 16 ace_dent 2008-05-16 03:31:52 UTC 
This Issue is 'Verified' and not updated in 1yr+, so Closing.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew
 
Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~