When saving a calc document leading tabstops inside cells are lost. How to reproduce: 1. New document 2. Insert large portion of e.g. python code into one cell 3. Save the document 4. Reload the document Now all leading tabstops are gone... Michael
Please attach a sample document and then set it to UNCONFIRMED.
Created attachment 128691 [details] Demo file
Created attachment 128692 [details] Demo text with tabs
Created testcase. Not only the leading tabs are lost, ALL tabs are missing after saving/re-opening.
Confirmed in - Version: 5.3.0.0.alpha1+ Build ID: 757a60d01dd152aadab2ba3c8224252481ce8a88 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2; Layout Engine: new; Locale: ca-ES (ca_ES.UTF-8); Calc: group - Version: 4.2.0.0.alpha1+ Build ID: fc8f44e82de4ebdd50ac5fbb9207cd1a59a927e3 - Version: 4.1.0.0.alpha1+ Build ID: a2c9d4f8bbde97f175bae4df771273a61251f40 But not in Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
it looks this issue was introduced in range https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=7b384313399ee8199cd7241527c3dbc1d50694a2..9e15d9e76d1fd542378a997e27175ca98dd3e558 where there're some commits made by Kohei Yoshida so probably one of those is the responsable.
Comment on attachment 128691 [details] Demo file The test file is useless. There are no tabs in the file.
You should have read the instruction inside the file, cell C6. There is also an explanation why there are no tabs in the file: Due to the bug! So please follow the instructions, insert some tabs (the second attachment) and save&reload the file. And yes - it's quite useless as a working testcase... but someone asked for some testcase. So the "testcase" gives some instructions to make it work.
*** Bug 98815 has been marked as a duplicate of this bug. ***
Another way to reproduce it: https://bugs.documentfoundation.org/show_bug.cgi?id=98815#c0
*** Bug 106350 has been marked as a duplicate of this bug. ***
*** Bug 119056 has been marked as a duplicate of this bug. ***
Dear michael.letzgus, 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
Still reproducible. Version: 6.4.0.0.alpha0+ (x64) Build-ID: 41cd3e8e817c8c33a13608e62eeb06ce2c6977e4 CPU-Threads: 12; BS: Windows 10.0; UI-Render: GL; VCL: win; TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2019-09-01_22:04:10 Gebietsschema: de-AT (de_AT); UI-Sprache: de-DE
Created attachment 153848 [details] Spreadsheet example w/ instructions in cell A1 Follow instructions in this .ODS spreadsheet in cell A1 to be able to reproduce the issue. Use of an outside editor - like LeafPad or vim - is also needed.
Example per comment 15 - "TabTest.ods" - was tested with Version: 6.2.6.2 Build ID: 6.2.6.2-2.fc30
Dear michael.letzgus, 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
Regression still reproducible. Version: 7.3.5.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-GB (en_US.UTF-8); UI: en-US 7.3.5-1 Calc: threaded
Created attachment 182348 [details] TabTestRT71.ods: used this to bibisect FILEOPEN - same commit range found repro 7.5+ I got the same bibisect-41max results as Xisco: https://cgit.freedesktop.org/libreoffice/core/log/?id=84fefd7c295fc05499ca222dff50c2fe4e0fb27e&qt=range&q=7b384313399ee8199cd7241527c3dbc1d50694a2..ca4cbae35630cc314d33cc7ad9bea36063097fa5 This affects both file-open and file-save AFAICS.
FILEOPEN is the problem in 4.1. The tab is an XML property <text:p> <text:tab/> This line should have ONE leading tab </text:p> Proposed import fix at http://gerrit.libreoffice.org/c/core/+/139757 FILESAVE breaks in 4.2 with commit 882bee5ede38b6ed4e1ec870d835546868c6586d Author: Kohei Yoshida on Sat Aug 24 23:24:13 2013 -0400 tdf#60740: Export edit cells to ods without using UNO API.
display tabs is really hit or miss. 1.) if just normal text (not editeng), then tabs not seen (except when editing) 2.) if multi-line (automatically editeng), then it looks ok 3.) except on a round-trip, when importing the tab-less office:string-value causes editeng display issues somehow. simple round-trip (for editeng text) fix is at http://gerrit.libreoffice.org/c/core/+/139761
(In reply to Justin L from comment #21) > 3.) except on a round-trip, when importing the tab-less office:string-value > causes editeng display issues somehow. For this particular string (with \x001 instead of \x9), the fix for 70275 looks like a regression...
*** Bug 117001 has been marked as a duplicate of this bug. ***
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/690a35680adad07c4ab79d82cd1531bb82fe4bc1 tdf#103829 ods import: parse <text:tab/> It will be available in 7.5.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.
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/a7589f621fcbe6305335730d2dd86b9230a18594 tdf#103829 ods export: output <text:tab/> when CELLTYPE_EDIT It will be available in 7.5.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.
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/eab9015d1e17950ee5a49f93a6ad40e7726f5050 tdf#103829 ods export: don't output invalid office:string-value It will be available in 7.5.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.
Confirmed duplicate bugs are also fixed. -bug 106350 with TabTest.xls and TabTest.ods -bug 117001 with Text_to_Columns.ods and Text_to_Columns._test_tabs_from_scratch.ods
*** Bug 114398 has been marked as a duplicate of this bug. ***