quarto-dev / quarto-dev/quarto-cli

Latex: Possiblity to remove 'Appendices' part title in table of contents

Open
#1,096 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

books enhancement latex
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

Discussed in https://github.com/quarto-dev/quarto-cli/discussions/1086

Originally posted by fitzchivalrik June 7, 2022
I am in the process of porting my latex template for my thesis to quarto, using the book template.
When using appendices in the book yaml, quarto inserts \addcontentsline{toc}{part}{Appendices} right after \appendix.
Unfortunately, this does not adhere to the style guide I need to use. It would be great if this was configurable (appendix-style: none does not seem to affect this).
Related, I think the produced hyperlink is incorrect, as clicking on Appendices in the toc in the PDF moves to the section before the first appendix, however, I am unsure if this is not an error in my setup.

book:
  chapters:
    - index.qmd
  appendices: # <-
    - appendix/first.qmd

https://github.com/quarto-dev/quarto-cli/blob/5a889b6316be4abcde8b0c3c5d4e4c2f58e4bbd4/src/resources/filters/quarto-pre/book-numbering.lua#L26-L32

Thanks for the software and your work, having one code base to produce a beautiful book-website and PDF is really great.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in src/resources/filters/quarto-pre/book-numbering.lua, especially the linked appendix handling, and reproduce the book YAML example with a LaTeX/PDF build. Check how the injected Appendices TOC entry and its hyperlink are generated. Done means the entry can be omitted through a configurable option and the resulting link behavior is correct.

Written by the indexing model from the issue text.

Assessment

Tech stack
latex, lua
Domain
tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.