Created attachment 87271 [details] test_file.ods with damaged cell A1 Problem description: Steps to reproduce: 1. set data format /@ in cell A1 2. type >, press enter, it looks like /> 3. save file 4. open saved file Current behavior: After opening saved file there is //> in cell A1 Expected behavior: After opening saved file I expect /> in cell A1 Operating System: All Version: 4.1.1.2 release
Thanks for the report! I can confirm this for 4.1.2.2 on Ubuntu 13.04. It works in the 4.0 series (tested in 4.0.4) - marking as regression. Importance increased to critical due to a data loss.
Seems that any text around @ format is added to cell content when the file is reloaded, but if the file is saved without changes doesn't happen. A really hard issue. Added to MAB for 4.1
*** Bug 70344 has been marked as a duplicate of this bug. ***
It is an import problem in xmlcelli.cxx. We import string-value which is the formatted string as original string. I think it is the result of some preformance work to avoid using editengine in simple text import. I need to think about a solution to use the normal string without editengine.
Ok fixed it. We somehow switched the formatted and original string.
Markus Mohrhard committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=591827c9ad0bec8b608bec63942aa7daf87dc5a0 fix cell text and unformatted cell text correctly, fdo#70275 The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://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": http://cgit.freedesktop.org/libreoffice/core/commit/?id=17d8e1f9eacb10654f2feb31df2fe0638af2b370 add test for fdo#70275 The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
This is an anoying critical bug, so why not push it to 4.1 series (4.1.4)?
*** Bug 69299 has been marked as a duplicate of this bug. ***
*** Bug 72252 has been marked as a duplicate of this bug. ***
*** Bug 72891 has been marked as a duplicate of this bug. ***
*** Bug 73305 has been marked as a duplicate of this bug. ***
I agree with comment#8. Please could this be applied to 4.1
4.2 is due end of january, so not too far away...
A fix pending review for 4-1 at https://gerrit.libreoffice.org/7555 for 4-1-5 at https://gerrit.libreoffice.org/7556
Eike Rathke committed a patch related to this issue. It has been pushed to "libreoffice-4-1": http://cgit.freedesktop.org/libreoffice/core/commit/?id=70c61a549184cf8611f7890ac31b0ba4c460cdec&h=libreoffice-4-1 resolved fdo#70275 write correct office:string-value if text format applied It will be available in LibreOffice 4.1.6. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Eike Rathke committed a patch related to this issue. It has been pushed to "libreoffice-4-1-5": http://cgit.freedesktop.org/libreoffice/core/commit/?id=68a753b6a36560eb83ba6ebe4fe9897a8759d265&h=libreoffice-4-1-5 resolved fdo#70275 write correct office:string-value if text format applied It will be available already in LibreOffice 4.1.5. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.