New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

section.autolabel supported? #128

Open
adamretter opened this Issue Nov 29, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@adamretter
Copy link

adamretter commented Nov 29, 2018

Is section.autolabel still supported? I have it set to 1, but I am not getting numbered section titles, also I can't find it in the code base if I grep it...

@ndw

This comment has been minimized.

Copy link
Contributor

ndw commented Jan 8, 2019

It's supposed to be. I'm getting numbered sections in my files. What is section.autolabel.max.depth set to? I may have decided that having a flag and a max depth was overkill.

@adamretter

This comment has been minimized.

Copy link

adamretter commented Jan 8, 2019

Unfortunately that still doesn't work for me. I am running this basically:

$ java -jar /Users/aretter/code/docbook-xslt2-2.3.8-app/docbook-xslt2-2.3.8.jar \
        --format foprint \
        --params params.xproc \
        --postprocess fixup.xslt \
        --pdf output.pdf \
        task-abstraction-for-xpdls.xml

My params.xproc file:

<param-set xmlns="http://www.w3.org/ns/xproc-step">
  <param name="paper.type" value="A4"/>
  <param name="column.count.titlepage" value="1"/>
  <param name="column.count.body" value="2"/>
  <param name="component.titlepage.properties" value="span='all'"/>
  <param name="section.autolabel" value="1"/>
  <param name="section.autolabel.max.depth" value="4"/>
  <param name="section.label.includes.component.label" value="1"/>
  <param name="bibliography.numbered" value="1"/>
  <param name="book.titlepage.recto.style.color" value="#E0E0E0"/>
</param-set>
@kosek

This comment has been minimized.

Copy link
Contributor

kosek commented Jan 8, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment