Created attachment 58668 [details] Original file, correct. Created using openoffice 3.3 first of all, this bug may be related to https://www.libreoffice.org/bugzilla/show_bug.cgi?id=32672, but it's a little different. Saving a .dbf file changes the columns datatype. Trailing decimals are ALWAYS added. There is no way to stop this. I tried saving in different charsets, changing the spreadshell cell format to whole numbers before saving, etc. Two trailing decimals are always added. I.E. COLUMN,N,5,0 becomes COLUMN,N,7,2 and 1995 becomes 1995,00 This bug did not occur in Openoffice between March 2009 up to Version 3.3(including) The reformatting seems to occure during filesave, not during opening the modified file.: Opening a saved file and saving it again leads to a binary identical (modified) file.
Created attachment 58669 [details] same file, saved by libreoffice. Column data structure has been modified. (File is Iso-8859-15 or winlatin1)
Please do not use https://www.libreoffice.org/bugzilla/*, use https://bugs.freedesktop.org/* URLs instead.. Thanks Florian R.
*** Bug 33511 has been marked as a duplicate of this bug. ***
I do not open first attachment file from Calc - General InOut error. Also do not save furst example from Bug 33511 - General InOut error. Os: Kubuntu 12.04 with last LO from Kubuntu repositories: LibreOffice 3.5.4.2 350m1(Build:2)
> I do not open first attachment file from Calc - General InOut error. > Also do not save furst example from Bug 33511 - General InOut error. It works OK for me (on Arch). Maybe try again?
Ho lo stesso problema. I campi numerici non conservano il formato originale. agiucar
This looks like a DUP of bug 32672 to me, since the output header becomes the same as the one mentioned in that report. Adding Kohei to CC. Alex
(This is an automated message.) LibreOffice development currently prioritizes bugs with the so called MAB (most annoying bugs) -- as this bug has not run through that process (including writing a short rationale for this bug being a candidate and other who are watching the tracker bug silently approving that rationale etc.) its priority is set to high. Note this is effectively no change in the urgency assigned to this bug, as we are currently not making a difference between high and highest and severity is untouched. You can find out more about MABs and how the process works by contacting libreoffice qa on irc: http://webchat.freenode.net/?channels=libreoffice-qa The QA wiki page also gives you hints on how to get in contact with the team (if IRC fails you, your next best choice is the mailing list): https://wiki.documentfoundation.org/QA
** 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 (4.4.2 or later) 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: 2015-05-02
** 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.1.5 or 5.2.1 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-20160920
Following Alex's comment, any better with recent LO version? (last stable one is 5.3.3). On pc Debian x86-64 with master sources updated yesterday, I don't reproduce this. (perhaps I missed something?)
Symptoms described are indeed the same as tdf#32672. If I'm wrong and someone still reproduces this with a recent LO version (5.2.7 or 5.3.3), don't hesitate to reopen this tracker. *** This bug has been marked as a duplicate of bug 32672 ***