Suppressing automatic promotion of deeper headings

Comments

3 comments

  • Avatar
    Thomas Rough (K15t)

    Hi Alessandro, 

    Thanks for your post. 

    Unfortunately, at the moment there is not an option that will prevent our heading algorithm from being used during the export process. As you are aware from the referenced document link, all our exporters use this algorithm to create a sensible hierarchy as Confluence does not enforce proper ordering of headings. 

    This means when Scroll PDF Exporter parses a tree of wiki pages it converts both the page hierarchy and the headings within a page into a hierarchical section and sets the highest level of heading on a page when it detects the first heading. In your use case, it means your heading 5's and 6's become level 3 headings. 

    Currently, we have an open improvement that pertains to introducing an option that will allow users to disable the algorithm. You can track this here: https://k15t.jira.com/browse/EXP-428. I would recommend signing up to our JIRA (via https://k15t.jira.com/secure/Dashboard.jspa) in order to watch, comment and/or vote on this issue.  You'll then receive a notification for every status update. 

    Cheers, Thomas (K15t Software) 

  • Avatar
    Alessandro Tondo

    I'm already watching that issue (which I've found only after asking this question).

    Thank you for the update, Thomas.

  • Avatar
    Michael Scholze

    I want to add to this topic and push the impotance of https://k15t.jira.com/browse/EXP-428 by saying that the promotion feature completely prevents usage of a "small" reusable document concept.

    I implemented the creation of subchapters with the PTC (PageTreeCreator) addon, which does the heading for me with predefined structures as I want them. The problem is, that the K15 Export algorithm pushes things on h1 level even with a SubPage category being neatly sorted. 

    In this case, this should be the levels as expected

    But instead, the 2nd Page Header gets L1 as well, breaking to a new page. The 2nd Heading (2) at level 3-5 is ignored alltogether. 

    I understand the concept behind this, especially when wild heading structures up to h6 are possible, but the algorithm should be configurable to stop the promotion at a certain heading level, e.g. h2 to allow for "room" for user configuration.

     

     

     

     

Please sign in to leave a comment.

Powered by Zendesk