When a document is saved as Word 2003 and closed and reopened, the tab setting in a table cell (except for the first column) will be impossible to manage by drag-and-drop tab marks on the ruler. This problem will still persist even when the document is saved as ODT. How to reproduce the problem: 1. Create a new Writer document. 2. Create a table of 2 columns. 3. Type "A", tab, "B", tab, and "C" in the cell on the 2nd column. 4. Put tab marks at 1cm and 2cm on the ruler for the text you just typed. You'll see the tab marks on the ruler above the 2nd column. 5. Save the document as Word 2003. 6. Close the document. 7. Reopen the document. 8. You'll see the tab marks on the ruler above the 1st column instead of the 2nd. The tab setting is now broken and cannot be managed using drag-and-drop. Even though you save this document as ODT, close it, and reopen it, this tab problem will still persist. Current behavior: The tab marks on the ruler appear above the first column only, no matter which column is being worked on. Expected behavior: The tab marks on the ruler should appear above the column in which the cursor is.
Hi preechaw, There are a few gaps in my libreoffice knowledge :( and I am not not sure about steps 3 & 4. How to you put the tab marks into the column? Cheers
this one is stalled. Any comments/advice?
Reproduced. Preechaw: for completeness's sake what operating system were you using? Tim: in step 3, use ctrl-tab to avoid advancing in the cells. For step 4, go to the beginning of the a b c and simply click on the ruler above to set those "90 degree angle" marks. Win 7 64-bit Version: 4.4.0.0.alpha2+ Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827 TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08 Ubuntu 14.10 64-bit Version: 4.4.0.0.alpha2+ Build ID: 3cf226622a3d8c09d655034dbcc81695f1662b87 TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2014-11-15_23:24:22
thanks for the info Beluga. FWIW Problem recreated in F21 Version: 4.4.0.0.alpha2+ Build ID: b7c4c78a097f76314982d8c1a9f2e58df95080a1 TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2014-11-11_01:59:1
** 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.4 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 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-12-20
** 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.6 or 5.2.3 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-20170103
If I understand this bug well, seems OK now. test 6.4+.