Created attachment 114195 [details] screenshot image of a data validity cell before and after saving in .xlsx format. Data validity error when saving decimal number to .xlsx format Error when sawing a spreadsheet in .xlsx -format. If write to data validity: 1,5 ; after saving in in MS - EXCEL .xlsx format, it looks : 1 5 Have as attachment a -.jpg screenshot image. In this image on the right side how it looks before saving and on the left side of this same image, how it looks, when re open this .xlsx
I can confirm with Version: 4.5.0.0.alpha0+ Build ID: e3167924fd28c8b854f23139dbf49f53e6282ef7 TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-03-17_03:10:47 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 on a currently supported version of LibreOffice (5.0.5 or 5.1.2 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
Created attachment 124401 [details] Bug DEMO table In use.: UBUNTU LINUX, version 15.10. LibreOffice: Version: 5.0.5.2 Build ID: 1:5.0.5~rc2-0ubuntu2
*** Bug 93122 has been marked as a duplicate of this bug. ***
Ubuntu 16.10 LibreOffice Version: 5.2.2.2 Bug: translation from .ods to .xlsx
Old bug. Still exists! I have Ubuntu 16.10 and LibreOffice Version: 5.2.2.2 Bug: When i save a file from .ods to .xlsx, data validation list with decimal numbers understand's as new line. Attachements: validity-bug.ods and validity-bug.xlsx
Created attachment 130920 [details] Data validation error when saving .ods to .xlsx format
*** Bug 102368 has been marked as a duplicate of this bug. ***
** 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
Dear Paavo Ingalsuo, 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 https://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
bug still present in actual 7.1.0.0 dev (winx64), imho a 'locale evaluation' problem, ex$el (2010) is funny, accepts 1.5 instead of 1,5 , but shows as '1. Mai' in the dropdown list after entering 1.5 somewhere else in the sheet, but calc has it's own problems, as mentioned by OP after saving in xlsx format and reopening decimal fractions are interpreted 'comma separated' in the dropdown, in 7.1 the dropdown doesn't stay on screen after a touchpad tab, but flashes short and disappears, it's neccessary to hold the mouse button down while hovering to the list item,
Created attachment 166155 [details] The example file saved by LO 7.1alpha - still bad
Created attachment 166156 [details] The Calc-saved example manually fixed up and saved in Excel
Created attachment 166157 [details] The original file in Calc and the fixed up xlsx in Excel It should be possible to correctly save this in xlsx.
@Tibor Nagy I thought you might be interested in this one...
Tibor Nagy committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/699372466384113cf015be714e0067e857f8fa5c tdf#90104 XLSX export: fix commas in data validation list It will be available in 7.1.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.
Can this issue also be solved for LO 7.03?
looks good now :-) thanks for fixing @Tibor Nagy (didn't do extensive test, and only win7x64, thus more tests and comments appreciated ...) backport planned? ver. 6? ver. 7?
(In reply to VLB from comment #17) > Can this issue also be solved for LO 7.03.1? I have test in LO 7.0.3.1 and it didn't work here.
Verified in: Version: 7.1.0.0.alpha1+ (x64) Build ID: 72056f39e01e36afac36c62988331b6813c8214f CPU threads: 4; OS: Windows 10.0 Build 17134; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: hu-HU Calc: threaded Thanks for fixing!