@heroiclands/package-build 23.12.4 → 23.12.6

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # @heroiclands/package-build
 
+## 23.12.6
+
+### Patch Changes
+
+A package can name a default calendar with `defaultCalendar` in its configuration, and it replaces the world note's calendar as the one dates fall back to.
+
+A note's dates print in its own `data.calendar`, which any note may now set, else its culture's, else for a place its parents', else the default. A place whose parents keep different calendars is a build error until it names its own.
+
+Chronologies and the other event sections print every date in the calendar of the page showing them, and `dateformat` with no calendar named uses the note's.
+
+## 23.12.5
+
+### Patch Changes
+
+In PDF books, the page number and section name at the foot of each page are set at the size of the body text.
+
+In PDF books, list items sit apart from one another and carry a bullet large enough to see at book size.
+
+In PDF books, a reference to another book that already sits in brackets joins them, reading (The Crossing, Thal. p524) rather than nesting a second pair.
+
+Chronology sections, and the other event sections, list each event's date first, written in the setting's calendar. A chronology shows its Felt here column only when some event is felt in the place, and prints across the full page in PDF books. A captioned table can ask to span the page in a PDF book with `.full-width`. A wide table floats to where it fits, and the text runs on past its heading rather than leaving an empty page.
+
+In PDF books, a profile box too long for the rest of a page continues on the next one between its rows, instead of running off the page over the footer.
+
+A note's name may give a `sort` form, the way an index would write it: `sort: Black Flame, The` for _The Black Flame_, or `sort: Hilvan, Doran`. It files the note in the book index, page lists and other name-ordered lists, and it is the note's entry text in the book index; every other list still shows the full name. Authored `sql` fences can order by the new `nameSort` column of `entries`, which is the `sort` form or, without one, the full name.
+
+Profile figures read as numbers do: 12,500 under a million, and 11 million or 1.2 million above it, on the website, in Foundry and in PDF books.
+
 ## 23.12.4
 
 ### Patch Changes

package/content-config.mjs

@@ -571,6 +571,10 @@ export function publishesContentPages(config) {
  *                                          resolved against it, so the build never
  *                                          depends on the working directory.
  * @property {string} [currentDate] Setting-wide neutral current date; defaults to "720.1".
+ * @property {string} [defaultCalendar]     Shortcode of the `lore` note with
+ *                                          `subType: calendar` that prints the
+ *                                          dates of a note no other rule gives a
+ *                                          calendar.
  * @property {string} contentPackage        Content package name — the address
  *                                          namespace every note in this
  *                                          repository is published under.
@@ -646,6 +650,8 @@ export function publishesContentPages(config) {
  *
  * @typedef {object} ContentBuildConfig
  * @property {string} currentDate Setting-wide neutral current date.
+ * @property {string|null} defaultCalendar The calendar of last resort's
+ *                                     shortcode, `null` when none is named.
  * @property {string} rootDir
  * @property {string} contentPackage
  * @property {string|null} foundryPackage  `null` for a `documentation`
@@ -730,6 +736,7 @@ const CONFIG_KEYS = [
     "rootDir",
     "contentPackage",
     "currentDate",
+    "defaultCalendar",
     "foundryPackage",
     "homepage",
     "authors",
@@ -912,6 +919,24 @@ function fail(field, problem) {
     throw Object.assign(new TypeError(`package-build config: \`${field}\` ${problem}.`), { field });
 }
 
+/**
+ * The configured `defaultCalendar`: a calendar note's shortcode, or `null`.
+ * Whether it names a calendar note is checked against the content tree when
+ * the content index is built.
+ *
+ * @param {unknown} value - The configured value.
+ * @returns {string|null} The shortcode.
+ */
+function normalizeDefaultCalendar(value) {
+    if (value === undefined || value === null) return null;
+    if (typeof value !== "string" || !isAddressSegment(value))
+        fail(
+            "defaultCalendar",
+            "must be the shortcode of a calendar note — lowercase letters and digits",
+        );
+    return /** @type {string} */ (value);
+}
+
 /**
  * @param {object} object
  * @param {readonly string[]} allowed
@@ -2973,6 +2998,7 @@ export function defineConfig(config) {
                 fail("currentDate", error.message);
             }
         })(),
+        defaultCalendar: normalizeDefaultCalendar(input.defaultCalendar),
         contentPackage: requireContentPackage(input.contentPackage, docEntryTypes, {
             rootDir,
             packageKind,

package/docs/api.md

@@ -384,6 +384,7 @@ The declared infobox: what a note's summary panel holds, decided once and render
 | `assertInfoboxSet`        | `assertInfoboxSet(boxes, fm, options)` | `readonly object[]`, throws | refusing a page that carries anything but the boxes its type maps to                   |
 | `buildInfoboxes`          | `buildInfoboxes(fm, options)`          | `object[]`                  | building every box a note carries, against a given set of maps and declarations        |
 | `defineInfobox`           | `defineInfobox(declaration)`           | `object`                    | declaring one system's half of the infobox                                             |
+| `formatQuantity`          | `formatQuantity(value)`                | `string`                    | writing a number as a profile shows it: `12,500` under a million, `11 million` above   |
 | `hasRenderableValue`      | `hasRenderableValue(kind, value)`      | `boolean`                   | deciding whether a built value is worth a row                                          |
 | `hasValue`                | `hasValue(value)`                      | `boolean`                   | deciding whether an authored value is worth a row                                      |
 | `humanizeFieldName`       | `humanizeFieldName(name)`              | `string`                    | turning a declared key into the label a reader sees                                    |
@@ -722,7 +723,7 @@ resolved value: the culture a place or affiliation inherits through
 
 ### `engine.markdownExpressions`
 
-`renderMarkdownExpressions(body, { fm, dates, sqlResults, figures, file, bodyLine })` expands scalar frontmatter references and registered Handlebars helpers outside Markdown code. The `dateformat` helper uses `formatDateInCalendar`; `gt`, `gte`, `lt`, `lte`, `eq`, `and`, `or`, and `not` evaluate explicit comparisons. The `sql` helper reads a prepared scalar result, which must contain one row and one column. The `ref` helper links to a captioned item by its anchor — `"#thorn"` on the same note — in `number` (the default, and admitted explicitly), `full` or `title` form; `figures` is a `Map` of this note's own figures, by id, to `{label, caption, hasCaption}`, and an address naming another note is reported as unresolved rather than looked up. `sqlQueriesInMarkdown` discovers SQL calls, including nested calls; `prepareInlineSqlExpressions` evaluates them through the same DuckDB connection as SQL tables. `EXPRESSION_HELPERS` is the one list of helpers: the engine registers from it and the authoring document is checked against it, so each name there carries the parameters it takes and a sentence on what it does. The renderer returns `{ markdown, findings }`, with source positions for invalid expressions. Site, Foundry and PDF passes invoke it after generated tables expand and before links resolve. Hugo shortcodes remain literal for the site renderer.
+`renderMarkdownExpressions(body, { fm, dates, sqlResults, figures, file, bodyLine })` expands scalar frontmatter references and registered Handlebars helpers outside Markdown code. The `dateformat` helper uses `formatDateInCalendar`, in the calendar it names or else the note's resolved calendar, which it reads from `dates.noteCalendars` — the map a reckoning context built over content-index records carries; `gt`, `gte`, `lt`, `lte`, `eq`, `and`, `or`, and `not` evaluate explicit comparisons. The `sql` helper reads a prepared scalar result, which must contain one row and one column. The `ref` helper links to a captioned item by its anchor — `"#thorn"` on the same note — in `number` (the default, and admitted explicitly), `full` or `title` form; `figures` is a `Map` of this note's own figures, by id, to `{label, caption, hasCaption}`, and an address naming another note is reported as unresolved rather than looked up. `sqlQueriesInMarkdown` discovers SQL calls, including nested calls; `prepareInlineSqlExpressions` evaluates them through the same DuckDB connection as SQL tables. `EXPRESSION_HELPERS` is the one list of helpers: the engine registers from it and the authoring document is checked against it, so each name there carries the parameters it takes and a sentence on what it does. The renderer returns `{ markdown, findings }`, with source positions for invalid expressions. Site, Foundry and PDF passes invoke it after generated tables expand and before links resolve. Hugo shortcodes remain literal for the site renderer.
 
 | Export                      | Signature                                  | Returns                | Use it when                                      |
 | --------------------------- | ------------------------------------------ | ---------------------- | ------------------------------------------------ |
@@ -735,10 +736,13 @@ resolved value: the culture a place or affiliation inherits through
 
 The corpus registry anchors each calendar's year 1, day 1 to its canonical `data.epoch` and maps every declared era to that calendar. Exactly one `start: null` era covers earlier years and counts backwards; exactly one `start: 1` era begins the forward count. Other starts are distinct positive calendar years. Numeric order determines bounds, irrespective of array order. Duplicate starts and markers, missing required eras, and invalid epochs are findings. Short qualifiers are ambiguous when they name eras in several packages; a full Address selects one.
 
-| Export                    | Signature                                     | Returns                                  | Use it when                                                 |
-| ------------------------- | --------------------------------------------- | ---------------------------------------- | ----------------------------------------------------------- |
-| `resolveReckoningMarkers` | `resolveReckoningMarkers(index, daysPerYear)` | `{eras, markers, findings}`              | resolving authored eras, their markers, and their bounds    |
-| `reckoningContext`        | `reckoningContext(index)`                     | `{eras, markers, daysPerYear, findings}` | sharing one resolved date context across checks on a corpus |
+| Export                    | Signature                                     | Returns                                                 | Use it when                                                                                           |
+| ------------------------- | --------------------------------------------- | ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
+| `resolveReckoningMarkers` | `resolveReckoningMarkers(index, daysPerYear)` | `{eras, markers, findings}`                             | resolving authored eras, their markers, and their bounds                                              |
+| `reckoningContext`        | `reckoningContext(index)`                     | `{eras, markers, daysPerYear, findings, noteCalendars}` | sharing one resolved date context across checks on a corpus                                           |
+| `noteCalendarMap`         | `noteCalendarMap(notes)`                      | `Map<string, string>`                                   | reading each record's `resolvedCalendar` by note, as `reckoningContext` carries it in `noteCalendars` |
+| `noteCalendarKey`         | `noteCalendarKey(fm)`                         | `string \| undefined`                                   | finding a note's entry in `noteCalendars` by its type and shortcode                                   |
+| `calendarAddress`         | `calendarAddress(value)`                      | `string \| undefined`                                   | reading a record's `resolvedCalendar`, tuple or string, as its canonical Address                      |
 
 ### `engine.calendarNotes`
 

package/docs/authoring/dates-and-calendars.md

@@ -84,7 +84,35 @@ package-build dateto commoncal 326.114 --format long
 
 The CLI `datefrom` command requires a day and reads the default (`std`, or first) pattern. `dateto` prints the era covering the canonical day. A clock time makes a date exact; a year or day without one spans the stated interval. `data.epoch` and `data.moon.newOn` require a day. The [detailed date rules](../reference/format-details.md#dates-and-calendars) describe precision and bounds.
 
-In prose, `{{dateformat "commoncal" data.born}}` prints a date in the chosen calendar. `{{dateformat data.calendar data.born}}` uses the note's calendar Address. A third argument chooses another named pattern. A being or place can set `data.calendar`; its infobox uses that calendar for dates.
+In prose, `{{dateformat "commoncal" data.born}}` prints a date in the chosen calendar, and `{{dateformat data.born}}` prints it in the note's own calendar. A last argument chooses another named pattern: `{{dateformat "commoncal" data.born "long"}}`, or `{{dateformat data.born "long"}}`.
+
+## Choose the calendar a note's dates print in
+
+Every note reads its dates in one calendar. The infobox's birth and death dates, `dateformat` with no calendar named, and every date in the event sections the build adds to the note's page all print in it. It is the first of:
+
+1. the note's own `data.calendar`, which any note may set and which always wins;
+2. its culture's calendar — the `data.calendar` of the culture note its `data.culture` names;
+3. for a place, its parents' calendar — the calendar each place in its `data.parents` reads in, by these same rules;
+4. the package's `defaultCalendar`, set in the [configuration](../configuration.md#defaultcalendar);
+5. otherwise none, and a date prints as it was written.
+
+```yaml
+# package-build.config.yaml
+defaultCalendar: commoncal
+```
+
+```yaml
+# A town in a province that keeps the Vylarian count
+type: place
+subType: settlement
+shortcode: brenford
+data:
+  parents: [vylaria]
+```
+
+Brenford names no calendar and no culture, so it reads in Vylaria's. A place whose parents read in **different** calendars is a build error at its `data.parents`, naming the place and each calendar; give the place its own `data.calendar` to settle it. A parent, or a culture, that only reaches the default counts for nothing, so a place among parents that all fall through to `defaultCalendar` takes the default without an error.
+
+An event section prints every date in the calendar of the page showing it, whichever note the event is written on: Brenford's chronology reads in Vylaria's count even where an event comes from a history kept in the common calendar. The [format reference](../reference/format-details.md#a-notes-calendar) gives the rules in full.
 
 ## Write a recurring date
 

package/docs/authoring/frontmatter.md

@@ -21,7 +21,7 @@ data: {}
 ---
 ```
 
-`name` is a map with a required, nonempty `full` display name. Every note may also use `aliases` for an ordered list of other names. The note infobox lists aliases directly beneath the full name. For a `being` with `subType: character`, `given` and `clan` are optional name components. The first alias of a character or NPC is its nickname. Omit optional keys when they do not apply; `given`, `clan`, and alias entries must be nonempty strings when present. No other keys are accepted under `name`.
+`name` is a map with a required, nonempty `full` display name. Every note may also use `aliases` for an ordered list of other names, and `sort` for the form the name takes in an index, such as `Black Flame, The` or `Hilvan, Doran`. The note infobox lists aliases directly beneath the full name. `sort` files the note wherever notes are ordered by name — the book index, page lists, generated lists of related notes, and the `nameSort` column of the `entries` relation — and is the note's entry text in the book index. Every other list still displays the `full` name. A note with no `sort` files and indexes by its `full` name. For `name: {full: The Black Flame, sort: "Black Flame, The"}`, the book index prints _Black Flame, The_ under **B**, and a page list prints _The Black Flame_ at the same place.
 
 `description` is the short page summary. `tags` hold draft state and descriptive labels. The note type's classification belongs in `subType` where it is declared. `data` holds facts about the subject shared by systems. A YAML comment is the place for an author-only note: commented values remain valid YAML but do not enter the content index or generated documents.
 

package/docs/authoring/links-and-markup.md

@@ -197,7 +197,7 @@ The caption attaches to exactly the next supported block:
 
 The optional `type` attribute overrides inference and accepts `figure`, `table`, `poetry`, `code`, `prose`, and `example`. `type=example` uses **Example 1**, **Example 2**, and so on. It does not allow an unsupported target. A heading, list, thematic break, another caption or end of document after a caption is an error. Caption markers without separating spaces or caption text are errors too.
 
-Identifiers are optional and must be unique within the note. Classes are unrestricted; `.border` uses the shared border style, while other classes can be styled by the medium. Named attributes use `key=value`, with quoted values for text containing spaces. Use `#id` and `.class` rather than `id=` and `class=`; event-handler attributes are refused.
+Identifiers are optional and must be unique within the note. Classes are unrestricted; `.border` uses the shared border style, while other classes can be styled by the medium. On a captioned table or SQL fence, `.full-width` sets the table across the page in a PDF book instead of in one column (`: Regional trade routes {.full-width}`); the other surfaces ignore it. Named attributes use `key=value`, with quoted values for text containing spaces. Use `#id` and `.class` rather than `id=` and `class=`; event-handler attributes are refused.
 
 Each numbered type has its own counter. Websites and Foundry number within a note; books number across their reading order. Unnumbered captions neither display nor consume a number. A map image can retain its asset-derived **Map** classification when no type is specified.
 
@@ -543,7 +543,7 @@ A column's heading is its SQL alias, so `AS "Name"` is what a reader sees. A cel
 | `market`           | The market scale as three columns — `value`, `name`, `trade` — so a table can print `village` beside the number a note wrote.                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
 | `<package>.notes`  | The same relations — `notes`, `entries`, `events`, `names`, `words`, `affixes`, `fields`, `glossary`, `language_lineage`, `dictionary`, `terms`, `register`, `tongues`, `retired`, `scope`, `letters`, `edges`, `clusters`, `stress`, `finals`, `syllables`, `joining`, `joins`, `marks`, `skeleton`, `frames`, `read_past`, `mutations`, `cluster_groups`, `sound_changes`, `elements`, `roots`, `cognates`, `calling_names`, `older`, `negation`, `name_shapes`, `name_edges`, `name_draws`, `held_from` and `near_names` — for each package this one declares a dependency on, in a schema named for it. |
 
-Nested frontmatter is addressed exactly as a note writes it: `name.full`, `sohl.weight`, `data.born`. Every Address is a string — the full canonical Address, as in `list_contains(data.parents, 'thalorna-note-place-xerathia')` — whichever package published it. Every note carries a computed `state` column of `full`, `draft` or `stub`. Notes tagged `gm` are absent from the relations on public surfaces.
+Nested frontmatter is addressed exactly as a note writes it: `name.full`, `sohl.weight`, `data.born`. Every Address is a string — the full canonical Address, as in `list_contains(data.parents, 'thalorna-note-place-xerathia')` — whichever package published it. Every note carries a computed `state` column of `full`, `draft` or `stub`, and a `nameSort` column holding its `name.sort` or, without one, its `name.full`, to `ORDER BY`. Notes tagged `gm` are absent from the relations on public surfaces.
 
 ### Sections the build adds
 
@@ -567,7 +567,7 @@ The vale holds three villages, of which only [[place-ford|Ford]] is walled.
 
 ### Sections the build adds about events
 
-A note's events are listed for you on the notes they concern: a place gets a **Chronology** of what happened there and below it, with every `depth: world` event as context, a being, affiliation or people the **Events** it took part in, an affiliation, place or people the **Accounts** it gives, and a note holding events **What followed** them. Each is a section appended after everything you wrote, with a fixed anchor — `chronology`, `events`, `accounts`, `followed` — and it appears only where it has something to list.
+A note's events are listed for you on the notes they concern: a place gets a **Chronology** of what happened there and below it, with every `depth: world` event as context, a being, affiliation or people the **Events** it took part in, an affiliation, place or people the **Accounts** it gives, and a note holding events **What followed** them. Each is a section appended after everything you wrote, with a fixed anchor — `chronology`, `events`, `accounts`, `followed` — and it appears only where it has something to list. Each lists the date first, written in the setting's calendar, followed by what happened; a Chronology adds a **Felt here** column only where some event is felt in the place, and a PDF book prints it across the full page width.
 
 To replace one, write the section yourself with the same anchor. The build then adds nothing for it and leaves yours exactly as written:
 
@@ -577,7 +577,7 @@ To replace one, write the section yourself with the same anchor. The build then
 The fells keep no reckoning before the raising.
 
 ```sql
-SELECT summary AS "What happened", "when" AS "When"
+SELECT summary AS "What happened", whenText AS "When"
 FROM events
 WHERE list_contains("where".locus, 'thalorna-note-place-ironfells')
 ORDER BY whenSort
@@ -1342,7 +1342,7 @@ The first call lists every page tagged `key-concept` alphabetically by title. Th
 An expression in `{{ }}` is replaced by a value, inline in a sentence. The note's own frontmatter is the context, so a field is read by the path a note writes it at.
 
 ```markdown
-{{name.full}} was born on {{dateformat data.calendar data.born}}.
+{{name.full}} was born on {{dateformat data.born}}.
 There are {{words (sql "SELECT COUNT(*) FROM notes WHERE type = 'being'")}} beings.
 ```
 
@@ -1373,14 +1373,14 @@ There are {{words (sql "SELECT COUNT(*) FROM notes WHERE type = 'being'")}} bein
 | `words`      | `number`                                                                                               | The number spelled out for running prose — `1200` becomes one thousand two hundred. Whole numbers only; a decimal is a finding, and `digits` takes one.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | `digits`     | `number`                                                                                               | The number as a grouped numeral — `1200` becomes 1,200, and a fractional part is kept.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
 | `sql`        | `"query"`                                                                                              | The single value a query returns, for use inside a sentence. The query is a quoted string, the same SQL a table fence takes.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| `dateformat` | `calendar date ["format"]`                                                                             | A date written in a calendar. The calendar is an Address or its shortcode, the date is the value a note carries, and the optional third argument names an output pattern.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `dateformat` | `[calendar] date ["format"]`                                                                           | A date written in a calendar. The calendar is an Address or its shortcode; left out, it is the note's own calendar — its `data.calendar`, else its culture's, else for a place its parents', else the configured `defaultCalendar` — and a note with none prints the date as written. The date is the value a note carries, and the optional last argument names an output pattern.                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | `ref`        | `address [form="number"\|"full"\|"title"] \| address field="when"\|"until"\|"kind"\|"summary"\|"name"` | A link to a captioned item, by its anchor — `"#thorn"` on this note, `"note-address#thorn"` on another. `form` is `number` (the default, and admitted explicitly), rendering "Figure 13"; `full`, the number and the caption; or `title`, the caption alone. Always renders as a link to the figure, and a link inside the caption contributes only its label text. The number rendered is the one the figure carries on the surface doing the rendering, whichever note names it. With `field` in place of `form`, the address names an event — `"place-ironfells#sack"`, `"#sack"` on this note, or `"lore-founding"` for a note holding one event — and the reference prints that event's `when`, `until`, `kind`, `summary` or `name` as plain text, never a link; a date prints as the note format prints any date. |
 
 <!-- expression-helpers:end -->
 
 A helper that is given the wrong kind of value reports it rather than printing something wrong: `words` refuses a decimal, the four comparisons refuse anything that is not a finite number, and `dateformat` refuses a date it cannot resolve in the calendar it was given.
 
-See [date rules](dates-and-calendars.md) for what `dateformat` accepts and the patterns its third argument names.
+See [date rules](dates-and-calendars.md) for what `dateformat` accepts, the calendar it uses when none is named, and the patterns its last argument names.
 
 ### An event's date, inline
 

package/docs/configuration.md

@@ -54,7 +54,7 @@ around its own evaluation.
 
 ### Quick reference
 
-24 top-level keys. `rootDir` is not one of them — a data configuration never
+25 top-level keys. `rootDir` is not one of them — a data configuration never
 writes it — and is documented under [Derived values](#derived-values) instead,
 alongside `foundryPackage`, `homepage`, `author` and `itemBuilders`, whose
 data-configuration behaviour is also derivation rather than ordinary
@@ -63,6 +63,7 @@ authoring.
 | Key                                         | Type                                                                       | Required                                                                                           | Default                   |
 | ------------------------------------------- | -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | ------------------------- |
 | [`currentDate`](#currentdate)               | quoted neutral date string                                                 | no                                                                                                 | `"720.1"`                 |
+| [`defaultCalendar`](#defaultcalendar)       | calendar note shortcode                                                    | no                                                                                                 | —                         |
 | [`contentPackage`](#contentpackage)         | string                                                                     | yes                                                                                                | —                         |
 | [`foundryPackage`](#foundrypackage)         | string                                                                     | yes (`.mjs` only — derived in YAML); refused in a `documentation` package                          | —                         |
 | [`homepage`](#homepage)                     | string                                                                     | no (`.mjs` only — derived in YAML)                                                                 | `null`                    |
@@ -88,7 +89,7 @@ authoring.
 
 Any key outside this list is refused:
 
-> `` `<key>` is not a recognized option (expected one of: rootDir, contentPackage, currentDate, foundryPackage, homepage, authors, packageKind, stats, itemBuilders, paths, skipDirectories, forbidGeneratedArt, icons, packs, docs, site, pdf, compatibility, relationships, systems, requiresSystem, packageBuild, publish, changelog). ``
+> `` `<key>` is not a recognized option (expected one of: rootDir, contentPackage, currentDate, defaultCalendar, foundryPackage, homepage, authors, packageKind, stats, itemBuilders, paths, skipDirectories, forbidGeneratedArt, icons, packs, docs, site, pdf, compatibility, relationships, systems, requiresSystem, packageBuild, publish, changelog). ``
 
 (`rootDir` appears in that list because it is a key `defineConfig` itself
 accepts — an `.mjs` configuration authors it directly. A YAML configuration
@@ -195,7 +196,7 @@ build writes its `name` as `params.author`. `null` when `authors` is empty.
 as an unknown key, at the key's own line, because `authors` is the one list a
 package names its people in:
 
-> ``package-build config: `author` is not a recognized option (expected one of: rootDir, contentPackage, currentDate, foundryPackage, homepage, authors, packageKind, stats, itemBuilders, paths, skipDirectories, forbidGeneratedArt, icons, packs, docs, site, pdf, compatibility, relationships, systems, requiresSystem, packageBuild, publish, changelog).``
+> ``package-build config: `author` is not a recognized option (expected one of: rootDir, contentPackage, currentDate, defaultCalendar, foundryPackage, homepage, authors, packageKind, stats, itemBuilders, paths, skipDirectories, forbidGeneratedArt, icons, packs, docs, site, pdf, compatibility, relationships, systems, requiresSystem, packageBuild, publish, changelog).``
 
 `package.json`'s own `author` is npm's and is not read.
 
@@ -313,6 +314,29 @@ day. Named calendars, `unknown`, numeric YAML values and malformed dates are
 configuration errors located at `currentDate`. Birth dates can still use named
 calendars when the output has the relevant calendar context.
 
+### `defaultCalendar`
+
+**Type:** string · optional · no default.
+
+The shortcode of the `lore` note with `subType: calendar` that prints the dates
+of every note no other rule gives a calendar. A note reads its dates in its own
+`data.calendar`, else its culture's, else — for a place — its parents', and
+only then in this one; with no `defaultCalendar` and nothing else to go on, a
+date prints as it was written. The
+[format reference](reference/format-details.md#a-notes-calendar) gives the
+rules in full.
+
+```yaml
+contentPackage: thalorna
+defaultCalendar: commoncal
+```
+
+A value that is not a lowercase alphanumeric shortcode is a configuration
+error at load. A shortcode that names no calendar note in the package is a
+build error located at `defaultCalendar`:
+
+> `defaultCalendar commonkal names no calendar note in thalorna; name the shortcode of a lore note with subType: calendar`
+
 ### `contentPackage`
 
 **Type:** string · **Required** · no default.
@@ -1259,7 +1283,9 @@ Each entry of `pdf.books` is one PDF:
   abbreviation and the page, and the other book's index, when
   `pdf.indexSeeAlso` is on, lists the note as `Name: Aelw. p307`. A book
   with no abbreviation is named by its full title in italics, `Name (_Book
-title_, p. 307)`. Each abbreviation is used once, since a reader could not
+title_, p. 307)`. A link the text closes a bracket on takes the reference
+  inside that bracket after a comma, so `(see The Crossing)` prints
+  `(see The Crossing, Thal. p524)` rather than nesting brackets. Each abbreviation is used once, since a reader could not
   tell which book to open from one shared by two.
 - `contents` is the tree written inline — the same `sectionName` /
   `contents` / `filter` / `file` shape a tree file holds under its own

package/docs/guides/book.md

@@ -174,11 +174,11 @@ the Lyrebird Inn (The Tenebrae Volume, p. 214)
 
 Which form a wikilink takes depends on where its target is printed:
 
-| The target is                                                 | The link prints                                                                      |
-| ------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
-| An entry of the same book, including a note the book reprints | An internal destination                                                              |
-| An entry of another book, and not of this one                 | `Name (_Book title_, p. N)`, or `Name (Aelw. pN)` with an abbreviation, with no link |
-| A note in no book                                             | The web address of the note's page                                                   |
+| The target is                                                 | The link prints                                                                                                                            |
+| ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| An entry of the same book, including a note the book reprints | An internal destination                                                                                                                    |
+| An entry of another book, and not of this one                 | `Name (_Book title_, p. N)`, or `Name (Aelw. pN)` with an abbreviation, with no link; inside a bracket the text closes, `(Name, Aelw. pN)` |
+| A note in no book                                             | The web address of the note's page                                                                                                         |
 
 The page is the page the PDF itself numbers, which is the number printed in the
 footer and used by the contents and the index, so the printed `p. N` is the
@@ -406,12 +406,12 @@ A book that prints at least one note ends with an **Index** chapter, grouped
 under letter headings. Nothing configures it: the build derives it from the
 notes the book prints.
 
-| Term                     | Source                | Shown as                                                                           |
-| ------------------------ | --------------------- | ---------------------------------------------------------------------------------- |
-| A note's name            | `name.full`           | the page of the note's entry in **bold**, then the pages of every authored mention |
-| A name without its head  | `name.full`           | the same pages as the note's entry, filed as `Targud, Kingdom of`                  |
-| An alias                 | `name.aliases`        | _see_ the note's name                                                              |
-| An event's in-world name | `data.events[].names` | _see_ the name of the note that holds the event                                    |
+| Term                     | Source                        | Shown as                                                                           |
+| ------------------------ | ----------------------------- | ---------------------------------------------------------------------------------- |
+| A note's name            | `name.sort`, else `name.full` | the page of the note's entry in **bold**, then the pages of every authored mention |
+| A name without its head  | `name.full`                   | the same pages as the note's entry, filed as `Targud, Kingdom of`                  |
+| An alias                 | `name.aliases`                | _see_ the note's name                                                              |
+| An event's in-world name | `data.events[].names`         | _see_ the name of the note that holds the event                                    |
 
 A name that opens with a generic word a reader would not look under, such as
 `Kingdom of Targud` or `Ritual: Blessing`, is also filed under the rest of the
@@ -460,7 +460,7 @@ Two kinds of link add nothing:
 
 Terms sort on the ASCII fold the content index derives for names (`nameAscii`),
 ignoring case, so an accented name files under its base letter and the order
-matches the table of contents. A term that does not begin with a letter files
+matches the table of contents. A note's own entry reads as its `name.sort` when it declares one, in index form such as `Black Flame, The` or `Hilvan, Doran`, and as its `name.full` otherwise; it files, and takes its letter heading, from that form. A note that declares a `sort` is not also filed under `pdf.indexHeads`. A term that does not begin with a letter files
 first, under `#`. An alias or event name that folds to the same text as the
 note's own name is not listed again.
 

package/docs/guides/module-project.md

@@ -275,7 +275,7 @@ Five keys, and each answers a question the build cannot answer for itself:
 Everything omitted has a default, and the defaults are the conventional
 HeroicLands layout: the content tree at `assets/content`, the compiled packs at
 `build/stage/packs`, the intermediates and caches elsewhere under `build/`.
-[`configuration.md`](../configuration.md) documents all eighteen top-level keys,
+[`configuration.md`](../configuration.md) documents every top-level key,
 what each refusal message means, and the five values that are derived rather
 than authored.
 

package/docs/reference/format-details.md

@@ -379,7 +379,13 @@ content, comment out its YAML lines with `#`. Comments remain valid YAML text
 and do not become data in the JSONL index, generated pages, or Foundry documents.
 
 `name` is a map with a required nonempty `full` string when present. It may
-also contain `aliases`, an ordered list of nonempty strings. A being with
+also contain `aliases`, an ordered list of nonempty strings, and `sort`, a nonempty
+string giving the form the name takes in an index, such as `Black Flame, The` or
+`Hilvan, Doran`. `sort` files the note wherever notes are ordered by name (page
+lists, generated lists of related notes, the book index, the `nameSort` column)
+and is the note's entry text in the book index; every other list still displays
+`full`. Without `sort`, the note files and indexes by `full`. Ordering compares
+the ASCII fold of the key (`Árdavon` files beside `Ardavon`). A being with
 `subType: character` may additionally contain nonempty `given` and `clan`
 strings. Other keys under `name` are errors. For a character or NPC, the first
 alias is its nickname. A being's homes belong in `data.homes`.
@@ -426,17 +432,55 @@ A named date uses `datefrom <calendar> <date>`, where the final text follows the
 
 `package-build datefrom <calendar> <date>` reads the default calendar pattern and prints a canonical day. `package-build dateto <calendar> <canonical-date>` prints the day in the covering era; `--format <name>` chooses another named output pattern. The [authoring guide](../authoring/dates-and-calendars.md) gives a complete example.
 
+##### A note's calendar
+
+A note's dates print in one calendar, the first of:
+
+1. its own `data.calendar`, which every note type accepts, and which always
+   wins;
+2. its culture's calendar: the culture note its `data.culture` names, resolved
+   by these same rules — in effect that culture's own `data.calendar`;
+3. for a `place`, its parents' calendar: each note its `data.parents` names,
+   resolved by these same rules;
+4. the package's [`defaultCalendar`](../configuration.md#defaultcalendar);
+5. otherwise none, and a date prints as it was written.
+
+Steps 2 and 3 take only a calendar that some note states. A culture or a
+parent that itself falls through to `defaultCalendar` contributes nothing, so a
+place whose parents all fall through takes the default. Parents that resolve to
+**two or more distinct calendars** are a build error at the place's
+`data.parents`, naming the place and each calendar with the parent it came
+through:
+
+```text
+Places/Edge.md:6:3: error: place edge: data.parents resolve to different calendars (thalorna-note-lore-commoncal via north, thalorna-note-lore-vrcal via south); state data.calendar
+```
+
+Stating `data.calendar` on the place settles it. A cycle through
+`data.parents` or `data.culture` contributes nothing, and the chain goes on to
+`defaultCalendar`. A culture or parent in another package contributes the
+`data.calendar` its published entry states, and nothing else.
+
+The calendar decides what a reader sees wherever the note prints a date: the
+infobox's `born` and `died`, `dateformat` with no calendar named, the `events`
+relation's `whenText`, and every date in the [event views](#event-views) the
+note's page shows.
+
 Markdown prose accepts inline `{{...}}` expressions. A property path reads
 the note's frontmatter, and `dateformat` converts a date to the reckoning used by a
-specified calendar. The first argument names a calendar note by shortcode or
-Address, or one of its eras by `<calendar>.<era>`. Use a full Address when a
-short name is ambiguous. The second argument is a canonical date or a
-frontmatter property holding a date. An optional third argument names an output
-format from the calendar note. An explicit era that does not cover the date is an error.
+calendar. The first argument names a calendar note by shortcode or Address, or
+one of its eras by `<calendar>.<era>`; left out, the calendar is
+[the note's own](#a-notes-calendar), and a note with none prints the date as
+written. Use a full Address when a short name is ambiguous. The date is a
+canonical date or a frontmatter property holding a date. An optional last
+argument names an output format from the calendar note. With two arguments,
+the first is the calendar unless it is a date that names no calendar, so
+`{{dateformat data.born "long"}}` prints the note's date in its own calendar's
+`long` format. An explicit era that does not cover the date is an error.
 
 ```markdown
 {{name.full}} was born on {{dateformat "vrcal" data.born}}.
-{{dateformat data.calendar data.born}}
+{{dateformat data.born}}
 The event fell on {{dateformat "vrcal" "300.25"}}.
 {{and (gt 3 5) (lt 4 2)}}
 {{sql "SELECT COUNT(*) FROM notes WHERE type = 'being'"}}
@@ -864,6 +908,7 @@ noticed:
 | `seeAlso`              | list of `{ address, gloss? }` | Deliberate cross-references in reading order, shown on the site, in journals and in books. |
 | `seeAlso[].address`    | a note `Address`              | Required; the whole note to read next.                                                     |
 | `seeAlso[].gloss`      | `string`                      | An optional short phrase saying why to follow the reference.                               |
+| `calendar`             | `Address`                     | The calendar note this note's dates print in — see [a note's calendar](#a-notes-calendar). |
 | `id`                   | `string`                      | A pinned document identity.                                                                |
 | `pack`                 | `string`                      | The shared compendium route.                                                               |
 | `packFolder`           | `Address` or pack map         | The shared compendium folder Address.                                                      |
@@ -2916,7 +2961,9 @@ reads `NULL` rather than failing. `data.culture` is the one field that reads as
 a derived value: the note's own culture, or the one it inherits. See
 [Culture in the index](#culture-in-the-index).
 
-**`notes` leaves out stubs; `entries` does not.** Both carry a derived `state`
+**`notes` leaves out stubs; `entries` does not.** Both carry a derived `nameSort`
+column — the note's `name.sort` when it declares one, otherwise its `name.full`,
+unfolded — for `ORDER BY`, and a derived `state`
 column — `stub`, `draft` or `full` — and `notes` is exactly
 `SELECT * FROM entries WHERE state <> 'stub'`. So every table already written
 selects what it always selected, and gains `state` for free; a table that should
@@ -2957,20 +3004,29 @@ query rather than a list kept by hand:
 
 ````markdown
 ```sql
-SELECT note AS _ref, "when" AS "When", summary AS "What happened"
+SELECT note AS _ref, whenText AS "When", summary AS "What happened"
 FROM events
 WHERE kind IN ('war', 'siege', 'battle')
 ORDER BY whenSort
 ```
 ````
 
-| Column                   | What it holds                                                                                                                                                                                                               |
-| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `note`                   | The canonical Address of the note the event is written on.                                                                                                                                                                  |
-| `address`                | The event's own Address: `note#id` where the event has an `id`, the note's Address alone where it has none.                                                                                                                 |
-| `id`, `kind`, `depth`, … | Every key of an event, each its own column under its own name — `id`, `kind`, `depth`, `when`, `until`, `recurs`, `summary`, `standing`, `names`, `where`, `who`, `follows`, `accounts`, `unresolved`, `sources`, `stated`. |
-| `whenSort`, `untilSort`  | The date's position on the canonical axis: the canonical year, with a day as its fraction of the year where the calendar states the year's length. `ORDER BY whenSort` is date order.                                       |
-| `whenYear`, `untilYear`  | The canonical year alone, for a filter such as `whenYear BETWEEN 200 AND 299`.                                                                                                                                              |
+| Column                   | What it holds                                                                                                                                                                                                                                                            |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `note`                   | The canonical Address of the note the event is written on.                                                                                                                                                                                                               |
+| `address`                | The event's own Address: `note#id` where the event has an `id`, the note's Address alone where it has none.                                                                                                                                                              |
+| `id`, `kind`, `depth`, … | Every key of an event, each its own column under its own name — `id`, `kind`, `depth`, `when`, `until`, `recurs`, `summary`, `standing`, `names`, `where`, `who`, `follows`, `accounts`, `unresolved`, `sources`, `stated`.                                              |
+| `whenSort`, `untilSort`  | The date's position on the canonical axis: the canonical year, with a day as its fraction of the year where the calendar states the year's length. `ORDER BY whenSort` is date order.                                                                                    |
+| `whenText`, `untilText`  | The date as a reader of the owning note sees it, printed as `dateformat` prints it in [the owning note's calendar](#a-notes-calendar), else in the era the date itself names; `~` marks an approximate date. A date that does not resolve keeps the text its note wrote. |
+| `whenIn`, `untilIn`      | The date in every calendar: a struct keyed by each calendar note's canonical Address, holding the date as `dateformat` prints it there. `whenIn['thalorna-note-lore-commoncal']` reads it in that calendar; a date that calendar cannot print reads as in `whenText`.    |
+| `whenYear`, `untilYear`  | The canonical year alone, for a filter such as `whenYear BETWEEN 200 AND 299`.                                                                                                                                                                                           |
+
+A fence chooses which calendar its dates print in. `whenText` prints each
+row in the calendar of the note that owns the event, so a table gathering the
+events of notes with different calendars reads in more than one count;
+`whenIn['<calendar Address>']` prints every row in one. The generated [event
+views](#event-views) do the second, in the calendar of the page showing the
+view.
 
 `when` and `until` read as the text the note wrote, `~` included. The sort
 keys and years are positions on the canonical axis, which counts a year `0`
@@ -3498,7 +3554,7 @@ The caption attaches to exactly the next supported block:
 
 The optional `type` attribute overrides inference and accepts `figure`, `table`, `poetry`, `code`, `prose`, and `example`. `type=example` uses **Example 1**, **Example 2**, and so on. It does not allow an unsupported target. A heading, list, thematic break, another caption or end of document after a caption is an error. Caption markers without separating spaces or caption text are errors too.
 
-Identifiers are optional and must be unique within the note. Classes are unrestricted; `.border` uses the shared border style, while other classes can be styled by the medium. Named attributes use `key=value`, with quoted values for text containing spaces. Use `#id` and `.class` rather than `id=` and `class=`; event-handler attributes are refused.
+Identifiers are optional and must be unique within the note. Classes are unrestricted; `.border` uses the shared border style, while other classes can be styled by the medium. On a captioned table or SQL fence, `.full-width` sets the table across the page in a PDF book instead of in one column (`: Regional trade routes {.full-width}`); the other surfaces ignore it. Named attributes use `key=value`, with quoted values for text containing spaces. Use `#id` and `.class` rather than `id=` and `class=`; event-handler attributes are refused.
 
 Each numbered type has its own counter. Websites and Foundry number within a note; books number across their reading order. Unnumbered captions neither display nor consume a number. A map image can retain its asset-derived **Map** classification when no type is specified.
 
@@ -3763,11 +3819,14 @@ The build appends sections to the end of a note's body that list the events conc
 
 | View          | Anchor       | On                                                               | Rows                                                                                                                                                                              | Columns                            |
 | ------------- | ------------ | ---------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- |
-| Chronology    | `chronology` | a `place`                                                        | events whose `where.locus` names the place or a place below it in `parents`; events whose `where.reach` names one, with that entry's `how`; every `depth: world` event as context | What happened, When, Felt here     |
-| Events        | `events`     | a `being`, an `affiliation`, a `lore` note of `subType: culture` | events whose `who[].ref` names the note, with the role it played                                                                                                                  | What happened, When, Role          |
-| Accounts      | `accounts`   | an `affiliation`, a `place`, a `lore` note of `subType: culture` | each `accounts[]` entry the note gives, with the event it concerns                                                                                                                | Event, When, What they say, Agrees |
-| What followed | `followed`   | a note holding events                                            | events whose `follows[].event` names one of this note's events, with how                                                                                                          | What followed, When, How           |
-
+| Chronology    | `chronology` | a `place`                                                        | events whose `where.locus` names the place or a place below it in `parents`; events whose `where.reach` names one, with that entry's `how`; every `depth: world` event as context | When, What happened, Felt here     |
+| Events        | `events`     | a `being`, an `affiliation`, a `lore` note of `subType: culture` | events whose `who[].ref` names the note, with the role it played                                                                                                                  | When, What happened, Role          |
+| Accounts      | `accounts`   | an `affiliation`, a `place`, a `lore` note of `subType: culture` | each `accounts[]` entry the note gives, with the event it concerns                                                                                                                | When, Event, What they say, Agrees |
+| What followed | `followed`   | a note holding events                                            | events whose `follows[].event` names one of this note's events, with how                                                                                                          | When, What followed, How           |
+
+- **Every view's first column is When**, every row's date written in [the calendar of the page showing the view](#a-notes-calendar), whichever note owns the event, so one table reads in one count. The fence reads `whenIn['<calendar Address>']` for that calendar; on a page with no calendar it reads `whenText`, each date in its owning note's calendar. An event whose date does not resolve shows the text its note wrote.
+- **A chronology's Felt here column appears only where some row is felt in the place.** A place whose rows are all events that happened there, or world events, has the When and What happened columns alone.
+- **A chronology is always set across the full page width in a PDF book**, whatever its columns.
 - **The views follow everything the author wrote**, in the order of the [generated sections](#generated-sections).
 - **A view with no rows is not generated.** A chronology is generated only where the place has rows of its own; the world events beside them are context and make no chronology by themselves.
 - **An author's own section replaces a view.** A note whose body declares a prose anchor with the view's slug — `# Chronology {#chronology}`, or a block or span with that `id` — gets no generated section for it, and its own section is left exactly as written. This is the one way to turn a view off, and the way to choose a different table: write the section and its own `sql` fence.
@@ -4068,7 +4127,6 @@ See [a being's subtype describes the subject](#a-beings-subtype-describes-the-su
 | `gender`                           | `male \| female \| nonbinary \| none \| other` | Gender of the being — see [a being's look](#a-beings-look)                                                                                            |
 | `species`                          | `Address`                                      | Being's species (lore)                                                                                                                                |
 | `born`                             | `date \| unknown`                              | When the being was born; absent, it was never born                                                                                                    |
-| `calendar`                         | `Address`                                      | Calendar note that prints the being's dates                                                                                                           |
 | `died`                             | `date \| unknown`                              | When the being died; absent, it is alive                                                                                                              |
 | `age`                              | `34 \| ~34`                                    | Age in years, stated only to override what `born` says; `~` marks an estimate                                                                         |
 | `ageYears`                         | `number`                                       | Written by the compiler beside an `age` estimate — the `~` stripped; a note never authors this                                                        |
@@ -6970,7 +7028,6 @@ level with no background prints nothing.
 | `data` property                   | Values                                                                           | Description                                                                                               |
 | --------------------------------- | -------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
 | `events`                          | event entries — see [Events](#events)                                            | What happened to or at this subject: dated, attributed events                                             |
-| `calendar`                        | `Address`                                                                        | Calendar note that prints this place's dates                                                              |
 | `demonym`                         | `string`                                                                         | What a person from this place is called — a Vylarian                                                      |
 | `purpose`                         | `placeCharacter` tag                                                             | The reason a settlement, site, or structure exists                                                        |
 | `lore`                            | `Address[]`                                                                      | Lore concerning this place — its peoples, its law, its calendar, its history                              |