https://bugs.documentfoundation.org/show_bug.cgi?id=162916

Justin L <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|4.3.7.2 release             |Inherited From OOo
           Keywords|bisected, regression        |
      Regression By|Michael Stahl               |

--- Comment #3 from Justin L <[email protected]> ---
The bibisect situation is a lot more complex than comment 1 suggests. 

In 4.2 the file loaded with the page numbers showing, until
    commit d6e321f8264188ce8371c060ebeb75b213f0c90f
    Author: Noel Grandin on Fri Oct 18 09:59:22 2013 +0200
        convert sw/source/core/doc/*.cxx from String to OUString

That commit can hardly be called a "fix" for TOC numbering, and was
specifically reverted by mstahl in 4.3 as referenced by comment 1. Note that
this fix returned the page numbers AT LOAD TIME - so it can hardly be called
the regression of this bug report.

The load time numbering was probably eliminated later in 4.3 with
commit 9679e9c23216decb5f9f25f85b04cb3f25211111
Vinaya Mandke <[email protected]> on Mon Dec 30 16:22 2013
    fdo#69649 Fix for pre-rendered Table Of Contents
    Reviewed on: https://gerrit.libreoffice.org/7207

I suspect that Vinaya's patch just renders the
last-seen-view-of-the-field-as-recorded-in-the-document instead of rendering an
updated TOC.

In other words I'm sure this has never worked. I expect that LO simply doesn't
have the ability to display the TOC without page numbers, making this an
enhancement request.

DomainMapper_Impl.cxx's handleToc for \n has "todo: what does the description
mean?"

-----

The TOC field can have an \n field-argument "Without field-argument, omits page
numbers from the table of contents. Page numbers are omitted from all levels
unless a range of entry levels is specified by text in this switch's
field-argument. A range is specified as for \l."

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to