Tables¶
A note with latex-env: table and a caption: becomes a numbered, referencable table. Two layouts: the default fits wide tables onto one page (auto-shrunk, no column overflow), longtable: true breaks long tables across pages with a repeating header. align: left switches from centered placement.
Source notes
---
title: "Feature: Tables"
author: MrIwan
notitlepage: true
toc: false
---
# Tables
![[tables-test]]
![[table-large]]
As shown in [[table-large]].
![[table-large-longtable]]
As shown in [[table-large-longtable]].
---
title: Table Numbering Test
author: Obsi Print
abstract: Tests the latex-env table feature. Tables from atomic notes with `caption:` in the frontmatter are embedded as numbered floats; [[Note]] links reference them as "Table N".
---
# Table Numbering Test
This document tests how tables from atomic notes are embedded as numbered floats. Convention: a single-source caption — the caption lives in the table note's frontmatter as `caption: "…"`. There is no pipe override in the embed tag and no Pandoc native-caption fallback.
# First Table
Source note `Table-Comparison.md` has `latex-env: table` and `caption: "Comparison of implementation variants"` in the frontmatter.
![[table-comparison]]
As [[table-comparison]] shows, variant B is superior on several dimensions. The reference also works with custom text — for example [[table-comparison|here]] — and stays clickable as a hyperref.
# Second Table
Demonstrates the counter increment (should become "Table 2"):
![[table-project-phases]]
See [[table-project-phases]] for the rough timeline.
[[Table-Does-Not-Exist]]
---
latex-env: table
caption: "Comparison of implementation variants"
---
| Criterion | Variant A | Variant B |
|--------------------|-----------|-----------|
| Cost | low | high |
| Maintenance effort | medium | low |
| Scalability | limited | excellent |
---
latex-env: table
caption: "Example table (longtable on)"
longtable: true
---
| No. | Component | Owner | Status | Priority | Effort | Risk | Description |
| --- | ---------- | --------- | ----------- | -------- | ------ | ------ | ------------------------------------ |
| 1 | Requirements | A. Meier | open | high | 2 d | low | Capture the functional requirements. |
| 2 | Architecture | B. Schulz | in progress | medium | 5 d | medium | Align with the stakeholders. |
| 3 | Data model | C. Roth | done | low | 8 d | high | Assess potential technical risks. |
| 4 | Backend | D. Kern | blocked | high | 13 d | low | Implementation including unit tests. |
| 5 | Frontend | E. Lang | in review | medium | 3 d | medium | Reviewed by two developers. |
| 6 | Interface | F. Vogt | open | low | 2 d | high | Integrate against third-party systems. |
| 7 | Test | A. Meier | in progress | high | 5 d | low | Capture the functional requirements. |
| 8 | Deployment | B. Schulz | done | medium | 8 d | medium | Align with the stakeholders. |
| 9 | Monitoring | C. Roth | blocked | low | 13 d | high | Assess potential technical risks. |
| 10 | Documentation| D. Kern | in review | high | 3 d | low | Implementation including unit tests. |
| 11 | Security | E. Lang | open | medium | 2 d | medium | Reviewed by two developers. |
| 12 | Release | F. Vogt | in progress | low | 5 d | high | Integrate against third-party systems. |