| Summary: | Chart Axis Number Format not display correctly in XLS but ODS is working | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Peter Oh <peteroh007> |
| Component: | Chart | Assignee: | Markus Mohrhard <markus.mohrhard> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | xiscofauli |
| Priority: | medium | Keywords: | preBibisect, regression |
| Version: | 3.5.0 release | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | target:6.3.0 target:6.2.0.1 target:6.1.5 | ||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 75057 | ||
| Attachments: |
Sample Chart in XLS file format
Display wrong number format in Calc Display Correct Axis number format in MS Excel or Excel Viewer Correcting Axis number format |
||
|
Description
Peter Oh
2017-01-10 11:53:59 UTC
Created attachment 130299 [details]
Sample Chart in XLS file format
Created attachment 130300 [details]
Display wrong number format in Calc
Created attachment 130301 [details]
Display Correct Axis number format in MS Excel or Excel Viewer
Created attachment 130302 [details]
Correcting Axis number format
Confirmed in - Version: 5.4.0.0.alpha0+ Build ID: 9a30cb2161506e003f14592d83075ab9d30516c1 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2; Locale: ca-ES (ca_ES.UTF-8); Calc: group - Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e - Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) but not in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 Also reproduced in LibreOffice 3.5.0 Build ID: d6cde02 ** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug This was a tough one. Actually we fixed the issue that was the initial problem quite some time ago. However a second issue crept in that resulted in this specific configuration to still fail. For quite some time the source number format flag was imported again correctly, however, we took the source number format from the string cells. As a result this still picked up the wrong number format. Markus Mohrhard committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/fb04e7180cdf656dbbd3daa9c81615d9478229e0%5E%21 tdf#105236, only take number format from numeric cells It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Markus Mohrhard committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/92c25a6163dca79987fd8fe7c3efd5527edc29b5%5E%21 add test for tdf#105236 It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Markus Mohrhard committed a patch related to this issue. It has been pushed to "libreoffice-6-2": https://git.libreoffice.org/core/+/5908f1ea0a19482a999c2e00aeaae05eabc1e8e6%5E%21 tdf#105236, only take number format from numeric cells It will be available in 6.2.0.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Markus Mohrhard committed a patch related to this issue. It has been pushed to "libreoffice-6-1": https://git.libreoffice.org/core/+/811d39b4ed3487ac6eb81d04de70f9845fec32db%5E%21 tdf#105236, only take number format from numeric cells It will be available in 6.1.5. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. |