Description: The hex strings "_x000D_" get shown inside Calc cells. They should be converted and treated as an special character "\r". Steps to Reproduce: It's necessary to generate an Excel (XLSX; OOXML) file containing carriage return and newline characters inside the cells. It's not possible to generate directly with Excel, since it deletes the "\r" symbols. It's necessary to generate it with a library or to edit the "sheet1.xml" inside the OOXML file. I generated those XLSX file from a R-lang library: https://github.com/ropensci/writexl/issues/22 Actual Results: The hex string "_x000D_" gets shown inside the cells. Expected Results: It was expected to transform the hex string "_x000D_" to a real carriage return inside the cell. Or, at least, to delete the string "_x000D_". Reproducible: Always User Profile Reset: No Additional Info: It should check if there is a newline character "\n" just after the "_x000D_" string. And then delete the "_x000D_" string from the cell. If there is a "_x000D_" string without a "\n" after, it should transform it into a newline char.
Created attachment 143225 [details] screenshot
Created attachment 143226 [details] to reproduce the described error
Confirmed. Arch Linux 64-bit LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 Arch Linux 64-bit Version: 6.2.0.0.alpha0+ Build ID: bd394492c165d27c96a44495d9ca694a242acb8f CPU threads: 8; OS: Linux 4.17; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded Built on July 11th 2018
Dear Marcos F, 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
*** Bug 135311 has been marked as a duplicate of this bug. ***
*** Bug 138477 has been marked as a duplicate of this bug. ***
Dennis Francis committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/2d5ba784a341aea1b7b2403842d2521d1548ea8f tdf#118470: sc oox: recover escaped unicode chars in strings import It will be available in 7.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.
Dennis Francis committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/d1d6c1535e51ef364a71d3d4c5bd331af88fce32 tdf#118470: unit test for escaped unicode chars in strings import It will be available in 7.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.
follow-up bug 149477
Note: implementation has been replaced by oox::AttributeConversion::decodeXString() with commit 96965871f4cd2e4afbdf3bcae9dc0c43d1543e1d.