Created attachment 118730 [details] sample Steps: 1) Open attached file 2) Notice that the second bar has a label 'Yousuf; 2', but it is supposed to be 'Yousuf, 2'. Version: 5.1.0.0.alpha1+ Build ID: eb2e1ab4651350bffc53f618961a910bd3bbcfd9 TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2015-09-02_23:57:52 Locale: en-US (en_US.UTF-8)
Hi Yousuf, I got the semicolon by importing the file in Calc, but also by opening it in Excel 2010, and changing there the separator to coma, gives a coma after import in Calc.
Created attachment 118735 [details] screenshot Hi Jacques, This file was created with excel 2010.
Excel 2010 and LO 5.0.1.2: in both is label 'Yousuf; 2' => problem is in excel2013?
Created attachment 118756 [details] screenshot from excel 2013
Created attachment 118758 [details] printscreen from excel2010
Excel 2013 displays Yousuf; 2 for me (same as LibO). Win 8.1 32-bit MSO 2013 LibO Version: 5.0.3.1 Build ID: fd8cfc22f7f58033351fcb8a83b92acbadb0749e Locale: fi-FI (fi_FI)
Marcus stated on IRC "it is not a bug, the file does not specify the separator so the application selects one (most likely based on the UI language)". But when i asked him whether LO does the same of selecting an appropriate separator based on UI language, he said he didnt know.
(In reply to Yousuf (Jay) Philips from comment #7) > Marcus stated on IRC "it is not a bug, the file does not specify the > separator so the application selects one (most likely based on the UI > language)". Ok, so NOTABUG > But when i asked him whether LO does the same of selecting an > appropriate separator based on UI language, he said he didnt know. Got an appropriate test to use to confirm this one way or another? (I'll toss in NEEDINFO for now)
@Eike: Can you give your input on this so it can be closed as NOTABUG if possible?
Citing Ecma OOXML: 21.2.2.166 separator (Separator) This element specifies text that shall be used to separate the parts of a data label. The default is a comma, except for pie charts showing only category name and percentage, when a line break shall be used instead. But apparently Excel doesn't follow its own standard and uses a semicolon instead, or even locale dependent? Loading the file in Excel2010 with English locale I get semicolon as well. However, if the value is absent we do the same and use "; ". We did not implement anything locale specific. It's also not clear to me what separator that would be, it might be it is the array/matrix row separator. But the Chart model doesn't know about that anyway when reading the OOXML DrawingML part. This ranks in a very low "fix if someone wants to scratch an itch until s/he bleeds" importance, researching/implementing this wouldn't be trivial and the effort per gain ratio for me just isn't worth it.
Or we just take what OOXML specifies and use comma. Period. ;-)
updatetest
@Jacques, @raal: What OS locale do you have on windows when you tested? You can used `systeminfo` to check this. I am using 'en-us;English (United States)'. (In reply to Eike Rathke from comment #11) > Citing Ecma OOXML: > 21.2.2.166 > separator (Separator) > This element specifies text that shall be used to separate the parts of a > data label. The default is a comma, > except for pie charts showing only category name and percentage, when a line > break shall be used instead. Could there be a difference between the ecma, transitional and strict about this? By the way, how to determine if ooxml version a document is saved in? > But apparently Excel doesn't follow its own standard and uses a semicolon > instead, or even locale dependent? Loading the file in Excel2010 with > English locale I get semicolon as well. Was it english US locale? (In reply to Eike Rathke from comment #12) > Or we just take what OOXML specifies and use comma. > Period. ;-) As everyone else but me sees it as a semicolon in excel, its likely better to leave it that way. :D
(In reply to Yousuf (Jay) Philips from comment #14) > Could there be a difference between the ecma, transitional and strict about > this? Yes of course it could, but I didn't investigate. > By the way, how to determine if ooxml version a document is saved in? Probably in the namespaces and markup compatibility, but I don't know off-head details. Anyway, only MS-Office 2013 started to write OOXML Strict, everything else is transitional, and the default still is transitional. > Was it english US locale? Yes. > (In reply to Eike Rathke from comment #12) > > Or we just take what OOXML specifies and use comma. > > Period. ;-) > > As everyone else but me sees it as a semicolon in excel, its likely better > to leave it that way. :D Likely. Unless someone wants to get hands dirty and implement the Excel behavior.
** 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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
Hi all, By digging a little, I found that the separator can be choosen for each label. There is no obligation of consistency between labels, even if we feel it as such. I join a screenshot of the setting window.
Created attachment 135965 [details] Label formating Window
Probably these patches could help here. But I also think this is not a real bug. The attached file (sample) opening with MS-Office 2010/2016 and LO Master, appeared with a semicolon separator. Balazs Varga committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/de73efb96fbb1d268caea0f41acbe20a234ec59f%5E%21 tdf#122226 OOXML Chart Import: data label new line separator 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. and Balazs Varga committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/42fd10b0ab6c6f65ba6394f9ae216c0f13973221%5E%21 Related: tdf#122226 OOXML Chart Import data label separator 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.