quarto-dev / quarto-dev/quarto-cli

Epic: Crossref Overhaul

Open
#4,944 18 comments 7 reactions 1 assignee View on GitHub

@cscheid is already working on this.

Since Mar 24, 2023.

  • #6620 by @cscheid — merged
crossref epic
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

ASAP

  • https://github.com/quarto-dev/quarto-cli/issues/8848
  • Customizable categories for Float and Block crossreferences
    • #1655
    • #3323
    • #3979
  • Add crossreferences to
    • floats (Tables, Figures, Listings, etc)
    • blocks
      • Callouts
      • Theorem environments
      • Proof environments
  • Allow fine-grained control over crossref label formatting
    • #1095
    • #1196
    • #1771
    • #2356
    • #2439
    • #3440
    • #4364
    • #4532
    • #5481
    • #5621
    • #5652
    • Improve treatment of compound crossreferences
      • #1706
      • #1707
  • Glossary support
    • #1697
  • Page number format control for page regions where collations (list of *) are put
    • #1889
  • Crossref collations (list of figures, tables, equations, etc) in non-PDF formats
    • #2138
  • Equation numbering, multiple refs in a single block, tags
    • #2275
    • #4136
  • Short caption support for all Float crossrefs
    • #3498
    • #4776
  • Niceties
    • #4938
  • Crossref, TOC, knit_child interactions
    • #3178
  • Book parts should be referenceable
    • #2571
    • #3234
  • Add crossreferences to
    • inlines (Equations, arbitrary spans, anchors from headings, etc)

Later

  • #4517
  • fig-* support: layout interaction, non-crossreferenced images
    • #2251
    • #3370
  • #8772

Uncategorized

Outstanding Tasks

  • Are we testing Epub crossrefs right now?
    • run output through epubcheck
  • Check the crossref label
  • Check the issues that refer to this
  • Consistency of CSS class names: "fig" vs "figure", etc.

Wontfix

Needs project overhaul (so will be worked on after that epic)

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.