Steps to reproduce: (1) Open new text document. (2) Define left tab position somewhere in the right half of the working area. (3) Format page with 2 columns. The tab position is still displayed in the ruler in the right half !!! It seems that this tab position belongs to the right column, but it does not. Expected: No display of tab position. But this is not the important thing. (4) Insert a word (left column). (5) Insert a manual column break. Cursor jumps to the beginning of the right column. The tab is no longer displayed, so far so good. (By the way: The column break is now only displayed with a blue line, the string „Manual Column Break“ is not displayed yet. But this is even less unimportant.) (6) Insert a word at the beginning of the right column. (7) Define a tab position in the right column. Then display tabs (Format > Paragraph > Tabs). 2 tab positions are defined, one inside the column margins, one outside (not displayed). (8) Save document as MS Word document (.doc) and close document. (9) Open document again. The cursor is in left column. One tab of left column is displayed at the right side. This is equal to step (3). (10) Set cursor in right column after the word. Two tabs positions are displayed, one on the right, one on the left side of the page. (11) Insert a tab. The cursor jumps to a new position, but this is not the position of the displayed tab position !!!! If you now look to the columns, to the tab positions and to the cursor position, you can recognize, that the distance between the left margin of the left column and the tab position at the left column is equal to the distance between the left margin of the right column and the cursor position. That means, that the calculation for the display of the tab positions is wrong. It has been forgotten to consider an offset for the width of a column. Operating System: Windows 7
Thanks for submitting this bug! I can reproduce this bug. (5) The string 'Manual Column Break' isn't displayed when you add it. But when I do step (7) and close the Paragraph Format window, The text is now displayed correctly (I have Dutch helppack installed). Mac OS X 10.8.2 LO 3.6.4.3 and LO Version 4.0.0.0.beta1 (Build-id: 87906242e87d3ddb2ba9827818f2d1416d80cc7) TinderBox: MacOSX TDF Release, Branch:libreoffice-4-0, Time: 2012-12-05_22:13:37 Both with Dutch helppack
I tryed with a new document and it works well, no problem, but after saving as DOC, then the BUG occurs! I'm using LibreOffice Writer 4.2.2.1 at Windows 7.
** 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.0.5 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-09-03
Bug still exists in version 5.0.1 with Win7.
** 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
Tested again with versions 5.0.1 and 5.2.2 with original test procedure: ... Step (3): Against my original statement the display of the tab in the right half is correct, because the numbering of the ruler in the right half also refers to the left column. What's irritating is the 'white' ruler background of the right column. It seems that this part of the ruler refers to the right column. I think that only the ruler background of the column where the cursor is positioned should be white. The background(s) of the other column(s) should be greyed like the backgrounds beyond the page margins. Perhaps also a lighter grey may be suitable. ... Step (5): With version 5.0.1 a blue line above the right column is displayed, with 5.2.2 the line is not displayed. It's only displayed if Non-printing Characters are displayed. To my opinion the version 5.2.2 is correct now. Not correct is, that the term "Manual Column Break" is not displayed above the blue line. You have to scroll the page down and up again, then the term is displayed. ... Step (10): In version 5.0.1 two tabs are displayed, in 5.2.2 only one is displayed. I think the version 5.2.2 is correct now. Step (11): Contrary to version 5.0.1 with version 5.2.2 the cursor now jumps to the correct tab position. Conclusion: Main problem is solved in version 5.2.2. Two minor problems still exist (step 3 and 5).
** 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 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
Regarding the two minor problems mentioned in comment 6 I wrote 2 new bug reports: Bug 114541, bug 114553. Hence the main problem is is no longer present (see also comment 6), this bug can be set to WORKSFORME.