Bug 54328 (Marcin) - Automatic table of contents heading numbering problem
Summary: Automatic table of contents heading numbering problem
Status: RESOLVED INVALID
Alias: Marcin
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.4 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-31 15:27 UTC by Marcin
Modified: 2013-10-25 16:18 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcin 2012-08-31 15:27:00 UTC
When I create table of contents, it works well, until I have more than 9 headings in numbering 1 (99 in numbering 2) then all the heading content is positioned right and so it looks like:

8. Heading.............................1
9. Heading.............................1
10..............................Heading1

same thing happens, when I pass the limit of 100 in numbering 2:

98 Heading.............................1
99 Heading.............................1
100.............................Heading1

Is there already a solution for this in the newest packages?

I am using Ubuntu 12.04 upgraded directly from 11.10 and have all updates applied.
Comment 1 Jean-Baptiste Faure 2012-09-10 17:36:23 UTC
I guess you have a problem with the position of a tab stop just after the numbering.

Best regards. JBF
Comment 2 Marcin 2012-09-26 21:48:05 UTC
It's not me, who have the problem, since it's the automatic TOC, that is generated by LO. I would know how to fix it on my own, but then the automatic table of contents become manual, and that's not what I expect.
Comment 3 Jorendc 2012-12-30 18:11:27 UTC
Can't reproduce this using 

Mac OSX 10.8.2
LibreOffice 4.0.0.0.beta2 (Bouw-id: 4104d660979c57e1160b5135634f732918460a0)
TinderBox: MacOSX TDF Release, Branch:libreoffice-4-0, Time: 2012-12-18_17:13:13

and Ubuntu 12.10
LibreOffice 3.5.0 (build id: d6cde02) and master 4.1 (build it by myself).

Can you please retest with a newer LibreOffice version (3.6 branch, or even the newer LO 4.0 beta's).

If you still can reproduce: can you please add the file you created in attachment (I tried reproducing this by myself).

Kind regards and thanks in advance,
Joren
Comment 4 QA Administrators 2013-09-24 01:58:48 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 5 QA Administrators 2013-10-25 15:19:46 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO
Comment 6 QA Administrators 2013-10-25 16:18:40 UTC
Apologies - these were accidentally set to FIXED instead of INVALID - sorry for the noise