Created attachment 69117 [details] Sample document with bug in action Problem description: The rightmost tabulator in the left colunm of a two-column-design TOC is formatted incorrectly. This appears to happen on even-numbered pages only, even though all pages are set to the standard page style. I supplied a sample file with a TOC. Additionally I provided two images that compare formatting between even-numbered and odd-numbered pages.
Created attachment 69118 [details] Image of how the TOC is formatted on even-numbered pages
Created attachment 69119 [details] Image of how the TOC is formatted on odd-numbered pages
I originally posted this bug on the openoffice.org forum: http://forum.openoffice.org/en/forum/viewtopic.php?f=7&t=57002
This might be related to this bug in OOo: https://issues.apache.org/ooo/show_bug.cgi?id=29920
Created attachment 69162 [details] Sample document with bug in action
Created attachment 69163 [details] Sample document showcasing the effect of hanging indents There seems to be a connection to hanging indents as enabling them causes the rightmost tab to disappear on all columns and pages. I attached a sample file with this effect in action.
Created attachment 69297 [details] Sample document based an a stock template showcasing the same bug
I have had a play around with this, after seeing it on the LO forum and can confirm the problem, both the the sample file and one I created for myself. (on LO 3.5.6 Fedora 17) I have just tested the example file on 3.5.7 and it shows the same behaviour
Confirmed with: LO 4.0.0.3 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit Sample file's TOC rendered differently on even and odd pages (as on attached pictures by reporter).
Hi everyone. I need this bug/feature so much that I'm willing to pay 20.00 bucks for it. This offer is registered at FreedomSponsors (http://www.freedomsponsors.org/core/issue/247/formatting-table-of-contents-tabulator-formatted-incorrectly-in-left-columns). Once you solve it (according to the acceptance criteria described there), just create a FreedomSponsors account and mark it as resolved (oh, you'll need a Paypal account too) I'll then check it out and will gladly pay up! If anyone else would like to throw in a few bucks to elevate the priority on this issue, feel free to do so!
These dots in the TOC are one Tabstop formatted with dots. Here the tabstops are generated: http://opengrok.libreoffice.org/xref/core/sw/source/core/doc/doctxm.cxx#1617 They are generated correctly, I just debugged this function. aToken has the right cTabFillChar etc, it's no difference to the other ones which are correctly displayed. Don't know where the right place is to look at this.
** 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 (4.4.1.2 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) Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-03-03
(In reply to Glutanimate from comment #7) > Created attachment 69297 [details] > Sample document based an a stock template showcasing the same bug Confirmed. Win 7 Pro 64-bit, LibO Version: 4.4.1.2 Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432 Locale: fi_FI
The content of attachment 69117 [details] has been deleted for the following reason: creator request
** 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
Created attachment 153918 [details] Sample document with ToC edited
I don't see the point of this bug. Is it to ask a solution for this attached Sample document from attachment 69162 [details] or report a general bug (but there's no steps and Expected/Experienced results)? Now with LO 6.4+, attached Sample document was also wrong. I also attached an edited ODT with corrected ToC that looks fine to me. Generated ToC is also fine, so I don't know what led to bug. I reported or edited a number of ToC bugs like Bug 118960, bug 118962, bug 32360, bug 114773. I hope this one is covered by them, so I'll close. If I'm wrong, feel free to set back to New and explain what's at stake here that is not covered by others.