@ecoma-io/loom 0.1.1 → 0.2.0

package/dist/lib/count-labels.d.ts

@@ -0,0 +1,78 @@
+import type { LabelOf } from "./labels";
+/**
+ * The five counter keys shared by TextField and Textarea — the ones a host
+ * worded for one can copy across unchanged to the other. The keys match by
+ * name and by argument shape; the slots are separate in `LoomLabels` only
+ * because `textField` also carries `reveal`.
+ *
+ * The four counting keys take the **numbers**, never a formatted string, for
+ * the reason `./labels.ts` gives at length: `${count}/${max}` is a punctuation
+ * choice made in one language, and "3 characters left" has one plural form in
+ * Vietnamese, two in English and six in Arabic. A host handed the integers
+ * reaches `Intl.PluralRules` for the category and `Intl.NumberFormat` for the
+ * digits; a host handed "3/20" can do neither.
+ *
+ * There are three visible counter strings rather than one with a conditional
+ * inside it, because the three say different things: a running total against
+ * no limit, a total against a limit, and a limit already passed. The last is
+ * the one that must not read as merely a redder version of the second — see
+ * `countOverMax`.
+ */
+export interface CountLabels {
+    /** The counter when the field has no maximum: a running total, nothing more. */
+    readonly count: LabelOf<{
+        count: number;
+    }>;
+    /** The counter when the field has a maximum and is within it. */
+    readonly countOfMax: LabelOf<{
+        count: number;
+        max: number;
+    }>;
+    /**
+     * The counter once the value is past the maximum.
+     *
+     * Loom's English adds words rather than only digits, and that is the
+     * accessibility requirement rather than a flourish: over-limit is painted
+     * `text-destructive`, and a state carried by colour alone fails WCAG 1.4.1.
+     * An override that returns the same shape as `countOfMax` puts that failure
+     * back.
+     */
+    readonly countOverMax: LabelOf<{
+        count: number;
+        max: number;
+        over: number;
+    }>;
+    /**
+     * Announced **once**, as the value crosses into the last stretch of its
+     * allowance — not on every keystroke after it. The numbers are true at the
+     * moment it is spoken; the visible counter is what carries them afterwards.
+     */
+    readonly approachingLimit: LabelOf<{
+        remaining: number;
+        max: number;
+    }>;
+    /** Announced once, as the value crosses the maximum. */
+    readonly limitExceeded: LabelOf<{
+        over: number;
+        max: number;
+    }>;
+}
+/**
+ * Loom's English defaults for the counter vocabulary, co-located here so the
+ * two components that share it tree-shake together and an importing host can
+ * build a partial vocabulary against the real thing rather than a transcription.
+ */
+export declare const COUNT_LABELS: CountLabels;
+/**
+ * How close to the maximum the warning fires: the last quarter of a short
+ * allowance, or the last ten characters of a long one, whichever is smaller.
+ *
+ * Ten is about a word, and a warning is only worth anything while there is
+ * still room to act on it — a fixed tenth would give a 280-character field
+ * twenty-eight characters of notice and a twenty-character field two, which is
+ * either too early to mean anything or too late to be a warning.
+ */
+export declare function warningWindow(max: number): number;
+/** Where the value sits against its maximum, and the only thing the announcement watches. */
+export type CountBand = "under" | "near" | "over";
+//# sourceMappingURL=count-labels.d.ts.map

package/dist/lib/count-labels.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"count-labels.d.ts","sourceRoot":"","sources":["../../src/lib/count-labels.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,UAAU,CAAC;AAExC;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,WAAW,WAAW;IAC1B,gFAAgF;IAChF,QAAQ,CAAC,KAAK,EAAE,OAAO,CAAC;QAAE,KAAK,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IAC3C,iEAAiE;IACjE,QAAQ,CAAC,UAAU,EAAE,OAAO,CAAC;QAAE,KAAK,EAAE,MAAM,CAAC;QAAC,GAAG,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IAC7D;;;;;;;;OAQG;IACH,QAAQ,CAAC,YAAY,EAAE,OAAO,CAAC;QAAE,KAAK,EAAE,MAAM,CAAC;QAAC,GAAG,EAAE,MAAM,CAAC;QAAC,IAAI,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IAC7E;;;;OAIG;IACH,QAAQ,CAAC,gBAAgB,EAAE,OAAO,CAAC;QAAE,SAAS,EAAE,MAAM,CAAC;QAAC,GAAG,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IACvE,wDAAwD;IACxD,QAAQ,CAAC,aAAa,EAAE,OAAO,CAAC;QAAE,IAAI,EAAE,MAAM,CAAC;QAAC,GAAG,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;CAChE;AAED;;;;GAIG;AACH,eAAO,MAAM,YAAY,EAAE,WAQ1B,CAAC;AAEF;;;;;;;;GAQG;AACH,wBAAgB,aAAa,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,CAEjD;AAED,6FAA6F;AAC7F,MAAM,MAAM,SAAS,GAAG,OAAO,GAAG,MAAM,GAAG,MAAM,CAAC"}

package/dist/lib/count-labels.js

@@ -0,0 +1,29 @@
+//#region src/lib/count-labels.ts
+/**
+* Loom's English defaults for the counter vocabulary, co-located here so the
+* two components that share it tree-shake together and an importing host can
+* build a partial vocabulary against the real thing rather than a transcription.
+*/
+var COUNT_LABELS = {
+	count: ({ count }) => String(count),
+	countOfMax: ({ count, max }) => `${String(count)}/${String(max)}`,
+	countOverMax: ({ count, max }) => `${String(count)}/${String(max)} over limit`,
+	approachingLimit: ({ remaining }) => `${String(remaining)} ${remaining === 1 ? "character" : "characters"} left`,
+	limitExceeded: ({ over, max }) => `${String(over)} ${over === 1 ? "character" : "characters"} over the limit of ${String(max)}`
+};
+/**
+* How close to the maximum the warning fires: the last quarter of a short
+* allowance, or the last ten characters of a long one, whichever is smaller.
+*
+* Ten is about a word, and a warning is only worth anything while there is
+* still room to act on it — a fixed tenth would give a 280-character field
+* twenty-eight characters of notice and a twenty-character field two, which is
+* either too early to mean anything or too late to be a warning.
+*/
+function warningWindow(max) {
+	return Math.min(10, Math.ceil(max / 4));
+}
+//#endregion
+export { COUNT_LABELS, warningWindow };
+
+//# sourceMappingURL=count-labels.js.map

package/dist/lib/count-labels.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"count-labels.js","names":[],"sources":["../../src/lib/count-labels.ts"],"sourcesContent":["import type { LabelOf } from \"./labels\";\n\n/**\n * The five counter keys shared by TextField and Textarea — the ones a host\n * worded for one can copy across unchanged to the other. The keys match by\n * name and by argument shape; the slots are separate in `LoomLabels` only\n * because `textField` also carries `reveal`.\n *\n * The four counting keys take the **numbers**, never a formatted string, for\n * the reason `./labels.ts` gives at length: `${count}/${max}` is a punctuation\n * choice made in one language, and \"3 characters left\" has one plural form in\n * Vietnamese, two in English and six in Arabic. A host handed the integers\n * reaches `Intl.PluralRules` for the category and `Intl.NumberFormat` for the\n * digits; a host handed \"3/20\" can do neither.\n *\n * There are three visible counter strings rather than one with a conditional\n * inside it, because the three say different things: a running total against\n * no limit, a total against a limit, and a limit already passed. The last is\n * the one that must not read as merely a redder version of the second — see\n * `countOverMax`.\n */\nexport interface CountLabels {\n  /** The counter when the field has no maximum: a running total, nothing more. */\n  readonly count: LabelOf<{ count: number }>;\n  /** The counter when the field has a maximum and is within it. */\n  readonly countOfMax: LabelOf<{ count: number; max: number }>;\n  /**\n   * The counter once the value is past the maximum.\n   *\n   * Loom's English adds words rather than only digits, and that is the\n   * accessibility requirement rather than a flourish: over-limit is painted\n   * `text-destructive`, and a state carried by colour alone fails WCAG 1.4.1.\n   * An override that returns the same shape as `countOfMax` puts that failure\n   * back.\n   */\n  readonly countOverMax: LabelOf<{ count: number; max: number; over: number }>;\n  /**\n   * Announced **once**, as the value crosses into the last stretch of its\n   * allowance — not on every keystroke after it. The numbers are true at the\n   * moment it is spoken; the visible counter is what carries them afterwards.\n   */\n  readonly approachingLimit: LabelOf<{ remaining: number; max: number }>;\n  /** Announced once, as the value crosses the maximum. */\n  readonly limitExceeded: LabelOf<{ over: number; max: number }>;\n}\n\n/**\n * Loom's English defaults for the counter vocabulary, co-located here so the\n * two components that share it tree-shake together and an importing host can\n * build a partial vocabulary against the real thing rather than a transcription.\n */\nexport const COUNT_LABELS: CountLabels = {\n  count: ({ count }) => String(count),\n  countOfMax: ({ count, max }) => `${String(count)}/${String(max)}`,\n  countOverMax: ({ count, max }) => `${String(count)}/${String(max)} over limit`,\n  approachingLimit: ({ remaining }) =>\n    `${String(remaining)} ${remaining === 1 ? \"character\" : \"characters\"} left`,\n  limitExceeded: ({ over, max }) =>\n    `${String(over)} ${over === 1 ? \"character\" : \"characters\"} over the limit of ${String(max)}`,\n};\n\n/**\n * How close to the maximum the warning fires: the last quarter of a short\n * allowance, or the last ten characters of a long one, whichever is smaller.\n *\n * Ten is about a word, and a warning is only worth anything while there is\n * still room to act on it — a fixed tenth would give a 280-character field\n * twenty-eight characters of notice and a twenty-character field two, which is\n * either too early to mean anything or too late to be a warning.\n */\nexport function warningWindow(max: number): number {\n  return Math.min(10, Math.ceil(max / 4));\n}\n\n/** Where the value sits against its maximum, and the only thing the announcement watches. */\nexport type CountBand = \"under\" | \"near\" | \"over\";\n"],"mappings":";;;;;;AAmDA,IAAa,eAA4B;CACvC,QAAQ,EAAE,YAAY,OAAO,KAAK;CAClC,aAAa,EAAE,OAAO,UAAU,GAAG,OAAO,KAAK,EAAE,GAAG,OAAO,GAAG;CAC9D,eAAe,EAAE,OAAO,UAAU,GAAG,OAAO,KAAK,EAAE,GAAG,OAAO,GAAG,EAAE;CAClE,mBAAmB,EAAE,gBACnB,GAAG,OAAO,SAAS,EAAE,GAAG,cAAc,IAAI,cAAc,aAAa;CACvE,gBAAgB,EAAE,MAAM,UACtB,GAAG,OAAO,IAAI,EAAE,GAAG,SAAS,IAAI,cAAc,aAAa,qBAAqB,OAAO,GAAG;AAC9F;;;;;;;;;;AAWA,SAAgB,cAAc,KAAqB;CACjD,OAAO,KAAK,IAAI,IAAI,KAAK,KAAK,MAAM,CAAC,CAAC;AACxC"}

package/dist/lib/date-labels.d.ts

@@ -0,0 +1,278 @@
+import { type DateValue } from "@internationalized/date";
+import type { LabelOf } from "./labels";
+/**
+ * The four slices the five date and time controls share, and the one decision
+ * behind putting them here rather than five times over.
+ *
+ * Every other component in the library declares its own bag beside its own
+ * markup, because its vocabulary is its own. These five do not have five
+ * vocabularies: `DatePicker`, `DateTimePicker`, `DateRangePicker` and
+ * `DateTimeRangePicker` all say *Open calendar*, *Previous month* and *Next
+ * month*, and all five name the parts of a segmented field with the same
+ * words — the words are Reka UI's `useDateField` and `CalendarRoot` speaking,
+ * one implementation underneath all five. Declared per component that would be
+ * fifty-two keys with the same twelve strings written four times, and a
+ * translator doing the same work four times to make one language complete.
+ *
+ * **Sliced by what a control actually says, not merged into one family bag.**
+ * A `TimePicker` has no calendar and never renders a month or a year, so it
+ * registers `timeSegments` alone: its documented vocabulary is four keys, and a
+ * consumer importing only that control ships only those four strings. One
+ * shared bag for the whole family would have made every one of the five carry
+ * all twenty, and would have printed keys on `TimePicker`'s API page that it
+ * has no element to put them on.
+ *
+ * What is deliberately *not* shared is the two range controls' half-group names
+ * and status lines. They name the same concepts with different words (`Start
+ * date` against `Start date and time`) and from different facts (a count of
+ * whole days against a signed duration in minutes), so a shared key would have
+ * to be a sentence that is never true of both. Their calendar cells' names are
+ * shared, because those differ in neither.
+ */
+/**
+ * The names Reka UI's `useDateField` writes onto the day, month, year and era
+ * segments — `"day,"`, `"month, "`, `"year, "`, `"era"`, each with the spacing
+ * of a string it meant to concatenate.
+ *
+ * There is no prop for any of them. A binding on Loom's side reaches the
+ * segment as a fallthrough attribute, which Vue merges onto the rendered vnode
+ * *after* Reka's own render function produced it, and `mergeProps` is
+ * last-write-wins for everything that is not `class`, `style` or `on*` — so
+ * these replace Reka's rather than competing with it. Leave one unset and the
+ * segment is not unnamed, it is named in English, which is the failure this
+ * seam exists to close.
+ *
+ * Loom's defaults differ from Reka's by their capitalisation, which is what
+ * lets a test assert *whose* string reached the DOM rather than merely what it
+ * said.
+ */
+export interface DateSegmentLabels {
+    /** The month segment of a date field. */
+    readonly month: string;
+    /** The day-of-month segment. */
+    readonly day: string;
+    /** The year segment. */
+    readonly year: string;
+    /**
+     * The era segment, which most locales never render — `ja-JP-u-ca-japanese`
+     * is the ordinary case that does.
+     */
+    readonly era: string;
+    /**
+     * What a segment with nothing in it yet reports as its value, replacing the
+     * `aria-valuetext="Empty"` Reka writes on an unfilled day, month or year.
+     *
+     * A segment shows the locale's own placeholder — `mm`, `jj`, `aaaa` — while
+     * announcing this instead, so it is the one word standing between a fully
+     * localised date field and a reader who is told "Empty" in English.
+     *
+     * Present on this slice *and* on `TimeSegmentLabels` rather than shared
+     * between them, for the reason the slices exist at all: a `TimePicker`
+     * registers no `dateSegments`, and a key it could only reach through the
+     * date half would be a key it could not set.
+     */
+    readonly empty: string;
+    /**
+     * What a filled month segment announces as its value, replacing the
+     * `aria-valuetext` Reka builds inside `useDateField`.
+     *
+     * Reka writes `"5 - May"` — the numeric month, a hard-coded `" - "`, and
+     * the month name from `Intl.DateTimeFormat`. The name is locale-aware, but
+     * the format is not: Japanese writes `"5月"`, Vietnamese `"tháng 5"`, and
+     * neither separates the two parts with a hyphen. A `LabelOf` hands the
+     * host the month number and the locale so they can compose the string their
+     * language needs, using `Intl.DateTimeFormat` for the name and arranging the
+     * parts in the right order.
+     *
+     * A `LabelOf` rather than a plain string, for the same reason
+     * `RangeCellLabels.cell` is one: the month name depends on the locale, and
+     * a string that did not receive the locale could not produce it. The host
+     * decides the format — Loom's English default matches Reka's output so that
+     * nothing changes for a consumer who does not override it.
+     */
+    readonly filledMonth: LabelOf<{
+        value: number;
+        locale: string;
+    }>;
+}
+/**
+ * Loom's English for the date segments, co-located so it tree-shakes with the
+ * controls that use it, and exported so a host can build a partial vocabulary
+ * against the real thing rather than a transcription of it.
+ */
+export declare const DATE_SEGMENT_LABELS: DateSegmentLabels;
+/**
+ * The same, for the clock half of a segmented field: Reka writes `"hour, "`,
+ * `"minute, "`, `"second, "` and `"AM/PM"`, and offers a prop for none of them.
+ *
+ * `dayPeriod` is spelled `AM or PM` rather than `AM/PM` so that it reads as
+ * words when it is spoken, and so the capitalisation trick above still works on
+ * the one segment whose name Reka already capitalises.
+ */
+export interface TimeSegmentLabels {
+    /** The hour segment. */
+    readonly hour: string;
+    /** The minute segment. */
+    readonly minute: string;
+    /** The seconds segment, which only a control at second granularity renders. */
+    readonly second: string;
+    /** The AM/PM segment, which only a 12-hour field renders. */
+    readonly dayPeriod: string;
+    /** What an hour, minute or second with nothing in it yet reports. See `DateSegmentLabels.empty`. */
+    readonly empty: string;
+    /**
+     * What a filled day-period segment announces as its value, replacing the
+     * `aria-valuetext` Reka writes inside `useDateField`.
+     *
+     * Reka writes `segmentValues.dayPeriod ?? "AM"` — always `"AM"` or `"PM"`,
+     * produced by its own hour-cycle logic (`hour >= 12 ? "PM" : "AM"`) rather
+     * than by `Intl.DateTimeFormat`. A host who has localised every other string
+     * in the library still hears Latin-script "AM"/"PM" from this segment, which
+     * is the defect this key exists to close.
+     *
+     * A `LabelOf` rather than a plain string, because the period name depends on
+     * the locale: Arabic writes `"ص"`/`"م"`, Japanese `"午前"`/`"午後"`, and a
+     * plain string could not carry that decision. Loom's English default returns
+     * `dayPeriod` unchanged, which is correct for Latin-script locales.
+     */
+    readonly filledDayPeriod: LabelOf<{
+        dayPeriod: string;
+    }>;
+}
+/** Loom's English for the time segments. See `DATE_SEGMENT_LABELS`. */
+export declare const TIME_SEGMENT_LABELS: TimeSegmentLabels;
+/**
+ * The parts each slice actually names — every key of its bag except `empty`,
+ * which is a message *about* a segment rather than the name of one.
+ *
+ * Both the type and the set below are written out rather than derived from the
+ * bags, which is what they were before `empty` joined them. Derived, the guards
+ * would answer `true` for `"empty"` and narrow a part to a key that names no
+ * element, and `segmentLabel` would happily return the empty message as a
+ * segment's accessible name.
+ */
+export type DateSegmentName = Exclude<keyof DateSegmentLabels, "empty" | "filledMonth">;
+export type TimeSegmentName = Exclude<keyof TimeSegmentLabels, "empty" | "filledDayPeriod">;
+/**
+ * The `aria-valuetext` override for one segment, as an object to `v-bind`
+ * rather than a string to bind directly — and that is the whole point of it.
+ *
+ * Reka writes `aria-valuetext="Empty"` on an unfilled segment and the number
+ * on a filled one, and only the first is a hard-coded English literal: the
+ * second is `${valueNow}`, and the month's `"3 - March"` takes its month name
+ * from the field's own `locale`. So this replaces exactly the empty case and
+ * leaves the rest alone. Binding `:aria-valuetext` directly could not do that
+ * — Vue merges a fallthrough `undefined` over Reka's value and *removes* the
+ * attribute, so a filled segment would lose the number it is there to read
+ * out. An absent key merges as nothing at all, which is what `optional()`
+ * exists for elsewhere and what returning `{}` does here.
+ *
+ * Emptiness is read off the digits in the segment's own displayed value, which
+ * is sound in both directions for these six parts: every locale's placeholder
+ * for them is letters (`mm`, `jj`, `aaaa`) and every value they can hold is
+ * digits. The two parts where that would not hold are the two excluded above.
+ */
+export declare function emptySegmentValueText(part: string, value: string, empty: string): {
+    "aria-valuetext"?: string;
+};
+/**
+ * Whether a part named by Reka's `segments` slot is one this slice names.
+ *
+ * A guard rather than an index, because the slot also yields `literal` — the
+ * slashes and colons between the segments, which Reka renders `aria-hidden`
+ * and which must stay unnamed — and `timeZoneName`, which none of these five
+ * controls can produce: their values parse through `parseDate`, `parseTime` and
+ * `parseDateTime`, none of which yields a zoned value, and no prop on any of
+ * them accepts a zone. Reka's `"timezone, "` is therefore unreachable from
+ * here, and a key for it would be a key nothing could ever render.
+ */
+export declare function isDateSegmentPart(part: string): part is DateSegmentName;
+/** Whether a part named by Reka's `segments` slot belongs to the clock half. */
+export declare function isTimeSegmentPart(part: string): part is TimeSegmentName;
+/**
+ * Everything the calendar popover says that is not a date: the panel's own
+ * name, the button that opens it, and the two that page the months.
+ *
+ * `calendar` is Reka's `CalendarRoot`/`RangeCalendarRoot` `calendarLabel` prop,
+ * whose default is the string `"Event Date"` — a name for somebody else's
+ * application, published both as the grid container's `aria-label` and inside a
+ * visually-hidden live region that a screen reader reads on every month change.
+ * It is a documented prop rather than a hard-coded literal, so it is the one
+ * name in this file that is set rather than overridden.
+ *
+ * `previousMonth` and `nextMonth` do replace literals: Reka writes
+ * `"Previous page"` and `"Next page"` on those two buttons, which is both
+ * English and wrong — what they move is a month.
+ */
+export interface CalendarPanelLabels {
+    /** The calendar's own name, read before the month and year on entering it. */
+    readonly calendar: string;
+    /** The button in the field that opens the calendar popover. */
+    readonly openCalendar: string;
+    /** The button that pages the calendar back one month. */
+    readonly previousMonth: string;
+    /** The button that pages the calendar on one month. */
+    readonly nextMonth: string;
+}
+/** Loom's English for the calendar popover. See `DATE_SEGMENT_LABELS`. */
+export declare const CALENDAR_PANEL_LABELS: CalendarPanelLabels;
+/**
+ * Which part of a chosen span one calendar cell plays, handed to the cell's
+ * label rather than resolved into words by the control.
+ *
+ * Four sibling keys and a joiner would be four phrases a translator cannot
+ * reorder around the date they qualify — and in several languages the qualifier
+ * does not follow the date at all. One argument carrying the variant is what
+ * keeps the whole cell name one sentence the host writes.
+ */
+export type RangeCellPart = "start" | "end" | "both" | "within";
+/**
+ * The accessible name of one day in a range calendar, shared by both range
+ * controls because they say it identically and from identical facts — a day
+ * and its part in the span. `DateTimeRangePicker`'s cells carry no time: the
+ * cell *is* a day, and choosing it moves only the day.
+ *
+ * The two controls' other strings are not shared, because they differ in words
+ * and in facts. This one does neither, and a translator writing it twice would
+ * be writing it twice for no reason.
+ */
+export interface RangeCellLabels {
+    /**
+     * One calendar cell's accessible name, which replaces the one Reka writes
+     * rather than adding to it: a cell's part in the range has to arrive *with*
+     * the date, and an element has no second slot for a name.
+     *
+     * `part` is `undefined` for a day with no part in the range at all.
+     */
+    readonly cell: LabelOf<{
+        locale: string;
+        date: DateValue;
+        part: RangeCellPart | undefined;
+    }>;
+}
+/**
+ * Loom's English for a range calendar's cells. The three fills that carry the
+ * first day, the last and the ones between are three shades of one colour,
+ * which survives neither a colour deficiency nor forced-colors mode — naming
+ * the part is what tells them apart, and it is what makes a one-day span say so
+ * once rather than announce itself twice as two different things.
+ */
+export declare const RANGE_CELL_LABELS: RangeCellLabels;
+/**
+ * A month name in the control's locale, for use in `aria-valuetext`.
+ *
+ * Exported so a host building a partial vocabulary can call it from their own
+ * `filledMonth` override rather than formatting from scratch — the same reason
+ * `formatFullDay` is exported.
+ */
+export declare function monthName(locale: string, month: number): string;
+/**
+ * A whole day written out — weekday, day, month and year — in the control's
+ * locale, which is the half of a range cell's name that is not a qualifier.
+ *
+ * Exported because both range controls' English defaults need it and neither
+ * should own it; a host replacing those defaults formats with whatever their
+ * own application already uses and never calls this.
+ */
+export declare function formatFullDay(locale: string, date: DateValue): string;
+//# sourceMappingURL=date-labels.d.ts.map

package/dist/lib/date-labels.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"date-labels.d.ts","sourceRoot":"","sources":["../../src/lib/date-labels.ts"],"names":[],"mappings":"AAAA,OAAO,EAAoB,KAAK,SAAS,EAAE,MAAM,yBAAyB,CAAC;AAC3E,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,UAAU,CAAC;AAExC;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AAEH;;;;;;;;;;;;;;;;GAgBG;AACH,MAAM,WAAW,iBAAiB;IAChC,yCAAyC;IACzC,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,gCAAgC;IAChC,QAAQ,CAAC,GAAG,EAAE,MAAM,CAAC;IACrB,wBAAwB;IACxB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB;;;OAGG;IACH,QAAQ,CAAC,GAAG,EAAE,MAAM,CAAC;IACrB;;;;;;;;;;;;OAYG;IACH,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB;;;;;;;;;;;;;;;;;OAiBG;IACH,QAAQ,CAAC,WAAW,EAAE,OAAO,CAAC;QAAE,KAAK,EAAE,MAAM,CAAC;QAAC,MAAM,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;CAClE;AAED;;;;GAIG;AACH,eAAO,MAAM,mBAAmB,EAAE,iBAkBjC,CAAC;AAEF;;;;;;;GAOG;AACH,MAAM,WAAW,iBAAiB;IAChC,wBAAwB;IACxB,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,0BAA0B;IAC1B,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;IACxB,+EAA+E;IAC/E,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;IACxB,6DAA6D;IAC7D,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAC3B,oGAAoG;IACpG,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB;;;;;;;;;;;;;;OAcG;IACH,QAAQ,CAAC,eAAe,EAAE,OAAO,CAAC;QAAE,SAAS,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;CAC1D;AAED,uEAAuE;AACvE,eAAO,MAAM,mBAAmB,EAAE,iBAUjC,CAAC;AAEF;;;;;;;;;GASG;AACH,MAAM,MAAM,eAAe,GAAG,OAAO,CAAC,MAAM,iBAAiB,EAAE,OAAO,GAAG,aAAa,CAAC,CAAC;AACxF,MAAM,MAAM,eAAe,GAAG,OAAO,CAAC,MAAM,iBAAiB,EAAE,OAAO,GAAG,iBAAiB,CAAC,CAAC;AAqB5F;;;;;;;;;;;;;;;;;;GAkBG;AACH,wBAAgB,qBAAqB,CACnC,IAAI,EAAE,MAAM,EACZ,KAAK,EAAE,MAAM,EACb,KAAK,EAAE,MAAM,GACZ;IAAE,gBAAgB,CAAC,EAAE,MAAM,CAAA;CAAE,CAE/B;AAED;;;;;;;;;;GAUG;AACH,wBAAgB,iBAAiB,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI,IAAI,eAAe,CAEvE;AAED,gFAAgF;AAChF,wBAAgB,iBAAiB,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI,IAAI,eAAe,CAEvE;AAED;;;;;;;;;;;;;;GAcG;AACH,MAAM,WAAW,mBAAmB;IAClC,8EAA8E;IAC9E,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,+DAA+D;IAC/D,QAAQ,CAAC,YAAY,EAAE,MAAM,CAAC;IAC9B,yDAAyD;IACzD,QAAQ,CAAC,aAAa,EAAE,MAAM,CAAC;IAC/B,uDAAuD;IACvD,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;CAC5B;AAED,0EAA0E;AAC1E,eAAO,MAAM,qBAAqB,EAAE,mBAKnC,CAAC;AAEF;;;;;;;;GAQG;AACH,MAAM,MAAM,aAAa,GAAG,OAAO,GAAG,KAAK,GAAG,MAAM,GAAG,QAAQ,CAAC;AAEhE;;;;;;;;;GASG;AACH,MAAM,WAAW,eAAe;IAC9B;;;;;;OAMG;IACH,QAAQ,CAAC,IAAI,EAAE,OAAO,CAAC;QACrB,MAAM,EAAE,MAAM,CAAC;QACf,IAAI,EAAE,SAAS,CAAC;QAChB,IAAI,EAAE,aAAa,GAAG,SAAS,CAAC;KACjC,CAAC,CAAC;CACJ;AAED;;;;;;GAMG;AACH,eAAO,MAAM,iBAAiB,EAAE,eAQ/B,CAAC;AAaF;;;;;;GAMG;AACH,wBAAgB,SAAS,CAAC,MAAM,EAAE,MAAM,EAAE,KAAK,EAAE,MAAM,GAAG,MAAM,CAQ/D;AAED;;;;;;;GAOG;AACH,wBAAgB,aAAa,CAAC,MAAM,EAAE,MAAM,EAAE,IAAI,EAAE,SAAS,GAAG,MAAM,CAYrE"}

package/dist/lib/date-labels.js

@@ -0,0 +1,157 @@
+import { getLocalTimeZone as $ad063034c8620db8$export$aa8b41735afcabd2 } from "../node_modules/.pnpm/@internationalized_date@3.12.3/node_modules/@internationalized/date/dist/private/queries.js";
+//#region src/lib/date-labels.ts
+/**
+* Loom's English for the date segments, co-located so it tree-shakes with the
+* controls that use it, and exported so a host can build a partial vocabulary
+* against the real thing rather than a transcription of it.
+*/
+var DATE_SEGMENT_LABELS = {
+	month: "Month",
+	day: "Day",
+	year: "Year",
+	era: "Era",
+	empty: "Not set",
+	filledMonth: ({ value, locale }) => {
+		const name = monthName(locale, value);
+		return `${String(value)} - ${name}`;
+	}
+};
+/** Loom's English for the time segments. See `DATE_SEGMENT_LABELS`. */
+var TIME_SEGMENT_LABELS = {
+	hour: "Hour",
+	minute: "Minute",
+	second: "Second",
+	dayPeriod: "AM or PM",
+	empty: "Not set",
+	filledDayPeriod: ({ dayPeriod }) => dayPeriod
+};
+var DATE_SEGMENT_PARTS = /* @__PURE__ */ new Set([
+	"month",
+	"day",
+	"year",
+	"era"
+]);
+var TIME_SEGMENT_PARTS = /* @__PURE__ */ new Set([
+	"hour",
+	"minute",
+	"second",
+	"dayPeriod"
+]);
+/**
+* The six segments Reka reports as `aria-valuetext="Empty"` when they hold
+* nothing — and, not by coincidence, the six that render as digits when they
+* hold something. `dayPeriod` and `era` are absent because Reka never writes
+* "Empty" on either: an unset `dayPeriod` reads `AM` and an unset `era` reads
+* the placeholder's own era, both of which are already the locale's words.
+*/
+var EMPTIABLE_SEGMENT_PARTS = /* @__PURE__ */ new Set([
+	"day",
+	"month",
+	"year",
+	"hour",
+	"minute",
+	"second"
+]);
+/**
+* The `aria-valuetext` override for one segment, as an object to `v-bind`
+* rather than a string to bind directly — and that is the whole point of it.
+*
+* Reka writes `aria-valuetext="Empty"` on an unfilled segment and the number
+* on a filled one, and only the first is a hard-coded English literal: the
+* second is `${valueNow}`, and the month's `"3 - March"` takes its month name
+* from the field's own `locale`. So this replaces exactly the empty case and
+* leaves the rest alone. Binding `:aria-valuetext` directly could not do that
+* — Vue merges a fallthrough `undefined` over Reka's value and *removes* the
+* attribute, so a filled segment would lose the number it is there to read
+* out. An absent key merges as nothing at all, which is what `optional()`
+* exists for elsewhere and what returning `{}` does here.
+*
+* Emptiness is read off the digits in the segment's own displayed value, which
+* is sound in both directions for these six parts: every locale's placeholder
+* for them is letters (`mm`, `jj`, `aaaa`) and every value they can hold is
+* digits. The two parts where that would not hold are the two excluded above.
+*/
+function emptySegmentValueText(part, value, empty) {
+	return EMPTIABLE_SEGMENT_PARTS.has(part) && !/\d/.test(value) ? { "aria-valuetext": empty } : {};
+}
+/**
+* Whether a part named by Reka's `segments` slot is one this slice names.
+*
+* A guard rather than an index, because the slot also yields `literal` — the
+* slashes and colons between the segments, which Reka renders `aria-hidden`
+* and which must stay unnamed — and `timeZoneName`, which none of these five
+* controls can produce: their values parse through `parseDate`, `parseTime` and
+* `parseDateTime`, none of which yields a zoned value, and no prop on any of
+* them accepts a zone. Reka's `"timezone, "` is therefore unreachable from
+* here, and a key for it would be a key nothing could ever render.
+*/
+function isDateSegmentPart(part) {
+	return DATE_SEGMENT_PARTS.has(part);
+}
+/** Whether a part named by Reka's `segments` slot belongs to the clock half. */
+function isTimeSegmentPart(part) {
+	return TIME_SEGMENT_PARTS.has(part);
+}
+/** Loom's English for the calendar popover. See `DATE_SEGMENT_LABELS`. */
+var CALENDAR_PANEL_LABELS = {
+	calendar: "Calendar",
+	openCalendar: "Open calendar",
+	previousMonth: "Previous month",
+	nextMonth: "Next month"
+};
+/**
+* Loom's English for a range calendar's cells. The three fills that carry the
+* first day, the last and the ones between are three shades of one colour,
+* which survives neither a colour deficiency nor forced-colors mode — naming
+* the part is what tells them apart, and it is what makes a one-day span say so
+* once rather than announce itself twice as two different things.
+*/
+var RANGE_CELL_LABELS = { cell: ({ locale, date, part }) => {
+	const full = formatFullDay(locale, date);
+	if (part === "both") return `${full}, the whole range, first and last day`;
+	if (part === "start") return `${full}, first day of the range`;
+	if (part === "end") return `${full}, last day of the range`;
+	return part === "within" ? `${full}, within the range` : full;
+} };
+var dayFormatters = /* @__PURE__ */ new Map();
+var monthFormatters = /* @__PURE__ */ new Map();
+/**
+* A month name in the control's locale, for use in `aria-valuetext`.
+*
+* Exported so a host building a partial vocabulary can call it from their own
+* `filledMonth` override rather than formatting from scratch — the same reason
+* `formatFullDay` is exported.
+*/
+function monthName(locale, month) {
+	let formatter = monthFormatters.get(locale);
+	if (!formatter) {
+		formatter = new Intl.DateTimeFormat(locale, { month: "long" });
+		monthFormatters.set(locale, formatter);
+	}
+	return formatter.format(new Date(2026, month - 1, 1));
+}
+/**
+* A whole day written out — weekday, day, month and year — in the control's
+* locale, which is the half of a range cell's name that is not a qualifier.
+*
+* Exported because both range controls' English defaults need it and neither
+* should own it; a host replacing those defaults formats with whatever their
+* own application already uses and never calls this.
+*/
+function formatFullDay(locale, date) {
+	let formatter = dayFormatters.get(locale);
+	if (!formatter) {
+		formatter = new Intl.DateTimeFormat(locale, {
+			weekday: "long",
+			day: "numeric",
+			month: "long",
+			year: "numeric"
+		});
+		dayFormatters.set(locale, formatter);
+	}
+	return formatter.format(date.toDate($ad063034c8620db8$export$aa8b41735afcabd2()));
+}
+//#endregion
+export { CALENDAR_PANEL_LABELS, DATE_SEGMENT_LABELS, RANGE_CELL_LABELS, TIME_SEGMENT_LABELS, emptySegmentValueText, formatFullDay, isDateSegmentPart, isTimeSegmentPart, monthName };
+
+//# sourceMappingURL=date-labels.js.map

package/dist/lib/date-labels.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"date-labels.js","names":[],"sources":["../../src/lib/date-labels.ts"],"sourcesContent":["import { getLocalTimeZone, type DateValue } from \"@internationalized/date\";\nimport type { LabelOf } from \"./labels\";\n\n/**\n * The four slices the five date and time controls share, and the one decision\n * behind putting them here rather than five times over.\n *\n * Every other component in the library declares its own bag beside its own\n * markup, because its vocabulary is its own. These five do not have five\n * vocabularies: `DatePicker`, `DateTimePicker`, `DateRangePicker` and\n * `DateTimeRangePicker` all say *Open calendar*, *Previous month* and *Next\n * month*, and all five name the parts of a segmented field with the same\n * words — the words are Reka UI's `useDateField` and `CalendarRoot` speaking,\n * one implementation underneath all five. Declared per component that would be\n * fifty-two keys with the same twelve strings written four times, and a\n * translator doing the same work four times to make one language complete.\n *\n * **Sliced by what a control actually says, not merged into one family bag.**\n * A `TimePicker` has no calendar and never renders a month or a year, so it\n * registers `timeSegments` alone: its documented vocabulary is four keys, and a\n * consumer importing only that control ships only those four strings. One\n * shared bag for the whole family would have made every one of the five carry\n * all twenty, and would have printed keys on `TimePicker`'s API page that it\n * has no element to put them on.\n *\n * What is deliberately *not* shared is the two range controls' half-group names\n * and status lines. They name the same concepts with different words (`Start\n * date` against `Start date and time`) and from different facts (a count of\n * whole days against a signed duration in minutes), so a shared key would have\n * to be a sentence that is never true of both. Their calendar cells' names are\n * shared, because those differ in neither.\n */\n\n/**\n * The names Reka UI's `useDateField` writes onto the day, month, year and era\n * segments — `\"day,\"`, `\"month, \"`, `\"year, \"`, `\"era\"`, each with the spacing\n * of a string it meant to concatenate.\n *\n * There is no prop for any of them. A binding on Loom's side reaches the\n * segment as a fallthrough attribute, which Vue merges onto the rendered vnode\n * *after* Reka's own render function produced it, and `mergeProps` is\n * last-write-wins for everything that is not `class`, `style` or `on*` — so\n * these replace Reka's rather than competing with it. Leave one unset and the\n * segment is not unnamed, it is named in English, which is the failure this\n * seam exists to close.\n *\n * Loom's defaults differ from Reka's by their capitalisation, which is what\n * lets a test assert *whose* string reached the DOM rather than merely what it\n * said.\n */\nexport interface DateSegmentLabels {\n  /** The month segment of a date field. */\n  readonly month: string;\n  /** The day-of-month segment. */\n  readonly day: string;\n  /** The year segment. */\n  readonly year: string;\n  /**\n   * The era segment, which most locales never render — `ja-JP-u-ca-japanese`\n   * is the ordinary case that does.\n   */\n  readonly era: string;\n  /**\n   * What a segment with nothing in it yet reports as its value, replacing the\n   * `aria-valuetext=\"Empty\"` Reka writes on an unfilled day, month or year.\n   *\n   * A segment shows the locale's own placeholder — `mm`, `jj`, `aaaa` — while\n   * announcing this instead, so it is the one word standing between a fully\n   * localised date field and a reader who is told \"Empty\" in English.\n   *\n   * Present on this slice *and* on `TimeSegmentLabels` rather than shared\n   * between them, for the reason the slices exist at all: a `TimePicker`\n   * registers no `dateSegments`, and a key it could only reach through the\n   * date half would be a key it could not set.\n   */\n  readonly empty: string;\n  /**\n   * What a filled month segment announces as its value, replacing the\n   * `aria-valuetext` Reka builds inside `useDateField`.\n   *\n   * Reka writes `\"5 - May\"` — the numeric month, a hard-coded `\" - \"`, and\n   * the month name from `Intl.DateTimeFormat`. The name is locale-aware, but\n   * the format is not: Japanese writes `\"5月\"`, Vietnamese `\"tháng 5\"`, and\n   * neither separates the two parts with a hyphen. A `LabelOf` hands the\n   * host the month number and the locale so they can compose the string their\n   * language needs, using `Intl.DateTimeFormat` for the name and arranging the\n   * parts in the right order.\n   *\n   * A `LabelOf` rather than a plain string, for the same reason\n   * `RangeCellLabels.cell` is one: the month name depends on the locale, and\n   * a string that did not receive the locale could not produce it. The host\n   * decides the format — Loom's English default matches Reka's output so that\n   * nothing changes for a consumer who does not override it.\n   */\n  readonly filledMonth: LabelOf<{ value: number; locale: string }>;\n}\n\n/**\n * Loom's English for the date segments, co-located so it tree-shakes with the\n * controls that use it, and exported so a host can build a partial vocabulary\n * against the real thing rather than a transcription of it.\n */\nexport const DATE_SEGMENT_LABELS: DateSegmentLabels = {\n  month: \"Month\",\n  day: \"Day\",\n  year: \"Year\",\n  era: \"Era\",\n  // \"Not set\" rather than Reka's own \"Empty\", and the difference is load-bearing\n  // in the same way the capitalisation of the names above is: it is what lets a\n  // test assert whose string reached the DOM. It also reads better spoken — a\n  // reader is being told this field has no value yet, not that it is blank.\n  empty: \"Not set\",\n  // Matches Reka's `\"5 - May\"` format for English. The month name comes from\n  // `Intl.DateTimeFormat` via the cached `monthFormatters` map, which avoids\n  // reconstructing the formatter on every render. A host overrides this to\n  // change the format — Japanese `\"5月\"`, Vietnamese `\"tháng 5\"`, etc.\n  filledMonth: ({ value, locale }) => {\n    const name = monthName(locale, value);\n    return `${String(value)} - ${name}`;\n  },\n};\n\n/**\n * The same, for the clock half of a segmented field: Reka writes `\"hour, \"`,\n * `\"minute, \"`, `\"second, \"` and `\"AM/PM\"`, and offers a prop for none of them.\n *\n * `dayPeriod` is spelled `AM or PM` rather than `AM/PM` so that it reads as\n * words when it is spoken, and so the capitalisation trick above still works on\n * the one segment whose name Reka already capitalises.\n */\nexport interface TimeSegmentLabels {\n  /** The hour segment. */\n  readonly hour: string;\n  /** The minute segment. */\n  readonly minute: string;\n  /** The seconds segment, which only a control at second granularity renders. */\n  readonly second: string;\n  /** The AM/PM segment, which only a 12-hour field renders. */\n  readonly dayPeriod: string;\n  /** What an hour, minute or second with nothing in it yet reports. See `DateSegmentLabels.empty`. */\n  readonly empty: string;\n  /**\n   * What a filled day-period segment announces as its value, replacing the\n   * `aria-valuetext` Reka writes inside `useDateField`.\n   *\n   * Reka writes `segmentValues.dayPeriod ?? \"AM\"` — always `\"AM\"` or `\"PM\"`,\n   * produced by its own hour-cycle logic (`hour >= 12 ? \"PM\" : \"AM\"`) rather\n   * than by `Intl.DateTimeFormat`. A host who has localised every other string\n   * in the library still hears Latin-script \"AM\"/\"PM\" from this segment, which\n   * is the defect this key exists to close.\n   *\n   * A `LabelOf` rather than a plain string, because the period name depends on\n   * the locale: Arabic writes `\"ص\"`/`\"م\"`, Japanese `\"午前\"`/`\"午後\"`, and a\n   * plain string could not carry that decision. Loom's English default returns\n   * `dayPeriod` unchanged, which is correct for Latin-script locales.\n   */\n  readonly filledDayPeriod: LabelOf<{ dayPeriod: string }>;\n}\n\n/** Loom's English for the time segments. See `DATE_SEGMENT_LABELS`. */\nexport const TIME_SEGMENT_LABELS: TimeSegmentLabels = {\n  hour: \"Hour\",\n  minute: \"Minute\",\n  second: \"Second\",\n  dayPeriod: \"AM or PM\",\n  empty: \"Not set\",\n  // The identity function for English: Reka's `\"AM\"`/`\"PM\"` are correct for\n  // Latin-script locales. A host localising to Arabic, Japanese, etc. overrides\n  // this to return the locale's own period names.\n  filledDayPeriod: ({ dayPeriod }) => dayPeriod,\n};\n\n/**\n * The parts each slice actually names — every key of its bag except `empty`,\n * which is a message *about* a segment rather than the name of one.\n *\n * Both the type and the set below are written out rather than derived from the\n * bags, which is what they were before `empty` joined them. Derived, the guards\n * would answer `true` for `\"empty\"` and narrow a part to a key that names no\n * element, and `segmentLabel` would happily return the empty message as a\n * segment's accessible name.\n */\nexport type DateSegmentName = Exclude<keyof DateSegmentLabels, \"empty\" | \"filledMonth\">;\nexport type TimeSegmentName = Exclude<keyof TimeSegmentLabels, \"empty\" | \"filledDayPeriod\">;\n\nconst DATE_SEGMENT_PARTS = new Set<DateSegmentName>([\"month\", \"day\", \"year\", \"era\"]);\nconst TIME_SEGMENT_PARTS = new Set<TimeSegmentName>([\"hour\", \"minute\", \"second\", \"dayPeriod\"]);\n\n/**\n * The six segments Reka reports as `aria-valuetext=\"Empty\"` when they hold\n * nothing — and, not by coincidence, the six that render as digits when they\n * hold something. `dayPeriod` and `era` are absent because Reka never writes\n * \"Empty\" on either: an unset `dayPeriod` reads `AM` and an unset `era` reads\n * the placeholder's own era, both of which are already the locale's words.\n */\nconst EMPTIABLE_SEGMENT_PARTS = new Set<string>([\n  \"day\",\n  \"month\",\n  \"year\",\n  \"hour\",\n  \"minute\",\n  \"second\",\n]);\n\n/**\n * The `aria-valuetext` override for one segment, as an object to `v-bind`\n * rather than a string to bind directly — and that is the whole point of it.\n *\n * Reka writes `aria-valuetext=\"Empty\"` on an unfilled segment and the number\n * on a filled one, and only the first is a hard-coded English literal: the\n * second is `${valueNow}`, and the month's `\"3 - March\"` takes its month name\n * from the field's own `locale`. So this replaces exactly the empty case and\n * leaves the rest alone. Binding `:aria-valuetext` directly could not do that\n * — Vue merges a fallthrough `undefined` over Reka's value and *removes* the\n * attribute, so a filled segment would lose the number it is there to read\n * out. An absent key merges as nothing at all, which is what `optional()`\n * exists for elsewhere and what returning `{}` does here.\n *\n * Emptiness is read off the digits in the segment's own displayed value, which\n * is sound in both directions for these six parts: every locale's placeholder\n * for them is letters (`mm`, `jj`, `aaaa`) and every value they can hold is\n * digits. The two parts where that would not hold are the two excluded above.\n */\nexport function emptySegmentValueText(\n  part: string,\n  value: string,\n  empty: string,\n): { \"aria-valuetext\"?: string } {\n  return EMPTIABLE_SEGMENT_PARTS.has(part) && !/\\d/.test(value) ? { \"aria-valuetext\": empty } : {};\n}\n\n/**\n * Whether a part named by Reka's `segments` slot is one this slice names.\n *\n * A guard rather than an index, because the slot also yields `literal` — the\n * slashes and colons between the segments, which Reka renders `aria-hidden`\n * and which must stay unnamed — and `timeZoneName`, which none of these five\n * controls can produce: their values parse through `parseDate`, `parseTime` and\n * `parseDateTime`, none of which yields a zoned value, and no prop on any of\n * them accepts a zone. Reka's `\"timezone, \"` is therefore unreachable from\n * here, and a key for it would be a key nothing could ever render.\n */\nexport function isDateSegmentPart(part: string): part is DateSegmentName {\n  return DATE_SEGMENT_PARTS.has(part as DateSegmentName);\n}\n\n/** Whether a part named by Reka's `segments` slot belongs to the clock half. */\nexport function isTimeSegmentPart(part: string): part is TimeSegmentName {\n  return TIME_SEGMENT_PARTS.has(part as TimeSegmentName);\n}\n\n/**\n * Everything the calendar popover says that is not a date: the panel's own\n * name, the button that opens it, and the two that page the months.\n *\n * `calendar` is Reka's `CalendarRoot`/`RangeCalendarRoot` `calendarLabel` prop,\n * whose default is the string `\"Event Date\"` — a name for somebody else's\n * application, published both as the grid container's `aria-label` and inside a\n * visually-hidden live region that a screen reader reads on every month change.\n * It is a documented prop rather than a hard-coded literal, so it is the one\n * name in this file that is set rather than overridden.\n *\n * `previousMonth` and `nextMonth` do replace literals: Reka writes\n * `\"Previous page\"` and `\"Next page\"` on those two buttons, which is both\n * English and wrong — what they move is a month.\n */\nexport interface CalendarPanelLabels {\n  /** The calendar's own name, read before the month and year on entering it. */\n  readonly calendar: string;\n  /** The button in the field that opens the calendar popover. */\n  readonly openCalendar: string;\n  /** The button that pages the calendar back one month. */\n  readonly previousMonth: string;\n  /** The button that pages the calendar on one month. */\n  readonly nextMonth: string;\n}\n\n/** Loom's English for the calendar popover. See `DATE_SEGMENT_LABELS`. */\nexport const CALENDAR_PANEL_LABELS: CalendarPanelLabels = {\n  calendar: \"Calendar\",\n  openCalendar: \"Open calendar\",\n  previousMonth: \"Previous month\",\n  nextMonth: \"Next month\",\n};\n\n/**\n * Which part of a chosen span one calendar cell plays, handed to the cell's\n * label rather than resolved into words by the control.\n *\n * Four sibling keys and a joiner would be four phrases a translator cannot\n * reorder around the date they qualify — and in several languages the qualifier\n * does not follow the date at all. One argument carrying the variant is what\n * keeps the whole cell name one sentence the host writes.\n */\nexport type RangeCellPart = \"start\" | \"end\" | \"both\" | \"within\";\n\n/**\n * The accessible name of one day in a range calendar, shared by both range\n * controls because they say it identically and from identical facts — a day\n * and its part in the span. `DateTimeRangePicker`'s cells carry no time: the\n * cell *is* a day, and choosing it moves only the day.\n *\n * The two controls' other strings are not shared, because they differ in words\n * and in facts. This one does neither, and a translator writing it twice would\n * be writing it twice for no reason.\n */\nexport interface RangeCellLabels {\n  /**\n   * One calendar cell's accessible name, which replaces the one Reka writes\n   * rather than adding to it: a cell's part in the range has to arrive *with*\n   * the date, and an element has no second slot for a name.\n   *\n   * `part` is `undefined` for a day with no part in the range at all.\n   */\n  readonly cell: LabelOf<{\n    locale: string;\n    date: DateValue;\n    part: RangeCellPart | undefined;\n  }>;\n}\n\n/**\n * Loom's English for a range calendar's cells. The three fills that carry the\n * first day, the last and the ones between are three shades of one colour,\n * which survives neither a colour deficiency nor forced-colors mode — naming\n * the part is what tells them apart, and it is what makes a one-day span say so\n * once rather than announce itself twice as two different things.\n */\nexport const RANGE_CELL_LABELS: RangeCellLabels = {\n  cell: ({ locale, date, part }) => {\n    const full = formatFullDay(locale, date);\n    if (part === \"both\") return `${full}, the whole range, first and last day`;\n    if (part === \"start\") return `${full}, first day of the range`;\n    if (part === \"end\") return `${full}, last day of the range`;\n    return part === \"within\" ? `${full}, within the range` : full;\n  },\n};\n\n// One formatter per locale, kept, because a range calendar's cell label runs\n// forty-two to eighty-four times per render and `Intl.DateTimeFormat`'s\n// constructor is the expensive half of it. The map is bounded by the number of\n// locales an application actually renders, which is one in nearly every case.\nconst dayFormatters = new Map<string, Intl.DateTimeFormat>();\n\n// Same pattern, for the filled month segment's `aria-valuetext`. The default\n// `filledMonth` label calls this on every render, so caching the formatter\n// avoids the `Intl.DateTimeFormat` constructor cost each time.\nconst monthFormatters = new Map<string, Intl.DateTimeFormat>();\n\n/**\n * A month name in the control's locale, for use in `aria-valuetext`.\n *\n * Exported so a host building a partial vocabulary can call it from their own\n * `filledMonth` override rather than formatting from scratch — the same reason\n * `formatFullDay` is exported.\n */\nexport function monthName(locale: string, month: number): string {\n  let formatter = monthFormatters.get(locale);\n  if (!formatter) {\n    formatter = new Intl.DateTimeFormat(locale, { month: \"long\" });\n    monthFormatters.set(locale, formatter);\n  }\n  // `Date` months are 0-indexed; Loom months are 1-indexed (as in `DateValue.month`).\n  return formatter.format(new Date(2026, month - 1, 1));\n}\n\n/**\n * A whole day written out — weekday, day, month and year — in the control's\n * locale, which is the half of a range cell's name that is not a qualifier.\n *\n * Exported because both range controls' English defaults need it and neither\n * should own it; a host replacing those defaults formats with whatever their\n * own application already uses and never calls this.\n */\nexport function formatFullDay(locale: string, date: DateValue): string {\n  let formatter = dayFormatters.get(locale);\n  if (!formatter) {\n    formatter = new Intl.DateTimeFormat(locale, {\n      weekday: \"long\",\n      day: \"numeric\",\n      month: \"long\",\n      year: \"numeric\",\n    });\n    dayFormatters.set(locale, formatter);\n  }\n  return formatter.format(date.toDate(getLocalTimeZone()));\n}\n"],"mappings":";;;;;;;AAsGA,IAAa,sBAAyC;CACpD,OAAO;CACP,KAAK;CACL,MAAM;CACN,KAAK;CAKL,OAAO;CAKP,cAAc,EAAE,OAAO,aAAa;EAClC,MAAM,OAAO,UAAU,QAAQ,KAAK;EACpC,OAAO,GAAG,OAAO,KAAK,EAAE,KAAK;CAC/B;AACF;;AAwCA,IAAa,sBAAyC;CACpD,MAAM;CACN,QAAQ;CACR,QAAQ;CACR,WAAW;CACX,OAAO;CAIP,kBAAkB,EAAE,gBAAgB;AACtC;AAeA,IAAM,qCAAqB,IAAI,IAAqB;CAAC;CAAS;CAAO;CAAQ;AAAK,CAAC;AACnF,IAAM,qCAAqB,IAAI,IAAqB;CAAC;CAAQ;CAAU;CAAU;AAAW,CAAC;;;;;;;;AAS7F,IAAM,0CAA0B,IAAI,IAAY;CAC9C;CACA;CACA;CACA;CACA;CACA;AACF,CAAC;;;;;;;;;;;;;;;;;;;;AAqBD,SAAgB,sBACd,MACA,OACA,OAC+B;CAC/B,OAAO,wBAAwB,IAAI,IAAI,KAAK,CAAC,KAAK,KAAK,KAAK,IAAI,EAAE,kBAAkB,MAAM,IAAI,CAAC;AACjG;;;;;;;;;;;;AAaA,SAAgB,kBAAkB,MAAuC;CACvE,OAAO,mBAAmB,IAAI,IAAuB;AACvD;;AAGA,SAAgB,kBAAkB,MAAuC;CACvE,OAAO,mBAAmB,IAAI,IAAuB;AACvD;;AA6BA,IAAa,wBAA6C;CACxD,UAAU;CACV,cAAc;CACd,eAAe;CACf,WAAW;AACb;;;;;;;;AA6CA,IAAa,oBAAqC,EAChD,OAAO,EAAE,QAAQ,MAAM,WAAW;CAChC,MAAM,OAAO,cAAc,QAAQ,IAAI;CACvC,IAAI,SAAS,QAAQ,OAAO,GAAG,KAAK;CACpC,IAAI,SAAS,SAAS,OAAO,GAAG,KAAK;CACrC,IAAI,SAAS,OAAO,OAAO,GAAG,KAAK;CACnC,OAAO,SAAS,WAAW,GAAG,KAAK,sBAAsB;AAC3D,EACF;AAMA,IAAM,gCAAgB,IAAI,IAAiC;AAK3D,IAAM,kCAAkB,IAAI,IAAiC;;;;;;;;AAS7D,SAAgB,UAAU,QAAgB,OAAuB;CAC/D,IAAI,YAAY,gBAAgB,IAAI,MAAM;CAC1C,IAAI,CAAC,WAAW;EACd,YAAY,IAAI,KAAK,eAAe,QAAQ,EAAE,OAAO,OAAO,CAAC;EAC7D,gBAAgB,IAAI,QAAQ,SAAS;CACvC;CAEA,OAAO,UAAU,OAAO,IAAI,KAAK,MAAM,QAAQ,GAAG,CAAC,CAAC;AACtD;;;;;;;;;AAUA,SAAgB,cAAc,QAAgB,MAAyB;CACrE,IAAI,YAAY,cAAc,IAAI,MAAM;CACxC,IAAI,CAAC,WAAW;EACd,YAAY,IAAI,KAAK,eAAe,QAAQ;GAC1C,SAAS;GACT,KAAK;GACL,OAAO;GACP,MAAM;EACR,CAAC;EACD,cAAc,IAAI,QAAQ,SAAS;CACrC;CACA,OAAO,UAAU,OAAO,KAAK,OAAO,0CAAiB,CAAC,CAAC;AACzD"}