@doenet/v06-to-v07 0.7.26-dev.565 → 0.7.26-dev.566

package/{index-O78gHXM_.js → index-tiXXndOE.js}

@@ -38632,7 +38632,7 @@ class Indent {
 }
 const chrome$1 = "# Viewer chrome: buttons, panel headers, and other UI the reader interacts\n# with. Rendered on the main thread and selected by `uiLocale`.\n#\n# Message ids are lower-kebab-case Fluent identifiers, optionally with a\n# single `.attribute` suffix (`submit-button`, `answer-status.correct`).\n#\n# This catalog is the source of truth for every other locale: `lint:i18n`\n# rejects a translation that defines a key missing here. Run\n# `npm run codegen -w @doenet/i18n` after editing.\n\n\n## Answer submission — the check-work button and the status it reports.\n\nanswer-checking = Checking...\nanswer-submitting = Submitting...\n\n# Announced to a screen reader while the submission is in flight. Separate\n# from the button's own text, which is abbreviated.\nanswer-checking-status = Checking answer\nanswer-submitting-status = Submitting answer\n\nanswer-correct = Correct\nanswer-incorrect = Incorrect\n\n# Shown instead of a correctness verdict when the activity withholds\n# correctness: the response was recorded, nothing is claimed about it.\nanswer-response-saved = Response Saved\n\n# Partial credit. `-credit` is used when repeated attempts reduce the credit\n# available, `-correct` when they do not, and `-short` on a button too narrow\n# for a word.\nanswer-percent-credit = { $percent }% Credit\nanswer-percent-correct = { $percent }% Correct\nanswer-percent-short = { $percent } %\n\nmax-credit-available = Max credit available: { $percent }%\n\n# Fluent formats `{ $count }` with `Intl.NumberFormat`, so a four-digit\n# attempt count renders as \"1,000\" where the hand-built string said \"1000\".\n# That is the one place English output is not byte-identical to what this\n# replaced, and grouping is the locale-correct rendering, so it stands.\nattempts-remaining =\n    { $count ->\n        [0] no attempts remaining\n        [one] { $count } attempt remaining\n       *[other] { $count } attempts remaining\n    }\n\n# Appended to an input's accessible name once its response has been graded,\n# so a screen reader reports the verdict along with the field.\nvalidation-correct = (Correct)\nvalidation-incorrect = (Incorrect)\nvalidation-partially-correct = (Partially correct)\n\n# Tooltip on the badge that reports how many responses have been submitted to\n# one answer, shown only to a host that asked for it. `$answerId` is the\n# answer's authored name and is never translated.\nanswer-show-responses =\n    { $count ->\n        [one] Show { $count } response to { $answerId }\n       *[other] Show { $count } responses to { $answerId }\n    }\n\n\n## Disclosure panels\n\nfeedback-heading = Feedback\n\n# Follows a disclosure panel's own heading — \"Solution (click to open)\" — and\n# is shared by `<solution>`, `<hint>`, and a collapsible `<section>`. The whole\n# parenthetical is one message: where the word for open or close falls inside\n# it is the translator's business.\ncollapsible-click-to-open = (click to open)\ncollapsible-click-to-close = (click to close)\n\n# Placeholder inside a panel that has been opened before its contents have\n# arrived from the core. Shared by `<solution>` and a collapsible `<section>`.\ncollapsible-initializing = Initializing...\n\n# Tooltip on a footnote marker, naming what activating it will do.\nfootnote-show = Show footnote\nfootnote-hide = Hide footnote\n\n# Tooltip on the ⓘ affordance that reveals an input's description.\ndescription-more-information = more information\n\n\n## Controls\n\nslider-previous = Prev\nslider-next = Next\n\nkeyboard-open = Open Keyboard\nkeyboard-close = Close Keyboard\n\n# Accessible name of the button that drops one selected choice from an inline\n# `<choiceInput selectMultiple>`. The button itself is drawn as a bare cross,\n# so `$choice` — the choice's own text, which is never translated — is the\n# only thing that says which chip it belongs to.\nchoice-input-remove-choice = Remove { $choice }\n\n# Accessible names of a matrix input's size controls, whose visible labels are\n# the symbols `r-` `r+` `c-` `c+`.\nmatrix-remove-row = Remove row\nmatrix-add-row = Add row\nmatrix-remove-column = Remove column\nmatrix-add-column = Add column\n\n# Modes and actions of the subset-of-reals input's control strip. The button\n# that selects all of the reals is the symbol `R`, not a word, and stays in\n# place.\nsubset-add-remove-points = Add/Remove points\nsubset-toggle-points-intervals = Toggle points and intervals\nsubset-move-points = Move Points\nsubset-clear = Clear\n\n# Buttons that edit an orbital diagram: rows hold boxes, boxes hold up to\n# three spin arrows.\norbital-add-row = Add Row\norbital-remove-row = Remove Row\norbital-add-box = Add Box\norbital-remove-box = Remove Box\norbital-add-up-arrow = Add Up Arrow\norbital-add-down-arrow = Add Down Arrow\norbital-remove-arrow = Remove Arrow\n\n# Accessible name of the text field naming one row of an orbital diagram,\n# counting from 1.\norbital-row-label = Label for row { $row }\n\n# Labels the answer column of a pretzel exercise's grid.\npretzel-answer = Answer\n\n# Caption above the table a `<summaryStatistics>` renders. It used to name the\n# data column being summarized; the statistics now come from values written in\n# the document, so there is no column to name and the message takes no\n# placeable. The table's own headings (`mean`, `stdev`, `quartile1`, …) are the\n# statistic ids an author references, not prose, and stay in place.\n#\n# Every translation of the old message named the column inside the sentence —\n# «Resumen estadístico de { $column }» — so none of them survives the placeable\n# being dropped, and the key was removed from the other catalogs rather than\n# truncated to whatever precedes the connector. Those locales fall back to\n# English here until the caption is translated again.\nsummary-statistics-caption = Summary statistics\n\n\n## Math input\n\n# Accessible name of the popover that previews the typed expression, and of\n# the rendered expression inside it.\nmath-input-preview-region = math expression preview\nmath-input-preview = Preview\nmath-input-invalid-expression = Invalid expression:\n\n\n## Document status\n\n# Shown while the core is still starting up and nothing can be rendered yet.\nviewer-initializing = Initializing...\n\n\n## Errors\n\n# Prefixes an error message wherever one is shown in place of content: an\n# `<error>` the core reported, the error boundary's fallback, and the\n# placeholder left where a renderer chunk failed to load.\nerror-heading = Error\n\n# Follows the error's own message inside that box, saying where in the source\n# the error was found. $span selects the sentence — one line or a range of\n# them — as a key rather than a phrase, so a translation is free to reorder the\n# whole of it. $startLine and $endLine are line numbers, and arrive as text\n# rather than as numbers so that line 1234 is not grouped as \"1,234\": a line\n# number is an identifier, not a quantity.\nerror-found-at =\n    { $span ->\n        [line] Found on line { $startLine }.\n       *[lines] Found on lines { $startLine }–{ $endLine }.\n    }\n\n# Banner above a document that compiled with at least one error in it.\ndocument-contains-errors = This document contains errors!\n\n# Headings of the tooltip the editor shows over a squiggle, naming what kind\n# of diagnostic it is. `-information` and `-hint` are styled identically but\n# are two different words; `-hint` is unreachable today, since nothing Doenet\n# raises is an LSP hint, and is here so the set is complete.\ndiagnostic-heading-error = Error\ndiagnostic-heading-warning = Warning\ndiagnostic-heading-information = Info\ndiagnostic-heading-hint = Hint\n\n# Headings of the same tooltip over an accessibility diagnostic, which says\n# what kind of problem it is rather than how severe. Level 1 is a failure\n# against the WCAG AA success criteria; level 2 is Doenet's own advice, which\n# no standard requires.\naccessibility-heading-level-1 = WCAG AA Accessibility Violation\naccessibility-heading-level-2 = Accessibility alert\n\n# Shown in place of the document when a renderer threw and the error boundary\n# caught it.\nsomething-went-wrong = Something went wrong.\n\n# Shown in place of a single renderer whose code chunk never arrived.\nrenderer-load-failed = a renderer failed to load. Please reload the page.\n\n# Shown in place of the document when the core worker could not be started\n# after retries, rather than leaving the pane blank.\ncore-start-failed = This document could not be started. Please reload the page.\n\n# Replaces `core-start-failed` when several documents were starting at the\n# same time — counted across every same-origin tab, so not necessarily all on\n# the page the reader sees. Naming the contention keeps the reader from\n# concluding the service is broken.\ncore-start-failed-busy = This document could not be started. Several documents were starting at once, which can take longer on a slower device. Reloading the page may help once the other documents have finished.\n\n# Shown for a core-start failure the reader can still retry, next to the\n# button that does it (`core-start-retry`). It leaves out the advice to\n# reload that the messages above carry: the button is the cheaper action,\n# and a reader told to reload will reload the whole page — restarting every\n# other document on it, which is what produced the failure in the first\n# place on a page that was already busy.\ncore-start-failed-retry = This document could not be started.\n\n# The contended variant of `core-start-failed-retry`, named for the same\n# reason `core-start-failed-busy` is: a reader who is told that several\n# documents were starting at once has a reason to try again in a moment\n# rather than concluding the service is broken.\ncore-start-failed-busy-retry = This document could not be started. Several documents were starting at once, which can take longer on a slower device.\n\n# Label of the button that starts a failed document over without reloading\n# the page. Offered once per document; a retry that fails too falls back to\n# `core-start-failed` / `core-start-failed-busy`, which advise the reload.\ncore-start-retry = Try again\n\n# Shown beside a document that is on screen and working, when the host\n# answered `SPLICE.getState` with an error and so the document started\n# without the reader's saved work (#1741). The host's own wording follows\n# this lead-in, so it says what was lost rather than why.\nsaved-state-unavailable = Your saved work could not be loaded.\n";
 const content = '# Worker-generated content: style descriptions ("thick red line"), boolean\n# words, and other prose the core computes into the document. Selected by\n# `documentLocale`, which follows the content\'s language rather than the\n# reader\'s UI language.\n#\n# Message ids are lower-kebab-case Fluent identifiers, optionally with a\n# single `.attribute` suffix (`color.blue`, `noun.line-segment`).\n\n\n## Style vocabulary\n##\n## The words the style pipeline derives from a component\'s numeric and\n## enumerated style values. A word an author writes directly — `lineColorWord`,\n## `markerStyleWord`, and their siblings — passes through untranslated: the\n## author chose those words, and rewriting them would be a surprise. So does a\n## CSS named color asked for by name ("rebeccapurple"), which\n## `resolveColorWord` deliberately preserves.\n##\n## Every adjective here is handed `$gender`, the grammatical gender of the noun\n## it describes (see `noun-gender`), and `$role`, the syntactic position the\n## phrase it belongs to is going into. English has no agreement and ignores\n## both; a language that inflects selects on them.\n##\n## `$role` is one of:\n##\n##   standalone          the phrase stands on its own, which is where all but\n##                       the three below are\n##   border-clause       inside `style-border-clause`, behind its preposition\n##   background-clause   the background colour inside `style-text`, behind its\n##                       preposition\n##   text-clause         the text colour beside it, inside `style-text`\n##\n## The last three exist because those words are rendered in two places each —\n## once alone, as `borderStyleDescription`, `backgroundColor` and `textColor`\n## report them, and once embedded in a clause. A language that inflects for\n## case needs a different form in each, and no amount of `$gender` can say\n## which is wanted. Which case a position governs is the catalog\'s business:\n## `border-clause` is a dative in German, an instrumental in Russian and\n## Polish, and nothing at all in a language that does not inflect.\n\n# The canonical color families a color value resolves to.\ncolor =\n    .black = black\n    .white = white\n    .gray = gray\n    .red = red\n    .orange = orange\n    .yellow = yellow\n    .green = green\n    .cyan = cyan\n    .blue = blue\n    .purple = purple\n    .pink = pink\n    .brown = brown\n\n# Stroke widths. Only the extremes are named — a middling width is described by\n# its color alone.\nline-width =\n    .thick = thick\n    .thin = thin\n\n# Dash patterns. A solid stroke is described by its color alone.\nline-style =\n    .dashed = dashed\n    .dotted = dotted\n\n# Patterns a shape\'s interior can be filled with. A solid fill is described by\n# its color alone.\nfill-style =\n    .horizontal = horizontal lines\n    .vertical = vertical lines\n    .diagonal = diagonal lines\n    .backdiagonal = reverse diagonal lines\n    .dots = dots\n    .diamonds = diamonds\n\n# The things being described. The shapes a point can be drawn as ("square",\n# "cross") are nouns too: a point\'s description names its marker shape rather\n# than always saying "point".\nnoun =\n    .line = line\n    .line-segment = line segment\n    .ray = ray\n    .vector = vector\n    .curve = curve\n    .function = function\n    .slope-field = slope field\n    .vector-field = vector field\n    .parabola = parabola\n    .polyline = polyline\n    .polygon = polygon\n    .triangle = triangle\n    .rectangle = rectangle\n    .circle = circle\n    .region = region\n    .point = point\n    .square = square\n    .diamond = diamond\n    .cross = cross\n    .plus = plus\n\n# A regular polygon names its side count, so it is a message of its own rather\n# than one of `noun`\'s attributes.\n#\n# `$part` splits the noun where a language needs it split: `head` is the word\n# the adjectives attach to, `tail` a complement that follows them. English\n# folds the side count into the head and has no tail; Spanish says "polígono\n# regular" and puts "de 5 lados" after the adjectives, so that they stay beside\n# the noun they agree with. `style-with-noun` and `style-filled-with-noun`\n# place the two halves.\n#\n# `$numSides` is a real number, so it is formatted by the locale\'s own rules —\n# a 1000-gon reads "1,000-sided" here and "de 1000 lados" in Spanish. That is\n# the number-formatting policy in the README, and the one place a description\n# is not character-for-character what the pre-catalog code produced.\nnoun-regular-polygon =\n    { $part ->\n        [tail] { "" }\n       *[head] { $numSides }-sided regular polygon\n    }\n\n# The grammatical gender of the noun being described, passed to every adjective\n# describing it so that translations can agree. English has no grammatical\n# gender, so every noun answers the same and the answer goes unused.\n#\n# `$noun` is one of `noun`\'s attribute names, `regular-polygon` for the shape\n# `noun-regular-polygon` names, or the head of a phrase the description builds\n# without naming it as a noun: `border`, `fill`, `text`, or `background`. A\n# word this message does not list falls to its default gender — which is also\n# what an author\'s own `markerStyleWord` gets, since the catalog has never seen\n# it.\nnoun-gender = neuter\n\n\n## Style composition\n##\n## `$parts` names which pieces the style actually supplies, so that a\n## translation can order and inflect each combination on its own terms instead\n## of substituting into a fixed English frame. An absent piece is a different\n## branch, never an empty placeable.\n\n# The adjectives describing a stroke: its width, its dash pattern, and its\n# color. Also describes a shape\'s border, where the color is dropped when it\n# matches the fill it surrounds.\nstyle-stroke =\n    { $parts ->\n        [width-style-color] { $width } { $lineStyle } { $color }\n        [width-color] { $width } { $color }\n        [style-color] { $lineStyle } { $color }\n        [width-style] { $width } { $lineStyle }\n        [width] { $width }\n        [style] { $lineStyle }\n       *[color] { $color }\n    }\n\n# A style description followed by what it describes: "thick red line".\n#\n# `$nounTail` is the noun\'s trailing complement, for the nouns whose\n# translation splits around the adjectives (see `noun-regular-polygon`).\n# English has none today, so it only ever selects `noun` for itself — the other\n# variant is still what a partly-translated locale falls back to, and dropping\n# it would drop that locale\'s side count.\n#\n# The phrase it builds is never governed by anything, so its `$role` is always\n# `standalone`.\nstyle-with-noun =\n    { $parts ->\n        [noun-tail] { $description } { $noun } { $nounTail }\n       *[noun] { $description } { $noun }\n    }\n\n# The word marking a shape as filled.\n#\n# A key of its own, looked up by the code and handed to the messages below as\n# `$filled`, rather than literal text inside them: a language that inflects it\n# has to agree it with the shape. Referencing it from those messages would not\n# do — a term reference (`{ -filled }`) gets an empty scope and never sees\n# `$gender`, and a message reference resolves only inside its own bundle, so a\n# locale that translated `style-filled` but not this word would render the\n# reference literally instead of falling back to English.\n#\n# Said only of the shape itself, so its `$role` is always `standalone`.\nstyle-filled-word = filled\n\n# A filled shape, and the pattern its interior is drawn with, if any.\nstyle-filled =\n    { $parts ->\n        [pattern] { $filled } { $color } with { $pattern }\n       *[plain] { $filled } { $color }\n    }\n\n# The same, naming the shape: "filled blue circle with diamonds".\n#\n# The `-tail` variants carry the noun\'s trailing complement, as\n# `style-with-noun` does.\nstyle-filled-with-noun =\n    { $parts ->\n        [pattern] { $filled } { $color } { $noun } with { $pattern }\n        [plain-tail] { $filled } { $color } { $noun } { $nounTail }\n        [pattern-tail] { $filled } { $color } { $noun } { $nounTail } with { $pattern }\n       *[plain] { $filled } { $color } { $noun }\n    }\n\n# The border clause appended to a filled shape: "with a thick red border".\n#\n# `$parts` carries two distinctions English cares about: whether a fill pattern\n# was already mentioned, which makes this a further clause ("and") rather than\n# the first ("with"), and whether the surrounding description named the shape,\n# which is where English wants an article.\nstyle-border-clause =\n    { $parts ->\n        [with-article] with a { $border } border\n        [and] and { $border } border\n        [and-article] and a { $border } border\n       *[with] with { $border } border\n    }\n\n# How a shape\'s interior is filled, on its own: "blue diamonds".\nstyle-fill =\n    { $parts ->\n        [pattern] { $color } { $pattern }\n       *[plain] { $color }\n    }\n\nstyle-unfilled = unfilled\n\n# How a piece of text is styled: its color, and the background behind it.\n#\n# The only composition message with no `$role`: its two words sit in two\n# different positions, so they arrive already inflected for `text-clause` and\n# `background-clause` respectively and no one token would describe them both.\nstyle-text =\n    { $parts ->\n        [background] { $color } with a { $background } background\n       *[plain] { $color }\n    }\n\n# What `backgroundColor` answers when nothing is drawn behind the text.\nstyle-background-none = none\n\n\n## Boolean words\n##\n## What a `<boolean>` or `<booleanInput>` *displays*.\n##\n## Not what it parses or serializes. `true` and `false` are DoenetML syntax —\n## an author writes them in the source, `<award>` compares against them, and\n## saved state stores them — so they stay English everywhere, in every\n## language, exactly as `<` stays `<`. Only the word the reader sees moves.\n##\n## The consequence is that a value has two spellings in a translated document,\n## and both have to be accepted where one is read back in: see\n## `booleanFromWord` in the worker.\n\nboolean-true = true\nboolean-false = false\n\n\n## Answer buttons\n##\n## The default text on an answer\'s submit button. Only the *default* is\n## translated: an author who writes `submitLabel="Ready?"` gets "Ready?" in\n## every locale, because they chose those words for their document and a\n## translation of it is not Doenet\'s to make.\n\n# Shown when the answer will report whether the response was right.\nanswer-submit-label = Check Work\n\n# Shown when it will not — the reader submits, and is told nothing more.\nanswer-submit-label-no-correctness = Submit Response\n\n\n## Sectional blocks\n##\n## The word a sectional block calls itself, which the reader sees in its\n## heading and on a `<solution>`\'s reveal control. Keyed by the element the\n## author writes, so `<subsection>` and `<subsubsection>` share `.section` —\n## they are all called a section.\n##\n## An author who writes `renameTo` has named the block themselves, and that\n## name passes through in every language.\n\nsection-name =\n    .activity = Activity\n    .aside = Aside\n    .cascade = Cascade\n    .definition = Definition\n    .example = Example\n    .exercise = Exercise\n    .exercises = Exercises\n    .given-answer = Answer\n    .note = Note\n    .objectives = Objectives\n    .paragraphs = Paragraphs\n    .part = Part\n    .problem = Problem\n    .problems = Problems\n    .proof = Proof\n    .question = Question\n    .section = Section\n    .solution = Solution\n    .task = Task\n    .theorem = Theorem\n\n# The heading a section builds for itself: "Example 2", "Section 1.3: Limits".\n#\n# `$parts` names which pieces are present and whether a `<title>` follows, so\n# that a translation orders and punctuates each combination on its own terms\n# rather than substituting into an English frame. English puts the word first\n# and separates a title with a colon — or with a period when the heading is a\n# bare number — and none of that is a given.\n#\n# The `-title` variants end in the separator, because what follows them is the\n# title child, rendered separately. Fluent trims trailing whitespace, so the\n# separator is written as a string literal to keep its space.\n#\n# `$sectionNumber` arrives as text ("2", "1.3") rather than as a number: it is\n# an identifier made of counters, and it is not the catalog\'s to reformat.\nsection-title-prefix =\n    { $parts ->\n        [name] { $sectionName }\n        [number] { $sectionNumber }\n        [name-title] { $sectionName }{ ": " }\n        [number-title] { $sectionNumber }{ ". " }\n        [name-number-title] { $sectionName } { $sectionNumber }{ ": " }\n       *[name-number] { $sectionName } { $sectionNumber }\n    }\n\n# The heading a `<hint>` shows when the author gave it no `<title>`.\nhint-title = Hint\n\n\n## Tables and figures\n##\n## The name a `<table>` or `<figure>` gives itself, which the renderer sets in\n## bold at the head of the title or caption: "Table 2", "Figure 3". An\n## unnumbered one is named by the bare word.\n##\n## The word and the number are one message rather than a word the code\n## concatenates a number onto, so that a language which orders or punctuates\n## them differently can say so.\n##\n## `$enumeration` arrives as text rather than as a number: it identifies the\n## table, so the thousandth one is "Table 1000" and not "Table 1,000".\n##\n## The `-title` and `-caption` branches end in the separator joining the name\n## to the authored title or caption, which the renderer used to write as a\n## literal `": "` of its own. That child is arbitrary marked-up content\n## rendered after this string rather than an argument passed into it, so where\n## it sits is the one thing a translation cannot reorder — the same shape\n## `section-title-prefix` has.\n\n## The name a `<chart>` gives a series that the author did not label.\n##\n## This is not decoration: it is the text a screen reader announces on the\n## level between the chart and its marks, so a reader stopping there is told\n## which group they have reached. A bare number would be indistinguishable\n## from a value or a category, which are what the levels either side of it\n## announce.\n##\n## `$position` arrives as text rather than as a number, for the reason\n## `table-name`\'s `$enumeration` does: it identifies the series, so the\n## thousandth one is "series 1000" and not "series 1,000".\nchart-unlabeled-series =\n    series { $position }\n\ntable-name =\n    { $parts ->\n        [numbered] Table { $enumeration }\n        [numbered-title] Table { $enumeration }{ ": " }\n        [unnumbered-title] Table{ ": " }\n       *[unnumbered] Table\n    }\n\nfigure-name =\n    { $parts ->\n        [numbered] Figure { $enumeration }\n        [numbered-caption] Figure { $enumeration }{ ": " }\n        [unnumbered-caption] Figure{ ": " }\n       *[unnumbered] Figure\n    }\n\n\n## Paginator controls\n##\n## The strip of controls that steps through a `<paginator>`\'s pages. All three\n## words are author-overridable attributes, so only the default is translated.\n\npaginator-previous = Previous\npaginator-next = Next\npaginator-page = Page\n\n# The status between the two buttons: "Page 3 of 5".\n#\n# Composed in the worker rather than in the renderer so that the whole of it is\n# in one language: `$pageLabel` is the `pageLabel` attribute, which an author\n# may have written themselves, and the words joining it to the counts have to\n# sit beside it in the same tongue.\n#\n# The two counts arrive as text, for the same reason `$enumeration` does above.\npaginator-page-status = { $pageLabel } { $currentPage } of { $numPages }\n\n\n## Piecewise functions\n##\n## `<piecewiseFunction>` renders each branch\'s domain as mathematics and writes\n## these three words around it: "if 1 < x < 2 or 4 < x < 5", and "otherwise"\n## for the branch that catches what the others leave. The inequalities are\n## notation and stay as they are; these are prose, and are read aloud as prose.\n##\n## `or` is the only conjunction the core composes into content. Everything else\n## that reads as "a, b, and c" is a diagnostic, and those are joined by\n## `Intl.ListFormat` at the moment the reader\'s language is known rather than\n## by a catalog word (see `DiagnosticListArg`).\n\npiecewise-condition-or = or\n\n# Introduces the domain a branch applies on; the mathematics follows it.\npiecewise-condition-if = if\n\n# The last branch, which applies wherever none of the earlier ones do.\npiecewise-condition-otherwise = otherwise\n\n\n## Chemistry\n##\n## The names the chemistry components generate. Symbols (`H`, `Fe`), formulas,\n## and anything an author\'s `<award>` compares against by value stay as they\n## are; only what is displayed as prose is here.\n##\n## Element names are keyed by symbol, which is the identifier the atom database\n## is read through and is itself never translated.\n##\n## An element\'s periodic group, its phase at STP and its metal category are not\n## here. They are enumerated values an author\'s `<award>` compares against —\n## `$atom.groupName = Noble Gas` — and translating one would break that\n## comparison the moment a document declared a language (#1577).\n\nelement-name =\n    .h = Hydrogen\n    .he = Helium\n    .li = Lithium\n    .be = Beryllium\n    .b = Boron\n    .c = Carbon\n    .n = Nitrogen\n    .o = Oxygen\n    .f = Fluorine\n    .ne = Neon\n    .na = Sodium\n    .mg = Magnesium\n    .al = Aluminum\n    .si = Silicon\n    .p = Phosphorus\n    .s = Sulfur\n    .cl = Chlorine\n    .ar = Argon\n    .k = Potassium\n    .ca = Calcium\n    .sc = Scandium\n    .ti = Titanium\n    .v = Vanadium\n    .cr = Chromium\n    .mn = Manganese\n    .fe = Iron\n    .co = Cobalt\n    .ni = Nickel\n    .cu = Copper\n    .zn = Zinc\n    .ga = Gallium\n    .ge = Germanium\n    .as = Arsenic\n    .se = Selenium\n    .br = Bromine\n    .kr = Krypton\n    .rb = Rubidium\n    .sr = Strontium\n    .y = Yttrium\n    .zr = Zirconium\n    .nb = Niobium\n    .mo = Molybdenum\n    .tc = Technetium\n    .ru = Ruthenium\n    .rh = Rhodium\n    .pd = Palladium\n    .ag = Silver\n    .cd = Cadmium\n    .in = Indium\n    .sn = Tin\n    .sb = Antimony\n    .te = Tellurium\n    .i = Iodine\n    .xe = Xenon\n    .cs = Cesium\n    .ba = Barium\n    .la = Lanthanum\n    .ce = Cerium\n    .pr = Praseodymium\n    .nd = Neodymium\n    .pm = Promethium\n    .sm = Samarium\n    .eu = Europium\n    .gd = Gadolinium\n    .tb = Terbium\n    .dy = Dysprosium\n    .ho = Holmium\n    .er = Erbium\n    .tm = Thulium\n    .yb = Ytterbium\n    .lu = Lutetium\n    .hf = Hafnium\n    .ta = Tantalum\n    .w = Tungsten\n    .re = Rhenium\n    .os = Osmium\n    .ir = Iridium\n    .pt = Platinum\n    .au = Gold\n    .hg = Mercury\n    .tl = Thallium\n    .pb = Lead\n    .bi = Bismuth\n    .po = Polonium\n    .at = Astatine\n    .rn = Radon\n    .fr = Francium\n    .ra = Radium\n    .ac = Actinium\n    .th = Thorium\n    .pa = Protactinium\n    .u = Uranium\n    .np = Neptunium\n    .pu = Plutonium\n    .am = Americium\n    .cm = Curium\n    .bk = Berkelium\n    .cf = Californium\n    .es = Einsteinium\n    .fm = Fermium\n    .md = Mendelevium\n    .no = Nobelium\n    .lr = Lawrencium\n    .rf = Rutherfordium\n    .db = Dubnium\n    .sg = Seaborgium\n    .bh = Bohrium\n    .hs = Hassium\n    .mt = Meitnerium\n    .ds = Darmstadtium\n    .rg = Roentgenium\n    .cn = Copernicium\n    .nh = Nihonium\n    .fl = Flerovium\n    .mc = Moscovium\n    .lv = Livermorium\n    .ts = Tennessine\n    .og = Oganesson\n\n# The name an anion takes, for the elements that have one.\n#\n# English derives these — strip a trailing "ine", add "ide", with a small table\n# for the words that rule does not fit — but that is English morphology, not a\n# fact about anions. So each language supplies the names it uses. An element\n# with no entry here is called by its own name, which is also what the English\n# rule does for everything it does not match.\nelement-anion-name =\n    .h = Hydride\n    .c = Carbide\n    .n = Nitride\n    .o = Oxide\n    .f = Fluoride\n    .p = Phosphide\n    .s = Sulfide\n    .cl = Chloride\n    .br = Bromide\n    .i = Iodide\n    .at = Astatide\n    .ts = Tennesside\n\n# A transition metal\'s ion, named with its oxidation state: "Iron (II)".\n#\n# The Roman numeral is IUPAC notation and is the same in every language. Where\n# it sits and how it is punctuated is not, which is why this is a message and\n# not a suffix the code appends.\nion-name-oxidation-state = { $name } ({ $numeral })\n\n# Shown in place of a chemical symbol or formula that names nothing. Rendered\n# into mathematics as well as into text, so the brackets around it are added by\n# the code — inside `\\text{}` for the LaTeX form — and are not part of the\n# message.\nchemistry-invalid-symbol = Invalid Chemical Symbol\nchemistry-invalid-ionic-compound = Invalid Ionic Compound\n\n## Inputs embedded in math\n\n# Names the gap an input fills when it is drawn inside a typeset expression, so\n# that a screen reader reads "x equals blank plus 3" rather than skipping over\n# it. Written into the mathematics itself and never shown on screen, so keep it\n# to a word or two.\nmath-embedded-input-blank = blank\n\n# The same, when one expression has more than one gap, so that a reader can tell\n# which one they have reached.\nmath-embedded-input-blank-ordinal = blank { $ordinal } of { $total }\n';
-const diagnostics = '# Errors and warnings surfaced to the reader or author. Produced by the worker\n# but addressed to whoever is looking at the screen, so these are selected by\n# `uiLocale`, not `documentLocale`.\n#\n# Message ids are lower-kebab-case Fluent identifiers, optionally with a\n# single `.attribute` suffix (`invalid-attribute-value`).\n#\n# Reached by stable diagnostic code rather than by a literal `t("key")` call:\n# `DIAGNOSTIC_CODES` in `src/diagnostics.ts` maps `doenet-w0001` to the id\n# below, and `lint:i18n` treats that registry as the call site. Adding a\n# message here without registering a code for it fails the lint as an orphan.\n#\n# Translators: `through`, `endpoint`, `midpointOffset`, `numDimensions` and the\n# like are DoenetML attribute names. They are part of the language, not prose,\n# and must be left in English exactly as written.\n\n## `<lineSegment>`\n\n# $attributes is a list of attribute names; $attributesCount is its length.\nline-segment-attributes-ignored-with-endpoints =\n    { $attributesCount ->\n        [one] { $attributes } is ignored when two endpoints are specified\n       *[other] { $attributes } are ignored when two endpoints are specified\n    }\n\n# $attributes is a list of attribute names; $attributesCount is its length.\nline-segment-attributes-ignored-with-endpoint-and-midpoint =\n    { $attributesCount ->\n        [one] { $attributes } is ignored when an endpoint and a midpoint are both specified\n       *[other] { $attributes } are ignored when an endpoint and a midpoint are both specified\n    }\n\nline-segment-midpoint-offset-without-midpoint = midpointOffset has no effect without a midpoint\n\n## `<line>`\n\nline-points-undetermined-dimensions = Line through points of undetermined dimensions.\n\nline-points-too-few-dimensions = Line must be through points of at least two dimensions.\n\n# $variables is a bare enumeration of variable names, not an "and" list.\nline-points-depend-on-variables = Line is through points that depend on variables: { $variables }.\n\nline-equation-invalid-format = Invalid format for equation of line in variables { $variable1 } and { $variable2 }.\n\n## `<ray>`\n\nray-overprescribed-through = Ray is prescribed by through, endpoint, and direction.  Ignoring specified through.\n\nray-dimension-mismatch = numDimensions mismatch in ray.\n\n## `<vector>`\n\nvector-overprescribed-head = Vector is prescribed by head, tail, and displacement.  Ignoring specified head.\n\nvector-dimension-mismatch = numDimensions mismatch in vector.\n\n## Attracting and constraining\n\n# $component is the DoenetML tag of the child that was named, e.g. "polygon".\nattract-to-without-nearest-point = Cannot attract to a `<{ $component }>` as it doesn\'t have a nearestPoint state variable.\n\nconstrain-to-without-nearest-point = Cannot constrain to a `<{ $component }>` as it doesn\'t have a nearestPoint state variable.\n\nconstrain-to-interior-without-nearest-point = Cannot constrain to interior of a `<{ $component }>` as it doesn\'t have a nearestPoint state variable.\n\n## `<choiceInput>`\n\n# Translators: `labelPosition` is an attribute name and stays in English.\nchoice-input-label-position-ignored = labelPosition is ignored for non-inline choiceInput\n\n## Ordering children by index\n##\n## These name the component in prose rather than as a tag, matching how the\n## messages have always read. The component names stay in English; the nouns\n## around them are prose and should be translated.\n\nchoice-input-indices-count-mismatch = Ignoring indices specified for choiceInput as number of indices doesn\'t match number of choice children.\n\npretzel-indices-count-mismatch = Ignoring indices specified for problem as number of indices doesn\'t match number of problem children.\n\nshuffle-indices-count-mismatch = Ignoring indices specified for shuffle as number of indices doesn\'t match number of components.\n\n# $component is `choiceInput`, `pretzel` or `shuffle` — a DoenetML component\n# name, so it stays in English.\nindices-ignored-out-of-range = Ignoring indices specified for { $component } as some indices out of range.\n\npretzel-indices-repeated = Ignoring indices specified for pretzel as some indices are repeated.\n\npretzel-circuit-first-index = Ignoring indices specified for pretzel in circuit mode as the first index must be 1.\n\n## `<shuffle>` and `<sort>`\n\n# $component is `shuffle` or `sort`. These two components accept the same\n# children and fail the same ways, so they share their messages.\nstring-children-need-type = For `<{ $component }>` to work with string children, a `type` attribute must be specified.\n\n# $type is what the author wrote; math, text, number and boolean are attribute\n# values and stay in English.\ninvalid-type-defaulting-to-math = Invalid type { $type } for { $component } component. Must be one of math, text, number, or boolean. Defaulting to math.\n\n# Raised when `type` names something that is not one of the four readings. The\n# value is dropped rather than replaced by a guess, so the children are read as\n# though no type had been written. $type is what the author wrote.\ninvalid-type-ignored =\n    Invalid type { $type } for { $component } component. Must be one of math, text, number, or boolean. Ignoring it and reading the values as though no type had been given.\n\n# $value is the string child that could not be used.\nstring-not-valid-component-to-arrange = String "{ $value }" is not a valid component to { $component }. Ignoring.\n\n## Types and variables\n\ninvalid-type-defaulting-to-number = Invalid type { $type }, setting type to number.\n\ninvalid-variable-value = Invalid value of a variable: `{ $value }`\n\n## Variants\n\n# $index is what the author wrote, reproduced verbatim rather than as a number:\n# it reached this message precisely because it was not one.\nvariant-index-must-be-number = Variant index { $index } must be a number\n\nvariant-index-must-be-integer = Variant index { $index } must be an integer\n\n## `<sideBySide>`\n\n# $component is `sideBySide` or `sbsGroup`.\nside-by-side-absolute-widths = `<{ $component }>` is not implemented for absolute measurements. Setting widths to relative.\n\nside-by-side-absolute-margins = `<{ $component }>` is not implemented for absolute measurements. Setting margins to relative.\n\nside-by-side-no-block-child = Invalid `<{ $component }>`: it must have at least one block child.\n\n## `<label>`\n\n# Translators: `for` is an attribute name and stays in English.\nlabel-for-ignored-on-graphical = The `for` attribute on graphical `<label>` is ignored.\n\nlabel-for-must-resolve-to-one = The `for` attribute on `<label>` must resolve to exactly one component.\n\nlabel-for-unresolved = The `for` attribute on `<label>` could not be resolved to a component.\n\nlabel-for-answer-with-authored-inputs = The `for` attribute on `<label>` references an `<answer>` with explicitly authored inputs; reference the input directly.\n\nlabel-for-answer-without-input = The `for` attribute on `<label>` references an `<answer>` without an input to label.\n\nlabel-for-must-reference-input-or-answer = The `for` attribute on `<label>` must reference an input or an answer.\n\n## Accessibility\n\n# $component is a DoenetML tag, e.g. "graph" or "image".\naccessibility-short-description-or-decorative = For accessibility, `<{ $component }>` must either have a short description or be specified as decorative.\n\naccessibility-video-short-description = For accessibility, `<video>` must have a short description.\n\naccessibility-input-short-description-or-label = For accessibility, `<{ $component }>` must have a short description or a label.\n\n# The companion to the message above, for the input an `<answer>` creates on the\n# author\'s behalf. Two messages rather than one with the subject passed in: the\n# subject is a phrase here, not a name, and a phrase handed over as an argument\n# would never reach a translator.\naccessibility-answer-input-short-description-or-label = For accessibility, an `<answer>` creating an input must have a short description or a label.\n\naccessibility-short-description-contains-math = Short descriptions should not contain math components such as `<{ $component }>`. Spell out any math with words.\n\n# $colorName is an attribute name and stays in English. $ratio and $threshold\n# are contrast ratios; $mode says which theme the shortfall was measured in,\n# and is `dark` or `light`.\naccessibility-section-title-insufficient-contrast =\n    { $mode ->\n        [dark] { $colorName } has insufficient contrast for the section heading text (dark mode) ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; requires at least { $threshold }:1).\n       *[other] { $colorName } has insufficient contrast for the section heading text ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; requires at least { $threshold }:1).\n    }\n\n## `<circle>`\n\n# $count is the number of through points.\ncircle-through-points-non-numerical = Haven\'t implemented `<circle>` through { $count } points in case where the points don\'t have numerical values.\n\ncircle-too-many-through-points = Cannot calculate circle through more than 3 points.\n\ncircle-overprescribed-radius-center-points = Cannot calculate circle with specified radius, center and through points.\n\ncircle-center-with-multiple-points = Cannot calculate circle with specified center through more than 1 point.\n\n# $distance and $radius arrive as strings, not numbers: $radius is the author\'s\n# own value echoed back for diagnosis, and formatting it as a quantity would\n# round a radius of 0.0001 away to 0.\ncircle-radius-too-small = Cannot calculate circle: given that the distance between the two points is { $distance }, the specified radius { $radius } is too small.\n\ncircle-radius-with-many-points = Cannot create circle through more than two points with a specified radius.\n\ncircle-invalid-center-or-through-points = Invalid center or through points of circle.\n\ncircle-radius-center-with-multiple-points = Cannot calculate radius of circle with specified center through more than 1 point.\n\ncircle-change-radius-non-numerical = Cannot change radius of circle with non-numerical through points\n\ncircle-radius-with-points-non-numerical = Cannot create circle through more than one point with specified radius when don\'t have numerical values.\n\ncircle-change-center-non-numerical = Haven\'t implemented changing center of circle through points with non numerical values.\n\n## `<function>`\n\n# Two independent counts in one sentence, so the variants multiply out. A\n# select\'s variants each need their own line, so the inner one spans lines too;\n# that is safe because newlines inside a placeable never reach the rendered\n# value. Only text continuing onto a further line would.\nfunction-domain-insufficient-dimensions =\n    { $intervals ->\n        [one] Insufficient dimensions for domain for function. Domain has { $intervals } interval but the function has { $inputs ->\n            [one] { $inputs } input\n           *[other] { $inputs } inputs\n        }.\n       *[other] Insufficient dimensions for domain for function. Domain has { $intervals } intervals but the function has { $inputs ->\n            [one] { $inputs } input\n           *[other] { $inputs } inputs\n        }.\n    }\n\nfunction-domain-invalid-format = Invalid format for domain for function.\n\n# $type is what was being read off the point. It selects the wording rather\n# than being substituted into it: "maximum", "slope" and the rest are English\n# nouns, and a noun handed over as an argument would never reach a translator.\n# The catch-all reproduces the pre-catalog behavior for a value not listed here.\nfunction-ignoring-non-numerical =\n    { $type ->\n        [maximum] Ignoring non-numerical maximum of function.\n        [minimum] Ignoring non-numerical minimum of function.\n        [extremum] Ignoring non-numerical extremum of function.\n        [point] Ignoring non-numerical point of function.\n        [slope] Ignoring non-numerical slope of function.\n       *[other] Ignoring non-numerical { $type } of function.\n    }\n\nfunction-ignoring-empty =\n    { $type ->\n        [maximum] Ignoring empty maximum of function.\n        [minimum] Ignoring empty minimum of function.\n        [extremum] Ignoring empty extremum of function.\n        [point] Ignoring empty point of function.\n       *[other] Ignoring empty { $type } of function.\n    }\n\nfunction-points-too-close = Function contains two points with locations too close together. Can\'t define function.\n\nfunction-iterates-input-output-mismatch =\n    { $inputs ->\n        [one] Function iterates are possible only if the number of inputs of the function is equal to the number of outputs. This function has { $inputs } input and { $outputs ->\n            [one] { $outputs } output\n           *[other] { $outputs } outputs\n        }.\n       *[other] Function iterates are possible only if the number of inputs of the function is equal to the number of outputs. This function has { $inputs } inputs and { $outputs ->\n            [one] { $outputs } output\n           *[other] { $outputs } outputs\n        }.\n    }\n\n## `<sequence>`\n\nsequence-invalid-length = Invalid length of sequence.  Must be a non-negative integer.\n\n# $type is a sequence type: number, letters, or math.\nsequence-invalid-step = Invalid step of sequence.  Must be a number for sequence of type { $type }.\n\n# $attribute is `from` or `to` — an attribute name, so it stays in English.\nsequence-invalid-endpoint-number = Invalid "{ $attribute }" of number sequence.  Must be a number.\n\nsequence-invalid-endpoint-letters = Invalid "{ $attribute }" of letters sequence.  Must be a letter combination.\n\nsequence-invalid-endpoint = Invalid "{ $attribute }" of sequence.\n\nselect-from-sequence-coprime-not-numbers = coprime ignored since not selecting numbers\n\nselect-from-sequence-coprime-with-exclude-combinations = coprime ignored since excludeCombinations specified\n\n## Resolving a `target`\n##\n## Raised by the components that take a `target` attribute. They resolve it\n## through the same code and fail the same two ways, so they share these two\n## messages rather than spelling each one out per component: $source is the tag\n## of the component that raised it, part of the DoenetML language, so it stays\n## in English.\n\ntarget-not-found = Invalid target for `<{ $source }>`: cannot find target.\n\n# $property is the state variable that was looked for; $component is the tag it\n# was looked for on.\ntarget-state-variable-not-found = Invalid target for `<{ $source }>`: cannot find a state variable named "{ $property }" on a `<{ $component }>`.\n\n## `<odeSystem>`\n\node-system-variables-match-independent = Variables of `<odeSystem>` must be different than independent variable.\n\node-system-duplicate-variable-names = Can\'t define ODE RHS functions with duplicate dependent variable names.\n\node-system-rhs-function-error = Cannot define ODE RHS function.  Error creating mathjs function.\n\n## `<angle>`, `<parabola>`, and `<intersection>`\n\n# $count is how many line children were found.\nangle-too-many-lines = Cannot define an angle between { $count } lines\n\nangle-invalid-through-point = Invalid point in through of `<angle>`\n\nparabola-vertex-too-many-points = Haven\'t implemented parabola with vertex through more than 1 point.\n\nparabola-too-many-points = Haven\'t implemented parabola through more than 3 points.\n\nintersection-too-many-items = Haven\'t implemented intersection for more than two items\n\n## Other math components\n\nionic-compound-not-two-ions = Have not implemented ionic compound for anything other than two ions.\n\nionic-compound-needs-cation-and-anion = Ionic compound implemented only for one cation and one anion.\n\n# $equation is the equation as the author wrote it.\nsolve-equations-cannot-evaluate = Cannot solve equation as could not evaluate equation: { $equation }\n\n# Translators: `operandNumber` is an attribute name and stays in English.\nmath-operators-operand-number-required = Must specify a operandNumber when extracting a math operand.\n\neigen-decomposition-failed = Could not calculate eigenvalues of matrix\n\n## `<matchesPattern>`\n\n# Translators: `parameters` is an attribute name and stays in English.\n# $parameters lists the parameters as the author wrote them;\n# $parametersCount is how many there were.\nmatches-pattern-parameter-not-in-pattern =\n    { $parametersCount ->\n        [one] `<matchesPattern>`: the parameter { $parameters } does not occur in the pattern, so it will always match a blank.\n       *[other] `<matchesPattern>`: the parameters { $parameters } do not occur in the pattern, so they will always match a blank.\n    }\n\n## `<graph>`\n\n# Translators: grid is an attribute name and none, medium and dense are its\n# values; all four stay in English, as does the example. $grid is the value the\n# author wrote, reproduced verbatim — it reached this message precisely because\n# it was not one of the forms listed.\ngraph-grid-invalid = `<graph>`: cannot interpret grid="{ $grid }". It must be none, medium, dense, or two positive numbers separated by a space, such as grid="1 0.5". No grid is drawn.\n\n## `<slopeField>` and `<vectorField>`\n\n# $component is the field\'s tag and $alternative the sibling field component\'s,\n# or `none` when the function would not suit it either; both are DoenetML tags\n# and stay in English, as do the example expressions. $expected is how many\n# outputs the component needs, $found how many the given function has. What a\n# field draws a mark from is the function\'s outputs, so the wrong number of\n# them means there is nothing to draw — and the author almost always wanted the\n# other component.\nfield-function-wrong-num-outputs =\n    `<{ $component }>` needs a function with { $expected ->\n        [one] one output, the slope y\' at each point, such as `y - x`\n       *[other] two outputs, the vector at each point, such as `(y, -x)`\n    }, but the function it was given has { $found ->\n        [one] { $found } output\n       *[other] { $found } outputs\n    }. { $alternative ->\n        [none] Nothing is drawn.\n       *[other] `<{ $alternative }>` is the component for that function. Nothing is drawn.\n    }\n\n# Translators: retired. `function` is an attribute name and stays in English.\n# It warned that a field had been given its function both as an attribute and\n# inside the component; the attribute no longer exists, so the two can no\n# longer disagree. Kept because diagnostic codes are never reused.\nfield-function-attribute-ignored-with-child = The `function` attribute is ignored because the function is also given inside the component; the one inside is used. Give the function only one of the two ways.\n\n# Translators: `variables` and `function` are a DoenetML attribute and tag and\n# stay in English, as does $component, the field\'s own tag. The attribute names\n# the inputs of an expression written directly inside the component; when there\n# is no such expression there is nothing for it to name, and $reason says which\n# of the two ways that happened.\nfield-variables-ignored =\n    `<{ $component }>`: the `variables` attribute names the variables of an expression written directly inside the component. { $reason ->\n        [function-child] The function here is given as a `<function>` child, which names its own variables, so `variables` is ignored.\n       *[no-expression] No such expression is given here, so `variables` is ignored.\n    }\n\n## PreFigure renderer\n\n# Translators: xLabelPosition, yLabelPosition and their values are attribute\n# names and stay in English, as does the renderer\'s name.\nprefigure-x-label-position-unsupported = `<graph>`: xLabelPosition="left" is not supported in prefigure renderer; using right-position behavior.\n\nprefigure-y-label-position-unsupported = `<graph>`: yLabelPosition="bottom" is not supported in prefigure renderer; using top-position behavior.\n\nprefigure-invalid-axis-bounds = `<graph>`: invalid axis bounds for prefigure conversion; using default bbox (-10,-10,10,10).\n\nprefigure-invalid-width = `<graph>`: invalid width for prefigure conversion; using default diagram width 425.\n\nprefigure-invalid-aspect-ratio = `<graph>`: invalid aspectRatio for prefigure conversion; using default aspect ratio 1.\n\n# Translators: the renderer\'s name, prefigure, stays in English. "grid" here is\n# the coordinate grid itself rather than the attribute that asks for one, so it\n# is prose and is translated.\nprefigure-grid-spacing-too-fine = `<graph>`: the grid spacing is too fine for the axis limits; the grid is omitted in the prefigure renderer.\n\nprefigure-annotations-not-rendered = `<graph>`: annotations will not be rendered when not using the PreFigure renderer.\n\nmultiple-annotations-children = Multiple `<annotations>` children found in `<graph>`; all but the last one are ignored.\n\n## Referring to other components\n##\n## `<updateValue>`\'s own "cannot find target" messages are not here: it\n## resolves a target the same way `<animateFromSequence>` does and fails the\n## same ways, so the two share `target-not-found` and\n## `target-state-variable-not-found` above.\n\ncopy-unrecognized-component-type = Cannot extend or copy an unrecognized component type: { $type }.\n\ncopy-prop-not-found = Could not find prop { $property } on a component of type { $component }\n\ncollect-no-source = No source found for collect.\n\ncollect-invalid-component-type = Cannot collect components of type `<{ $component }>` as it is an invalid component type.\n\n# $reference is the reference exactly as the author wrote it, `$` and all —\n# the `$p.styleDescription[1]` of `<text extend="$p.styleDescription[1]" />`.\n# An index only means something applied to an array, and the thing named here\n# is not one. The reference is quoted back rather than explained because the\n# text in front of the author is the only part of this they can act on: the\n# state variable and component index the core knows about are its own business\n# and go to the console instead.\nreference-index-unavailable = Cannot reference index `{ $reference }`\n\n## `<callAction>`\n\n# $action is the `actionName` the author asked for, part of the DoenetML\n# language, so it stays in English. $reference is the `target` as written.\ncomponent-action-unavailable = Cannot call { $action } on component `{ $reference }`\n\n## `<dataFrame>`\n\n# $componentIdx is an internal index, passed as a string so it is not grouped\n# like a quantity; the odd spacing before the colon is reproduced from the\n# original message.\ndata-frame-inconsistent-row-lengths = Data has invalid shape.  Rows has inconsistent lengths. Found in componentIdx :{ $componentIdx }\n\ndata-frame-duplicate-column-names = Data has duplicate column names.  Found in componentIdx :{ $componentIdx }\n\ndata-frame-missing-column-name = Data is missing a column name.  Found in componentIdx :{ $componentIdx }\n\n## `<answer>` and scoring\n\nanswer-award-depends-on-own-response = An award for this answer is based on the answer tag\'s own submitted response, which will lead to unexpected behavior.\n\n# Translators: maxNumAttempts and sectionWideCheckWork are attribute names.\nanswer-max-num-attempts-in-section-wide-check-work = Setting `maxNumAttempts` on an `<answer>` inside a container with `sectionWideCheckWork` has no effect, as the number of attempts is controlled by the container. Set `maxNumAttempts` on the container instead.\n\nnested-section-wide-check-work-max-num-attempts = Setting `maxNumAttempts` on a container with `sectionWideCheckWork` that is inside another container with `sectionWideCheckWork` has no effect, as the number of attempts is controlled by the outer container. Set `maxNumAttempts` on the outer container instead.\n\n# $attributes is a list of attribute names; $attributesCount is its length.\nanswer-attributes-need-symbolic-equality =\n    { $attributesCount ->\n        [one] The { $attributes } attribute will have no effect without symbolicEquality set.\n       *[other] The { $attributes } attributes will have no effect without symbolicEquality set.\n    }\n\nanswer-invalid-type = Invalid type for answer: { $type }\n\n## `<module>`, `<conditionalContent>`, `<slider>`, `<pretzel>`\n\nmodule-attribute-child-needs-name = Since the component `<{ $component }>` does not have a name, it cannot be used for a module attribute\n\nmodule-attribute-name-already-defined = The component `<{ $component } name="{ $name }">` cannot be used as an attribute for a module because the `<module>` component type already has a "{ $name }" attribute defined.\n\nconditional-content-condition-ignored = Attribute `condition` is ignored on a `<conditionalContent>` component with case or else children.\n\nslider-markers-type-mismatch = Markers type doesn\'t match slider type.\n\npretzel-problem-needs-statement-and-answer = Invalid pretzel: each `<problem>` must contain one `<statement>` and one `<answer>`.\n\npretzel-circuit-first-problem-distractor = Invalid pretzel: in mode="circuit", the first `<problem>` cannot be a distractor.\n\n## Attribute values\n\n# $values is a list of the values that were rejected, each already in\n# backticks; $valuesCount is how many there were.\nattribute-invalid-values =\n    { $valuesCount ->\n        [one] Invalid value { $values } for attribute `{ $attribute }`; ignoring.\n       *[other] Invalid values { $values } for attribute `{ $attribute }`; ignoring.\n    }\n\nattribute-must-be-references = Invalid value `{ $value }` for attribute `{ $attribute }`. Attribute must be composed of references that begin with a `$`.\n\n# $names is a list of the rejected names, each already in single quotes.\nmath-input-invalid-function-names = <mathInput>: ignored invalid function name(s) in { $attribute }: { $names }. Each name\'s display segment must be at least 2 characters (letters or dashes); an optional `|<mathspeak alternative>` suffix may follow.\n\n## Building components from the source\n\n# Raised while the source is being turned into components, by throwing rather\n# than by building a record: the thrower is caught, the component becomes an\n# `_error`, and the diagnostic is re-raised from it.\n\ncomponent-type-invalid = Invalid component type: `<{ $componentType }>`\n\nattribute-repeated = Cannot repeat attribute { $attribute }.\n\nattribute-invalid-for-component = Invalid attribute "{ $attribute }" for a component of type `<{ $componentType }>`.\n\n## Style definition contrast\n\n# $context names the pair being compared, $mode which colour scheme it was\n# rendered in. Both are symbolic — the phrase is chosen here so a translator\n# can rewrite it, rather than being handed over already in English.\nstyle-definition-insufficient-contrast =\n    Style definition { $styleNumber } has insufficient contrast for { $context ->\n        [text-on-background] text color against background color\n        [high-contrast] high-contrast color against the canvas\n        [line] line color against the canvas\n        [marker] marker color against the canvas\n       *[text-on-canvas] text color against the canvas\n    }{ $mode ->\n        [dark] { " (dark mode)" }\n       *[light] { "" }\n    } ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; requires at least { $threshold }:1).\n\n# $suggestion says whether a concrete replacement colour could be computed.\n# The attribute names and colour values in the `available` branch are\n# DoenetML source, not prose, and stay as they are in every language.\nstyle-definition-dark-mode-text-background-contrast =\n    Although style definition { $styleNumber } has specified colors that provide sufficient contrast for light mode, the dark-mode colors derived from these values have insufficient contrast for the text color against the background color ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; requires at least { $threshold }:1). { $suggestion ->\n        [available] To ensure sufficient contrast in dark mode, either increase the light-mode contrast (e.g., set { $lightAttribute }="{ $lightColor }") or override the dark-mode color (e.g., set { $darkAttribute }="{ $darkColor }").\n       *[none] To ensure sufficient contrast in dark mode, increase the light-mode contrast or override the derived colors with textColorDarkMode and/or backgroundColorDarkMode.\n    }\n\nstyle-definition-dark-mode-text-canvas-contrast =\n    Although style definition { $styleNumber } has a specified text color that provides sufficient contrast for light mode, the dark-mode text color derived from this value has insufficient contrast against the canvas ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; requires at least { $threshold }:1). { $suggestion ->\n        [available] To ensure sufficient contrast in dark mode, either increase the light-mode contrast (e.g., set textColor="{ $lightColor }") or override the dark-mode color (e.g., set textColorDarkMode="{ $darkColor }").\n       *[none] To ensure sufficient contrast in dark mode, increase the light-mode contrast or override the derived color with textColorDarkMode.\n    }\n\nsection-multiple-style-palettes = A section can select only one <stylePalette>; using the last one.\n\n## Unique variants\n\n# Explanations of why a component\'s unique variants could not be worked out.\n# $component is the tag that could not be analyzed and stays as written; the\n# reason is a separate message per situation, so a host can tell them apart by\n# code and a translator sees a whole sentence rather than a fragment.\n\nvariant-num-to-select-not-non-negative-integer = cannot determine unique variants of { $component } as numToSelect isn\'t a non-negative integer.\n\nvariant-num-to-select-not-constant-number = cannot determine unique variants of { $component } as numToSelect isn\'t constant number.\n\nvariant-with-replacement-not-constant-boolean = cannot determine unique variants of { $component } as withReplacement isn\'t constant boolean.\n\nvariant-select-weight-disables-unique = Unique variants for select disabled if have an option with selectWeight or selectForVariants specified\n\nvariant-coprime-undetermined = cannot determine unique variants of { $component } as cannot determine coprime is always false.\n\n# $attribute is an attribute name (`from`, `to`, `step`, `sort`, `length`) and\n# stays as written.\nvariant-attribute-not-constant = cannot determine unique variants of { $component } as { $attribute } isn\'t a constant.\n\nvariant-attribute-not-number = cannot determine unique variants of { $component } as { $attribute } isn\'t a number.\n\n# $type is the sequence type the component was declared with. $expected names\n# what the value had to be, symbolically, because which one applies depends on\n# both the type and the attribute.\nvariant-attribute-wrong-type-for-sequence =\n    cannot determine unique variants of { $component } of { $type } type as { $attribute } isn\'t { $expected ->\n        [letters-combination] a combination of letters\n        [math-expression] a valid math expression\n        [integer] an integer\n       *[number] a number\n    }.\n\nvariant-length-not-integer = cannot determine unique variants of { $component } as length isn\'t an integer.\n\nvariant-sort-not-implemented = have not implemented unique variants of a { $component } with sort\n\nvariant-exclude-combinations-not-implemented = have not implemented unique variants of a { $component } with excludeCombinations\n\nvariant-math-exclude-not-implemented = have not implemented unique variants of a { $component } of type math with exclude\n\nvariant-non-constant-exclude-not-implemented = have not implemented unique variants of a { $component } with non-constant exclude\n\n## PreFigure conversion\n\n# $subject identifies the component the warning is about, already written as\n# `<tag>` or `<tag> (name)`. It is composed in code rather than here because\n# Fluent terms cannot take a variable as an argument, so a shared subject\n# fragment cannot be parameterized from the catalog. It holds only a tag name,\n# a component name and punctuation — never a word — which is why a descendant\n# with no type reads `<?>` rather than `<unknown>`.\n\nprefigure-descendant-unsupported = { $subject }: unsupported in graph prefigure renderer; descendant skipped.\n\nprefigure-descendant-invalid-geometry = { $subject }: non-finite or incomplete geometry; descendant skipped.\n\nprefigure-curve-label-omitted = { $subject }: labels are not supported on converted curve elements; label omitted.\n\nprefigure-curve-unsupported-definition-type = { $subject }: unsupported curve function definition type \'{ $definitionType }\'; descendant skipped.\n\nprefigure-region-flip-functions-unsupported = { $subject }: unsupported flipFunctions attribute on regionBetweenCurves; descendant skipped.\n\nprefigure-region-non-formula-child = { $subject }: only formula-typed child functions are supported on regionBetweenCurves; descendant skipped.\n\n# $labelKind says which family of object carried the label, since the advice\n# is the same but the object is not.\nprefigure-label-position-unsupported =\n    { $subject }: unsupported labelPosition \'{ $labelPosition }\' for { $labelKind ->\n        [line-family] line-family label\n       *[point] point label\n    }; default PreFigure alignment used.\n\nprefigure-fill-style-unsupported = { $subject }: fill style \'{ $fillStyle }\' is unsupported by PreFigure; falling back to a solid fill.\n\nprefigure-line-style-unknown = { $subject }: unknown line style \'{ $lineStyle }\' omitted from PreFigure output.\n\nprefigure-marker-style-mapped-to-diamond = { $subject }: marker style \'{ $markerStyle }\' mapped to PreFigure style \'diamond\'.\n\nprefigure-marker-style-unsupported = { $subject }: marker style \'{ $markerStyle }\' is unsupported by PreFigure; default style used.\n\n## PreFigure annotations\n\nannotation-ref-unresolvable = `<annotation>`: invalid `ref`; cannot resolve target. Annotation omitted.\n\nannotation-ref-multiple-targets = `<annotation>`: `ref` resolved to multiple targets; using the first target.\n\nannotation-ref-outside-graph = `<annotation>`: invalid `ref`; target is outside the containing graph. Annotation omitted.\n\nannotation-ref-unsupported-target = `<annotation>`: invalid `ref`; target is not a supported graphical object in prefigure conversion. Annotation omitted.\n\nannotation-text-missing = `<annotation>`: missing or empty `text`; emitting empty text.\n\n## Composites and references\n\n# $componentType is the type the composite was asked to create, when it is\n# known; `none` when the composite did not say.\ncomposite-circular-dependency =\n    { $componentType ->\n        [none] Circular dependency detected.\n       *[other] Circular dependency detected involving `<{ $componentType }>` component.\n    }\n\n# $reference is the reference as the author wrote it, already carrying its `$`.\nreference-no-referent = No referent found for reference: `{ $reference }`\n\nreference-multiple-referents = Multiple referents found for reference: `{ $reference }`\n\n## Children that do not match\n\nchildren-invalid-attribute-format = Invalid format for attribute { $attribute } of `<{ $componentType }>`.\n\n# $children is the list of child types that did not match, already joined.\nchildren-invalid = Invalid children for `<{ $componentType }>`: Found invalid children: { $children }\n\n## Falling back to a default\n\n# The attribute had a default to fall back to, and the message names it: the\n# component went on to behave as though the author had written that value, and\n# an author not told which one goes looking for the difference in the wrong\n# place.\nattribute-value-invalid-using-default = Invalid value `{ $value }` for attribute `{ $attribute }`, using value `{ $default }`\n\n# The same rejection where the attribute has no default to fall back to, so\n# nothing stood in for the value and the component behaves as though the\n# attribute had not been written. A separate message rather than the one above\n# with a blank in it: "using value `null`" would describe a substitution that\n# did not happen, and name a value no author could have typed. What follows is\n# usually a second message from the component itself, saying what it did\n# without the attribute.\nattribute-value-invalid-ignoring = Invalid value `{ $value }` for attribute `{ $attribute }`, ignoring it\n\n## Loading a DoenetML version\n\n# $fallback is the version that will be used instead, or `none` when the\n# embedding page named a standalone bundle of its own.\ndoenetml-version-not-found =\n    { $fallback ->\n        [none] DoenetML version { $version } not found.\n       *[other] DoenetML version { $version } not found. Falling back to version { $fallback }\n    }\n\n## Reading the DoenetML\n\n# The parser\'s own diagnostics: what the author sees before anything runs, and\n# for a beginner usually the first Doenet message they ever read.\n#\n# The parser writes its English beside the code rather than rendering it from\n# here, because `@doenet/parser` is inside the language-server bundle and a\n# catalog there is dead weight on the editor\'s critical path\n# (`packages/lsp/scripts/check-server-bundle.mjs` fails if one arrives). The\n# two copies are held together by a test in that package, which parses a\n# corpus and asserts every coded error renders to exactly what the parser\n# wrote — so a message edited here without its counterpart fails there.\n#\n# $tag, $value, $attribute and their relatives quote the author\'s own source\n# back at them and stay exactly as written. The `Invalid DoenetML: ` opening is\n# repeated in each message instead of being a shared term: a term a locale\n# forgets to define renders as its own name, and a prefix on fifteen messages\n# is not worth that failure mode.\n\nparse-invalid-doenetml = Invalid DoenetML: { $content }\n\nparse-tag-missing-close-tag = Invalid DoenetML: The tag `{ $tag }` has no closing tag. Expected a self-closing tag or a `</{ $tagName }>` tag.\n\nparse-tag-error = Invalid DoenetML: Error in tag `<{ $tagName }>`\n\nparse-attribute-missing-value = Invalid DoenetML: Invalid attribute `{ $attribute }` appears to be missing a value.\n\nparse-attribute-invalid = Invalid DoenetML: Invalid attribute `{ $attribute }`\n\nparse-attribute-value-invalid = Invalid DoenetML: Invalid attribute value `{ $value }`\n\n# $quote is the quote character that would balance the pair: `"` or `\'`.\nparse-attribute-value-quote-mismatch = Invalid DoenetML: Invalid attribute value `{ $value }`. The quote marks do not match. You appear to be missing a `{ $quote }`\n\nparse-open-tag-name-missing = Invalid DoenetML: Found a tag without a tag name, e.g. `<`\n\nparse-tag-not-closed = Invalid DoenetML: Tag `{ $tag }` was not closed (a `>` appears to be missing).\n\nparse-self-closing-tag-name-missing = Invalid DoenetML: Found a tag without a tag name `<{ $content }>`\n\nparse-self-closing-tag-not-closed = Invalid DoenetML: Tag `{ $tag }` was not closed (`/>` appears to be missing).\n\nparse-tag-invalid-attributes = Invalid DoenetML: Tag `{ $tag }` is not valid. It may have incorrect attributes.\n\nparse-close-tag-name-missing = Invalid DoenetML: Found a closing tag without a tag name, e.g. `</`\n\n# $attribute is the attribute name and $value the unquoted token that followed\n# it, shown reassembled the way the author should have written it.\nparse-attribute-value-unquoted = Attribute values must be enclosed in quotes: `{ $attribute }="{ $value }"`\n\nparse-close-tag-without-open-tag = Invalid DoenetML: Found closing tag `{ $tag }`, but no corresponding opening tag\n\nparse-close-tag-mismatched = Invalid DoenetML: Mismatched closing tag. Expected `</{ $expected }>`. Found `{ $found }`\n\n# The conversion\'s fall-through: the syntax tree held a node shape it has no\n# case for. Reaching an author means the grammar and the conversion have gone\n# out of step, which is a bug in Doenet rather than in their document — hence\n# `parser-` rather than the `parse-` of every message above, which is about\n# what the author wrote. They are still the one looking at it, so it is\n# translated like any other error. $node is the node\'s own name and stays as\n# it is.\nparser-node-unconvertible = Could not convert node { $node } to Dast node.\n\n## Names\n\n# $reason says which rule the name broke, as a key rather than a phrase, so the\n# whole sentence is translatable rather than assembled from two halves.\nname-attribute-invalid =\n    Invalid attribute name=\'{ $name }\'. { $reason ->\n        [characters] Names can contain only letters, numbers, underscores or hyphens.\n       *[start] Names must start with a letter.\n    }\n\ncomponent-name-invalid-start = Invalid component name "{ $name }". Names must start with a letter.\n\n## `<answer>` sugar\n\nanswer-video-watched-missing-video = Answer with type videoWatched must have a video attribute\n\nanswer-video-watched-video-not-reference = Answer with type videoWatched must have video attribute that is a reference\n\nanswer-name-not-single-text = Answer name attribute must have a single text child\n\n## Referencing another document\n\n# $attribute is the attribute the URI was written in (`copyFrom`, `extend`, …)\n# and stays as written; $uri is the author\'s own value.\n\nexternal-doenetml-recursion-limit = Unable to retrieve external DoenetML due to too many levels of recursion. Is there a circular reference?\n\nexternal-doenetml-unavailable = Unable to retrieve DoenetML from { $attribute }="{ $uri }"\n\nexternal-doenetml-type-mismatch = Invalid DoenetML retrieved from { $attribute }="{ $uri }": it did not match the component type "{ $componentType }"\n\n## Deprecated syntax\n\n# $from and $to are attribute names and $component a tag name; all three stay\n# as written. $component is `none` for a rename that applies to every component\n# accepting the attribute, where naming one would be wrong.\n#\n# The `[deprecation]` opening is a literal marker shared by all four messages,\n# not a word: leave it as it is.\n\ndeprecated-attribute-renamed =\n    { $component ->\n        [none] [deprecation] Attribute `{ $from }` is deprecated; use `{ $to }` instead.\n       *[other] [deprecation] Attribute `{ $from }` on `<{ $component }>` is deprecated; use `{ $to }` instead.\n    }\n\ndeprecated-attribute-renamed-conflict =\n    { $component ->\n        [none] [deprecation] Attribute `{ $from }` is deprecated and ignored because `{ $to }` is also specified.\n       *[other] [deprecation] Attribute `{ $from }` on `<{ $component }>` is deprecated and ignored because `{ $to }` is also specified.\n    }\n\ndeprecated-attribute-ignored = [deprecation] Attribute `{ $attribute }` on `<{ $component }>` is deprecated and ignored.\n\n# An attribute replaced by a child element rather than by another attribute:\n# $attribute and $component stay as written, and so does $child, which is the\n# tag name of the child to write instead.\n\ndeprecated-attribute-to-child = [deprecation] Attribute `{ $attribute }` on `<{ $component }>` is deprecated; use a `<{ $child }>` child instead.\n\n# One value of an attribute is deprecated while the attribute itself stays:\n# $value is what the author wrote and $to what to write instead, with\n# $attribute and $component naming where. All four stay as written.\n\ndeprecated-attribute-value-renamed = [deprecation] Value `{ $value }` of attribute `{ $attribute }` on `<{ $component }>` is deprecated; use `{ $to }` instead.\n\n\n## Language coverage\n\n# `<pluralize>` runs an English part-of-speech model over its text and puts the\n# nouns in the plural. There is no equivalent for an arbitrary language — a\n# correct plural needs that language\'s own morphology, and often its\n# dictionary — so in a document written in anything else the word is left as\n# the author typed it, and this says so rather than silently doing nothing.\n#\n# Raised only when there is nothing else to fall back on: a `pluralForm` is the\n# author supplying their own language\'s plural, and that is honored in every\n# language, which is why this can recommend it.\n#\n# $locale is the document\'s language tag, as declared.\npluralize-english-only = `<pluralize>` can only pluralize English, so its text is left unchanged in a document written in { $locale }. Write the plural form directly, or set it with the `pluralForm` attribute.\n\n\n## Checking against the schema\n\n# What the editor draws a squiggle under: the language server\'s own check of\n# the document against the DoenetML schema, run on every keystroke and\n# answered before anything is evaluated. A beginner meets these first, and\n# usually only these, because a document that does not pass them rarely gets\n# as far as producing a diagnostic from the core.\n#\n# `@doenet/lsp-tools` writes its English beside the code rather than rendering\n# it from here, for the same reason `@doenet/parser` does: it is inside the\n# language-server bundle, which `@doenet/codemirror` embeds verbatim and\n# starts as a blob worker, and a catalog on the editor\'s critical path is what\n# `packages/lsp/scripts/check-server-bundle.mjs` exists to reject. The two\n# copies are held together by a test in that package, which runs the checker\n# over a corpus and asserts every coded violation renders to exactly what the\n# checker wrote — so a message edited here without its counterpart fails\n# there.\n#\n# $tag, $parent and $attribute quote the author\'s own source back at them and\n# stay exactly as written; the angle brackets and backticks around them are\n# punctuation this catalog supplies, not part of the name.\n\nschema-element-unrecognized = Element `<{ $tag }>` is not a recognized Doenet element.\n\nschema-element-not-allowed-at-root = Element `<{ $tag }>` is not allowed at the root of the document.\n\nschema-element-not-allowed-inside = Element `<{ $tag }>` is not allowed inside of `<{ $parent }>`.\n\nschema-attribute-unrecognized = Element `<{ $tag }>` doesn\'t have an attribute called `{ $attribute }`.\n\n# $allowed is the attribute\'s permitted values, each already in double quotes\n# and joined for the reader\'s language. $isList says whether the attribute\n# takes several of them at once: one situation, two sentences, because the\n# reader has to be told they are choosing a whole list rather than a value.\nschema-attribute-value-not-allowed =\n    { $isList ->\n        [true] Attribute `{ $attribute }` of element `<{ $tag }>` must be a list whose items are each one of: { $allowed }\n       *[other] Attribute `{ $attribute }` of element `<{ $tag }>` must be one of: { $allowed }\n    }\n\n\n## The `<select>` family\'s error boxes\n##\n## The messages that replace the whole component with a red box rather than\n## warning beside it: nothing can be selected, so there is nothing to render.\n## They were the last uncoded `_error` path in the worker (#1581).\n##\n## Counts arrive as numbers rather than as text, so a language that agrees a\n## noun with them can select on them. English does not agree here — it says\n## "1 options" today and these messages reproduce it exactly, because the box\'s\n## text is what the existing suites pin.\n##\n## Being numbers, they are grouped: a count of 1500 renders as "1,500" in\n## English where the concatenated sentence these replaced wrote "1500". That is\n## the one way the English moved, and it moved in the right direction — these\n## are quantities, not identifiers like a line or a section number, which is\n## the distinction that decides between a number and a string everywhere in\n## these catalogs.\n##\n## Translators: component and attribute names — `selectFromSequence`,\n## `selectPrimeNumbers`, `from`, `to`, `step` — are DoenetML identifiers, not\n## words. They are written into these messages as they stand and must be left\n## in English exactly as written.\n\nselect-variant-name-option-count-mismatch = Invalid variant name for select.  Variant name { $variantName } appears in { $numOptions } options but number to select is { $numToSelect }.\n\nselect-variant-name-without-options = Some variants are specified for select but no options are specified for possible variant name: { $variantName }.\n\nselect-variant-name-not-possible = Variant name { $variantName } that is specified for select is not a possible variant name.\n\nselect-too-few-options = Cannot select { $numToSelect } components from only { $numOptions }.\n\nselect-from-sequence-too-few-values = Cannot select { $numToSelect } values from a sequence of length { $length }.\n\nselect-from-sequence-indices-count-mismatch = Number of indices specified for select must match number to select\n\nselect-from-sequence-indices-not-integers = All indices specified for select must be integers\n\nselect-from-sequence-index-excluded = Specified index of selectfromsequence that was excluded\n\nselect-from-sequence-indices-excluded-combination = Specified indices of selectfromsequence that was an excluded combination\n\nselect-from-sequence-coprime-not-positive-integers = Cannot select coprime combinations as not selecting positive integers.\n\n# Translators: from, to and step are attribute names. They are written into\n# the message rather than passed in because these three never vary — an\n# argument is for a name that changes from one call to the next.\nselect-from-sequence-coprime-common-factor = Cannot select coprime numbers. All possible values share a common factor. (Specified values of "from" or "to" must be coprime with "step".)\n\nselect-from-sequence-coprime-single-number = Cannot select coprime combinations from a single number that is not 1.\n\nselect-from-sequence-excluded-too-many-combinations = Excluded over 70% of combinations in selectFromSequence\n\n# The sibling of `select-from-sequence-coprime-common-factor`, and a different\n# situation rather than a rewording of it: that one is decided up front, from\n# the sequence\'s own arithmetic. This one is what is left after two hundred\n# draws found no coprime combination among values that could have supplied one.\nselect-from-sequence-coprime-none-found = Could not select coprime numbers. All possible values share a common factor.\n\nselect-from-sequence-too-few-unique-values = Cannot select { $numToSelect } unique values from sequence of length { $numPossibleValues }\n\nselect-prime-numbers-too-few-values = Cannot select { $numToSelect } values from a list of primes of length { $numValues }\n\nselect-prime-numbers-values-count-mismatch = Number of values specified for select must match number to select\n\nselect-prime-numbers-values-not-prime = All values specified for select prime number must be in the list of primes\n\nselect-prime-numbers-values-excluded-combination = Specified values of selectPrimeNumbers was an excluded combination\n\nselect-prime-numbers-excluded-too-many-combinations = Excluded over 70% of combinations in selectPrimeNumbers\n\n# Both flukes are shared by `<selectFromSequence>` and `<selectPrimeNumbers>`,\n# which say the same thing in the same words. Neither is reachable in practice\n# — each follows two hundred independent draws — but an unreachable box is\n# still a box, and it renders in whatever language the rest of the page does.\nselect-random-combination-fluke = By extremely unlikely fluke, couldn\'t select combination of random values\n\nselect-random-value-fluke = By extremely unlikely fluke, couldn\'t select random value\n\n## Inputs embedded in math\n\n# Translators: $component is the input\'s own DoenetML tag and stays in English,\n# as do the attribute names `inline`, `expanded` and `width`. An input written\n# inside `<m>` is drawn in the place it is written, inside the typeset\n# expression, which makes room for it as it grows. That needs a control small\n# enough to sit in a line of mathematics, with a width the expression can\n# measure, in an expression that is not drawn on a graph; $reason says which of\n# those this input fails. When it fails, the input is not shown at all, and the\n# expression is typeset with the input\'s value in its place — a text input\'s\n# text, a math input\'s mathematics — or with nothing there for a choice input.\nmath-embedded-input-shape-unsuitable =\n    { $reason ->\n        [not-inline] This `<{ $component }>` is not shown because it is inside math and is not `inline`. Add `inline` so it becomes a drop-down list, which fits inside an expression.\n        [expanded] This `<{ $component }>` is not shown because it is inside math and is `expanded`. Remove `expanded`; a multi-line box does not fit inside an expression.\n        [on-graph] This `<{ $component }>` is not shown because it is inside math drawn on a graph, which has no room for an input.\n       *[relative-width] This `<{ $component }>` is not shown because it is inside math and has a relative width. Give the width in absolute units, such as `px`, instead.\n    }\n\n## `<sampleRandomNumbers>` and `<selectRandomNumbers>`\n##\n## Translators: `mean`, `standardDeviation`, `variance`, `numTotal`,\n## `numSuccesses`, `numDraws`, `numTrials`, `probability` and `numSamples` are\n## DoenetML attribute names. They are written into these messages as they stand\n## and must be left in English exactly as written. Each of these names the\n## attribute the author has to change, so a message that translated one would\n## point at an attribute that does not exist.\n\n# The spread reaches the sampler as a standard deviation however it was written,\n# so a negative `variance` arrives here as a `standardDeviation` of NaN and the\n# message has to name both for the author to know what to edit.\nsample-gaussian-parameters-invalid =\n    Invalid mean ({ $mean }) or standardDeviation ({ $standardDeviation }) for a gaussian random variable. The mean must be a finite number, and the standardDeviation (or the variance it is derived from) must be finite and non-negative. No numbers can be sampled.\n\n# These three attributes are the only ones with no default, so leaving one out is\n# the commonest way to reach this message. Each arrives either as the number the\n# author wrote or as `not-set` for an attribute they left off entirely; translate\n# the "not set" wording, but leave the `not-set` key that selects it untouched.\nsample-hypergeometric-parameters-invalid =\n    Invalid numTotal ({ $numTotal ->\n        [not-set] not set\n       *[other] { $numTotal }\n    }), numSuccesses ({ $numSuccesses ->\n        [not-set] not set\n       *[other] { $numSuccesses }\n    }), or numDraws ({ $numDraws ->\n        [not-set] not set\n       *[other] { $numDraws }\n    }) for a hypergeometric random variable. numTotal must be a positive whole number, and numSuccesses and numDraws must be non-negative whole numbers no larger than numTotal. All three must also stay below about nine quadrillion, past which whole numbers can no longer be counted exactly.\n\n# $maxDraws is the largest number of random draws allowed for a single sample.\nsample-hypergeometric-draws-too-many =\n    Drawing { $numDraws } items from a population of { $numTotal } would need more than { $maxDraws } random draws for each sample, which would stop the page from responding. Reduce numDraws, or bring it closer to numTotal.\n\nsample-binomial-parameters-invalid =\n    Invalid numTrials ({ $numTrials }) or probability ({ $probability }) for a binomial random variable. numTrials must be a non-negative whole number below about nine quadrillion, past which whole numbers can no longer be counted exactly, and probability must be between 0 and 1.\n\n# $maxDraws is the largest number of random draws allowed for a single sample.\nsample-binomial-trials-too-many =\n    Running { $numTrials } trials would need more than { $maxDraws } random draws for each sample, which would stop the page from responding. Reduce numTrials.\n\nsample-poisson-mean-invalid =\n    Invalid mean ({ $mean }) for a poisson random variable. The mean must be a finite, non-negative number.\n\n# $maxDraws is the largest number of random draws allowed for a single sample.\nsample-poisson-mean-too-large =\n    A poisson mean of { $mean } would need more than { $maxDraws } random draws for each sample, which would stop the page from responding. Reduce the mean.\n\n# $distribution names the distribution being sampled, e.g. "binomial" or\n# "multivariate hypergeometric"; $draws is roughly how many random draws each value\n# needs. Raised by `<sampleRandomNumbers>`, `<selectRandomNumbers>` and\n# `<sampleMultivariateRandomNumber>`, which count values with `numSamples`,\n# `numToSelect` and one vector respectively, so the wording names no attribute.\nsample-distribution-slow =\n    Each value from this { $distribution } distribution needs about { $draws } random draws, so sampling may be slow. Reduce the distribution\'s parameters, or ask for fewer values, if the page feels sluggish.\n\n## List index operators\n\n# Raised by the index-returning list operators (`<indexOf>`, `<searchSorted>`)\n# when no `target` was given. $component names the tag the author wrote.\nindex-operator-missing-target =\n    `{ $component }` has no `target` to look for, so it cannot report a position and gives 0.\n\n# Raised when the operator had no values to look through — an empty list, or one\n# whose only children were references that produced nothing.\nindex-operator-no-values =\n    `{ $component }` has no values to look through, so it gives 0, which is not the index of any item.\n## `<sampleMultivariateRandomNumber>`\n##\n## Translators: `type`, `numInCategories` and `numDraws` are DoenetML attribute\n## names, and `hypergeometric` is one of the values `type` takes. They are written\n## into these messages as they stand and must be left in English exactly as\n## written. Each names the attribute the author has to change, so a message that\n## translated one would point at an attribute that does not exist.\n\n# Neither attribute has a default that names a population — numDraws has none at\n# all, and numInCategories falls back to a list with no categories in it — so\n# leaving one out is the commonest way to reach this message. Each arrives either\n# as the value the author wrote or as `not-set`: for numDraws when it is missing,\n# and for numInCategories when it names no categories, whether it was left off or\n# written empty. Translate the "not set" wording, but leave the `not-set` key that\n# selects it untouched.\nsample-multivariate-parameters-invalid =\n    Invalid numInCategories ({ $numInCategories ->\n        [not-set] not set\n       *[other] { $numInCategories }\n    }) or numDraws ({ $numDraws ->\n        [not-set] not set\n       *[other] { $numDraws }\n    }) for a multivariate hypergeometric random variable. numInCategories must list at least one category, each a non-negative whole number, and numDraws must be a non-negative whole number no larger than their total. Each category, that total, and numDraws must also stay below about nine quadrillion, past which whole numbers can no longer be counted exactly.\n\n# $maxDraws is the largest number of random draws allowed for a single sample.\n# Drawing nearly the whole population is as cheap as drawing almost none of it, so\n# raising numDraws is a fix as well as lowering it. "could need" rather than "would\n# need": each category is counted at the most its draw could cost, so the count\n# these parameters are refused on is an upper bound on the work they really take.\nsample-multivariate-draws-too-many =\n    Drawing { $numDraws } items from a population of { $numTotal } split into { $numCategories } categories could need more than { $maxDraws } random draws for each sample, which would stop the page from responding. Reduce numDraws, bring it closer to numTotal, or use fewer categories.\n\n# `type` has no default, so this is what leaving it off gets. A type the attribute\n# does not recognize falls back to no type at all and reaches this message too,\n# after a separate one naming the value that was rejected — hence "no distribution\n# was named" rather than wording that assumes the attribute is missing.\nsample-multivariate-type-not-specified =\n    No multivariate distribution was named for this random variable, so nothing was sampled. Give the type attribute the name of a distribution, such as `type="hypergeometric"`.\n\n## Counting operators\n\n# Raised by `<tally>` when the author named `categories` explicitly and some\n# values matched none of them, so those values were not counted anywhere. Info\n# rather than a warning: a list fed by an input legitimately holds\n# non-categories while a student is typing. It deliberately does not say how\n# many such values there were: the diagnostics queue is append-only and\n# deduplicates by message, so a count would leave one permanent entry behind\n# for every number of stray values the list passed through while being typed.\ntally-values-outside-categories =\n    Some values matched none of the declared categories, so they were not counted.\n\n# Raised by `<tally>` when `categories` names the same category more than once.\n# A warning rather than info: unlike a stray value, a repeated category is a\n# property of what the author wrote, so it stays true of a settled document. The\n# message says what the counts will be, since the behavior is defensible but not\n# what an author who repeated a category by accident expects.\ntally-repeated-category =\n    `categories` names the same category more than once. Each count reports the values equal to its own category, so the repeated ones all report the same number.\n\n# Raised by `<binCounts>` when no `bins` attribute was given, so there are no\n# intervals to count into. $component names the tag the author wrote.\nbin-counts-missing-bins =\n    `{ $component }` has no `bins` cut points, so there are no intervals to count into and it gives no counts.\n\n# Raised by `<binCounts>` when `bins` held fewer than the two cut points needed\n# to define a single interval. $count is how many were given, and can be 0 or 1,\n# so the sentence is worded to read for both without forking on the number.\nbin-counts-too-few-cut-points =\n    `bins` needs at least 2 cut points to define an interval, but received { $count }.\n\n# Raised by `<binCounts>` when its values are not all numeric, so they cannot be\n# placed between numeric cut points. $component names the tag the author wrote.\nbin-counts-values-not-numeric =\n    `{ $component }` can only count numeric values into bins, but not every value it was given is numeric. All counts are 0.\n\n# Raised by `<binCounts>` when the `bins` cut points do not climb: one is\n# smaller than the one before it, so a bin would run backwards and its count\n# would come out negative, or one is not a number at all, which has the same\n# effect. Equal adjacent cut points are accepted, so the message says "at least\n# as large as" rather than "increasing": what is rejected is a decrease, not a\n# failure to strictly increase. Between two interior cut points that names an\n# empty bin; at either end the outermost-edge rule can still put a value in it.\nbin-counts-cut-points-decreasing =\n    Each `bins` cut point must be a number at least as large as the one before it, but one is not a number or is smaller than its predecessor, so no counts were produced.\n\n## Charts\n\n# Raised by `<chart type="bar">` when a value is not a finite number, so it gets\n# no bar. The alternative reading of a missing bar is a value of zero, which the\n# author cannot distinguish by looking, so the absence is stated rather than left\n# to be inferred. No count: the queue is append-only and deduplicates by message,\n# and the number of such values changes as an input is typed into. (The message\n# key is `bar-chart-…` because a code names one situation forever and this one\n# was issued while the component was still spelled `<barChart>`.)\nbar-chart-values-not-drawable =\n    A bar chart draws no bar for a value that is not a finite number, so those places on the chart are empty rather than zero.\n\n# Raised by `<chart type="bar">` when `barWidth` is outside the (0, 1] range a\n# fraction of a bar\'s slot can take. $barWidth is what the author wrote.\nbar-chart-bar-width-invalid =\n    `barWidth` must be greater than 0 and at most 1, but { $barWidth } was given. Using 0.8 instead.\n\n# `type` has no default, so this is what `<chart>` on its own gets. A type the\n# attribute does not recognize falls back to no type at all and reaches this\n# message too, after a separate one naming the value that was rejected — hence\n# "no chart type was named" rather than wording that assumes the attribute is\n# missing.\nchart-type-not-specified =\n    No chart type was named, so nothing was drawn. Give the type attribute the name of a chart, such as `type="bar"`.\n\n# Raised by `<chart>` when values are written beside its `<series>` children.\n# A value outside every series belongs to no group of the data, so there is no\n# place on the chart to draw it; saying so matters because the alternative\n# reading of the missing bar is that the value was zero.\nchart-values-outside-series =\n    A chart with `<series>` children draws only the values inside them, so values written beside a series were not drawn. Move them into a series of their own.\n';
+const diagnostics = '# Errors and warnings surfaced to the reader or author. Produced by the worker\n# but addressed to whoever is looking at the screen, so these are selected by\n# `uiLocale`, not `documentLocale`.\n#\n# Message ids are lower-kebab-case Fluent identifiers, optionally with a\n# single `.attribute` suffix (`invalid-attribute-value`).\n#\n# Reached by stable diagnostic code rather than by a literal `t("key")` call:\n# `DIAGNOSTIC_CODES` in `src/diagnostics.ts` maps `doenet-w0001` to the id\n# below, and `lint:i18n` treats that registry as the call site. Adding a\n# message here without registering a code for it fails the lint as an orphan.\n#\n# Translators: `through`, `endpoint`, `midpointOffset`, `numDimensions` and the\n# like are DoenetML attribute names. They are part of the language, not prose,\n# and must be left in English exactly as written.\n\n## `<lineSegment>`\n\n# $attributes is a list of attribute names; $attributesCount is its length.\nline-segment-attributes-ignored-with-endpoints =\n    { $attributesCount ->\n        [one] { $attributes } is ignored when two endpoints are specified\n       *[other] { $attributes } are ignored when two endpoints are specified\n    }\n\n# $attributes is a list of attribute names; $attributesCount is its length.\nline-segment-attributes-ignored-with-endpoint-and-midpoint =\n    { $attributesCount ->\n        [one] { $attributes } is ignored when an endpoint and a midpoint are both specified\n       *[other] { $attributes } are ignored when an endpoint and a midpoint are both specified\n    }\n\nline-segment-midpoint-offset-without-midpoint = midpointOffset has no effect without a midpoint\n\n## `<line>`\n\nline-points-undetermined-dimensions = Line through points of undetermined dimensions.\n\nline-points-too-few-dimensions = Line must be through points of at least two dimensions.\n\n# $variables is a bare enumeration of variable names, not an "and" list.\nline-points-depend-on-variables = Line is through points that depend on variables: { $variables }.\n\nline-equation-invalid-format = Invalid format for equation of line in variables { $variable1 } and { $variable2 }.\n\n## `<ray>`\n\nray-overprescribed-through = Ray is prescribed by through, endpoint, and direction.  Ignoring specified through.\n\nray-dimension-mismatch = numDimensions mismatch in ray.\n\n## `<vector>`\n\nvector-overprescribed-head = Vector is prescribed by head, tail, and displacement.  Ignoring specified head.\n\nvector-dimension-mismatch = numDimensions mismatch in vector.\n\n## Attracting and constraining\n\n# $component is the DoenetML tag of the child that was named, e.g. "polygon".\nattract-to-without-nearest-point = Cannot attract to a `<{ $component }>` as it doesn\'t have a nearestPoint state variable.\n\nconstrain-to-without-nearest-point = Cannot constrain to a `<{ $component }>` as it doesn\'t have a nearestPoint state variable.\n\nconstrain-to-interior-without-nearest-point = Cannot constrain to interior of a `<{ $component }>` as it doesn\'t have a nearestPoint state variable.\n\n## `<choiceInput>`\n\n# Translators: `labelPosition` is an attribute name and stays in English.\nchoice-input-label-position-ignored = labelPosition is ignored for non-inline choiceInput\n\n## Ordering children by index\n##\n## These name the component in prose rather than as a tag, matching how the\n## messages have always read. The component names stay in English; the nouns\n## around them are prose and should be translated.\n\nchoice-input-indices-count-mismatch = Ignoring indices specified for choiceInput as number of indices doesn\'t match number of choice children.\n\npretzel-indices-count-mismatch = Ignoring indices specified for problem as number of indices doesn\'t match number of problem children.\n\nshuffle-indices-count-mismatch = Ignoring indices specified for shuffle as number of indices doesn\'t match number of components.\n\n# $component is `choiceInput`, `pretzel` or `shuffle` — a DoenetML component\n# name, so it stays in English.\nindices-ignored-out-of-range = Ignoring indices specified for { $component } as some indices out of range.\n\npretzel-indices-repeated = Ignoring indices specified for pretzel as some indices are repeated.\n\npretzel-circuit-first-index = Ignoring indices specified for pretzel in circuit mode as the first index must be 1.\n\n## `<shuffle>` and `<sort>`\n\n# $component is `shuffle` or `sort`. These two components accept the same\n# children and fail the same ways, so they share their messages.\nstring-children-need-type = For `<{ $component }>` to work with string children, a `type` attribute must be specified.\n\n# $type is what the author wrote; math, text, number and boolean are attribute\n# values and stay in English.\ninvalid-type-defaulting-to-math = Invalid type { $type } for { $component } component. Must be one of math, text, number, or boolean. Defaulting to math.\n\n# Raised when `type` names something that is not one of the four readings. The\n# value is dropped rather than replaced by a guess, so the children are read as\n# though no type had been written. $type is what the author wrote.\ninvalid-type-ignored =\n    Invalid type { $type } for { $component } component. Must be one of math, text, number, or boolean. Ignoring it and reading the values as though no type had been given.\n\n# $value is the string child that could not be used.\nstring-not-valid-component-to-arrange = String "{ $value }" is not a valid component to { $component }. Ignoring.\n\n## Types and variables\n\ninvalid-type-defaulting-to-number = Invalid type { $type }, setting type to number.\n\ninvalid-variable-value = Invalid value of a variable: `{ $value }`\n\n## Variants\n\n# $index is what the author wrote, reproduced verbatim rather than as a number:\n# it reached this message precisely because it was not one.\nvariant-index-must-be-number = Variant index { $index } must be a number\n\nvariant-index-must-be-integer = Variant index { $index } must be an integer\n\n## `<sideBySide>`\n\n# $component is `sideBySide` or `sbsGroup`.\nside-by-side-absolute-widths = `<{ $component }>` is not implemented for absolute measurements. Setting widths to relative.\n\nside-by-side-absolute-margins = `<{ $component }>` is not implemented for absolute measurements. Setting margins to relative.\n\nside-by-side-no-block-child = Invalid `<{ $component }>`: it must have at least one block child.\n\n## `<label>`\n\n# Translators: `for` is an attribute name and stays in English.\nlabel-for-ignored-on-graphical = The `for` attribute on graphical `<label>` is ignored.\n\nlabel-for-must-resolve-to-one = The `for` attribute on `<label>` must resolve to exactly one component.\n\nlabel-for-unresolved = The `for` attribute on `<label>` could not be resolved to a component.\n\nlabel-for-answer-with-authored-inputs = The `for` attribute on `<label>` references an `<answer>` with explicitly authored inputs; reference the input directly.\n\nlabel-for-answer-without-input = The `for` attribute on `<label>` references an `<answer>` without an input to label.\n\nlabel-for-must-reference-input-or-answer = The `for` attribute on `<label>` must reference an input or an answer.\n\n## Accessibility\n\n# $component is a DoenetML tag, e.g. "graph" or "image".\naccessibility-short-description-or-decorative = For accessibility, `<{ $component }>` must either have a short description or be specified as decorative.\n\naccessibility-video-short-description = For accessibility, `<video>` must have a short description.\n\naccessibility-input-short-description-or-label = For accessibility, `<{ $component }>` must have a short description or a label.\n\n# The companion to the message above, for the input an `<answer>` creates on the\n# author\'s behalf. Two messages rather than one with the subject passed in: the\n# subject is a phrase here, not a name, and a phrase handed over as an argument\n# would never reach a translator.\naccessibility-answer-input-short-description-or-label = For accessibility, an `<answer>` creating an input must have a short description or a label.\n\naccessibility-short-description-contains-math = Short descriptions should not contain math components such as `<{ $component }>`. Spell out any math with words.\n\n# $colorName is an attribute name and stays in English. $ratio and $threshold\n# are contrast ratios; $mode says which theme the shortfall was measured in,\n# and is `dark` or `light`.\naccessibility-section-title-insufficient-contrast =\n    { $mode ->\n        [dark] { $colorName } has insufficient contrast for the section heading text (dark mode) ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; requires at least { $threshold }:1).\n       *[other] { $colorName } has insufficient contrast for the section heading text ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; requires at least { $threshold }:1).\n    }\n\n## `<circle>`\n\n# $count is the number of through points.\ncircle-through-points-non-numerical = Haven\'t implemented `<circle>` through { $count } points in case where the points don\'t have numerical values.\n\ncircle-too-many-through-points = Cannot calculate circle through more than 3 points.\n\ncircle-overprescribed-radius-center-points = Cannot calculate circle with specified radius, center and through points.\n\ncircle-center-with-multiple-points = Cannot calculate circle with specified center through more than 1 point.\n\n# $distance and $radius arrive as strings, not numbers: $radius is the author\'s\n# own value echoed back for diagnosis, and formatting it as a quantity would\n# round a radius of 0.0001 away to 0.\ncircle-radius-too-small = Cannot calculate circle: given that the distance between the two points is { $distance }, the specified radius { $radius } is too small.\n\ncircle-radius-with-many-points = Cannot create circle through more than two points with a specified radius.\n\ncircle-invalid-center-or-through-points = Invalid center or through points of circle.\n\ncircle-radius-center-with-multiple-points = Cannot calculate radius of circle with specified center through more than 1 point.\n\ncircle-change-radius-non-numerical = Cannot change radius of circle with non-numerical through points\n\ncircle-radius-with-points-non-numerical = Cannot create circle through more than one point with specified radius when don\'t have numerical values.\n\ncircle-change-center-non-numerical = Haven\'t implemented changing center of circle through points with non numerical values.\n\n## `<function>`\n\n# Two independent counts in one sentence, so the variants multiply out. A\n# select\'s variants each need their own line, so the inner one spans lines too;\n# that is safe because newlines inside a placeable never reach the rendered\n# value. Only text continuing onto a further line would.\nfunction-domain-insufficient-dimensions =\n    { $intervals ->\n        [one] Insufficient dimensions for domain for function. Domain has { $intervals } interval but the function has { $inputs ->\n            [one] { $inputs } input\n           *[other] { $inputs } inputs\n        }.\n       *[other] Insufficient dimensions for domain for function. Domain has { $intervals } intervals but the function has { $inputs ->\n            [one] { $inputs } input\n           *[other] { $inputs } inputs\n        }.\n    }\n\nfunction-domain-invalid-format = Invalid format for domain for function.\n\n# $type is what was being read off the point. It selects the wording rather\n# than being substituted into it: "maximum", "slope" and the rest are English\n# nouns, and a noun handed over as an argument would never reach a translator.\n# The catch-all reproduces the pre-catalog behavior for a value not listed here.\nfunction-ignoring-non-numerical =\n    { $type ->\n        [maximum] Ignoring non-numerical maximum of function.\n        [minimum] Ignoring non-numerical minimum of function.\n        [extremum] Ignoring non-numerical extremum of function.\n        [point] Ignoring non-numerical point of function.\n        [slope] Ignoring non-numerical slope of function.\n       *[other] Ignoring non-numerical { $type } of function.\n    }\n\nfunction-ignoring-empty =\n    { $type ->\n        [maximum] Ignoring empty maximum of function.\n        [minimum] Ignoring empty minimum of function.\n        [extremum] Ignoring empty extremum of function.\n        [point] Ignoring empty point of function.\n       *[other] Ignoring empty { $type } of function.\n    }\n\nfunction-points-too-close = Function contains two points with locations too close together. Can\'t define function.\n\nfunction-iterates-input-output-mismatch =\n    { $inputs ->\n        [one] Function iterates are possible only if the number of inputs of the function is equal to the number of outputs. This function has { $inputs } input and { $outputs ->\n            [one] { $outputs } output\n           *[other] { $outputs } outputs\n        }.\n       *[other] Function iterates are possible only if the number of inputs of the function is equal to the number of outputs. This function has { $inputs } inputs and { $outputs ->\n            [one] { $outputs } output\n           *[other] { $outputs } outputs\n        }.\n    }\n\n## `<sequence>`\n\nsequence-invalid-length = Invalid length of sequence.  Must be a non-negative integer.\n\n# $type is a sequence type: number, letters, or math.\nsequence-invalid-step = Invalid step of sequence.  Must be a number for sequence of type { $type }.\n\n# $attribute is `from` or `to` — an attribute name, so it stays in English.\nsequence-invalid-endpoint-number = Invalid "{ $attribute }" of number sequence.  Must be a number.\n\nsequence-invalid-endpoint-letters = Invalid "{ $attribute }" of letters sequence.  Must be a letter combination.\n\nsequence-invalid-endpoint = Invalid "{ $attribute }" of sequence.\n\nselect-from-sequence-coprime-not-numbers = coprime ignored since not selecting numbers\n\nselect-from-sequence-coprime-with-exclude-combinations = coprime ignored since excludeCombinations specified\n\n## Resolving a `target`\n##\n## Raised by the components that take a `target` attribute. They resolve it\n## through the same code and fail the same two ways, so they share these two\n## messages rather than spelling each one out per component: $source is the tag\n## of the component that raised it, part of the DoenetML language, so it stays\n## in English.\n\ntarget-not-found = Invalid target for `<{ $source }>`: cannot find target.\n\n# $property is the state variable that was looked for; $component is the tag it\n# was looked for on.\ntarget-state-variable-not-found = Invalid target for `<{ $source }>`: cannot find a state variable named "{ $property }" on a `<{ $component }>`.\n\n## `<odeSystem>`\n\node-system-variables-match-independent = Variables of `<odeSystem>` must be different than independent variable.\n\node-system-duplicate-variable-names = Can\'t define ODE RHS functions with duplicate dependent variable names.\n\node-system-rhs-function-error = Cannot define ODE RHS function.  Error creating mathjs function.\n\n## `<angle>`, `<parabola>`, and `<intersection>`\n\n# $count is how many line children were found.\nangle-too-many-lines = Cannot define an angle between { $count } lines\n\nangle-invalid-through-point = Invalid point in through of `<angle>`\n\nparabola-vertex-too-many-points = Haven\'t implemented parabola with vertex through more than 1 point.\n\nparabola-too-many-points = Haven\'t implemented parabola through more than 3 points.\n\nintersection-too-many-items = Haven\'t implemented intersection for more than two items\n\n## Other math components\n\nionic-compound-not-two-ions = Have not implemented ionic compound for anything other than two ions.\n\nionic-compound-needs-cation-and-anion = Ionic compound implemented only for one cation and one anion.\n\n# $equation is the equation as the author wrote it.\nsolve-equations-cannot-evaluate = Cannot solve equation as could not evaluate equation: { $equation }\n\n# Translators: `operandNumber` is an attribute name and stays in English.\nmath-operators-operand-number-required = Must specify a operandNumber when extracting a math operand.\n\neigen-decomposition-failed = Could not calculate eigenvalues of matrix\n\n## `<matchesPattern>`\n\n# Translators: `parameters` is an attribute name and stays in English.\n# $parameters lists the parameters as the author wrote them;\n# $parametersCount is how many there were.\nmatches-pattern-parameter-not-in-pattern =\n    { $parametersCount ->\n        [one] `<matchesPattern>`: the parameter { $parameters } does not occur in the pattern, so it will always match a blank.\n       *[other] `<matchesPattern>`: the parameters { $parameters } do not occur in the pattern, so they will always match a blank.\n    }\n\n## `<graph>`\n\n# Translators: grid is an attribute name and none, medium and dense are its\n# values; all four stay in English, as does the example. $grid is the value the\n# author wrote, reproduced verbatim — it reached this message precisely because\n# it was not one of the forms listed.\ngraph-grid-invalid = `<graph>`: cannot interpret grid="{ $grid }". It must be none, medium, dense, or two positive numbers separated by a space, such as grid="1 0.5". No grid is drawn.\n\n## `<slopeField>` and `<vectorField>`\n\n# $component is the field\'s tag and $alternative the sibling field component\'s,\n# or `none` when the function would not suit it either; both are DoenetML tags\n# and stay in English, as do the example expressions. $expected is how many\n# outputs the component needs, $found how many the given function has. What a\n# field draws a mark from is the function\'s outputs, so the wrong number of\n# them means there is nothing to draw — and the author almost always wanted the\n# other component.\nfield-function-wrong-num-outputs =\n    `<{ $component }>` needs a function with { $expected ->\n        [one] one output, the slope y\' at each point, such as `y - x`\n       *[other] two outputs, the vector at each point, such as `(y, -x)`\n    }, but the function it was given has { $found ->\n        [one] { $found } output\n       *[other] { $found } outputs\n    }. { $alternative ->\n        [none] Nothing is drawn.\n       *[other] `<{ $alternative }>` is the component for that function. Nothing is drawn.\n    }\n\n# Translators: retired. `function` is an attribute name and stays in English.\n# It warned that a field had been given its function both as an attribute and\n# inside the component; the attribute no longer exists, so the two can no\n# longer disagree. Kept because diagnostic codes are never reused.\nfield-function-attribute-ignored-with-child = The `function` attribute is ignored because the function is also given inside the component; the one inside is used. Give the function only one of the two ways.\n\n# Translators: `variables` and `function` are a DoenetML attribute and tag and\n# stay in English, as does $component, the field\'s own tag. The attribute names\n# the inputs of an expression written directly inside the component; when there\n# is no such expression there is nothing for it to name, and $reason says which\n# of the two ways that happened.\nfield-variables-ignored =\n    `<{ $component }>`: the `variables` attribute names the variables of an expression written directly inside the component. { $reason ->\n        [function-child] The function here is given as a `<function>` child, which names its own variables, so `variables` is ignored.\n       *[no-expression] No such expression is given here, so `variables` is ignored.\n    }\n\n## PreFigure renderer\n\n# Translators: xLabelPosition, yLabelPosition and their values are attribute\n# names and stay in English, as does the renderer\'s name.\nprefigure-x-label-position-unsupported = `<graph>`: xLabelPosition="left" is not supported in prefigure renderer; using right-position behavior.\n\nprefigure-y-label-position-unsupported = `<graph>`: yLabelPosition="bottom" is not supported in prefigure renderer; using top-position behavior.\n\nprefigure-invalid-axis-bounds = `<graph>`: invalid axis bounds for prefigure conversion; using default bbox (-10,-10,10,10).\n\nprefigure-invalid-width = `<graph>`: invalid width for prefigure conversion; using default diagram width 425.\n\nprefigure-invalid-aspect-ratio = `<graph>`: invalid aspectRatio for prefigure conversion; using default aspect ratio 1.\n\n# Translators: the renderer\'s name, prefigure, stays in English. "grid" here is\n# the coordinate grid itself rather than the attribute that asks for one, so it\n# is prose and is translated.\nprefigure-grid-spacing-too-fine = `<graph>`: the grid spacing is too fine for the axis limits; the grid is omitted in the prefigure renderer.\n\nprefigure-annotations-not-rendered = `<graph>`: annotations will not be rendered when not using the PreFigure renderer.\n\nmultiple-annotations-children = Multiple `<annotations>` children found in `<graph>`; all but the last one are ignored.\n\n## Referring to other components\n##\n## `<updateValue>`\'s own "cannot find target" messages are not here: it\n## resolves a target the same way `<animateFromSequence>` does and fails the\n## same ways, so the two share `target-not-found` and\n## `target-state-variable-not-found` above.\n\ncopy-unrecognized-component-type = Cannot extend or copy an unrecognized component type: { $type }.\n\ncopy-prop-not-found = Could not find prop { $property } on a component of type { $component }\n\ncollect-no-source = No source found for collect.\n\ncollect-invalid-component-type = Cannot collect components of type `<{ $component }>` as it is an invalid component type.\n\n# $reference is the reference exactly as the author wrote it, `$` and all —\n# the `$p.styleDescription[1]` of `<text extend="$p.styleDescription[1]" />`.\n# An index only means something applied to an array, and the thing named here\n# is not one. The reference is quoted back rather than explained because the\n# text in front of the author is the only part of this they can act on: the\n# state variable and component index the core knows about are its own business\n# and go to the console instead.\nreference-index-unavailable = Cannot reference index `{ $reference }`\n\n## `<callAction>`\n\n# $action is the `actionName` the author asked for, part of the DoenetML\n# language, so it stays in English. $reference is the `target` as written.\ncomponent-action-unavailable = Cannot call { $action } on component `{ $reference }`\n\n## `<dataFrame>`\n\n# $componentIdx is an internal index, passed as a string so it is not grouped\n# like a quantity; the odd spacing before the colon is reproduced from the\n# original message.\ndata-frame-inconsistent-row-lengths = Data has invalid shape.  Rows has inconsistent lengths. Found in componentIdx :{ $componentIdx }\n\ndata-frame-duplicate-column-names = Data has duplicate column names.  Found in componentIdx :{ $componentIdx }\n\ndata-frame-missing-column-name = Data is missing a column name.  Found in componentIdx :{ $componentIdx }\n\n## `<answer>` and scoring\n\nanswer-award-depends-on-own-response = An award for this answer is based on the answer tag\'s own submitted response, which will lead to unexpected behavior.\n\n# Translators: maxNumAttempts and sectionWideCheckWork are attribute names.\nanswer-max-num-attempts-in-section-wide-check-work = Setting `maxNumAttempts` on an `<answer>` inside a container with `sectionWideCheckWork` has no effect, as the number of attempts is controlled by the container. Set `maxNumAttempts` on the container instead.\n\nnested-section-wide-check-work-max-num-attempts = Setting `maxNumAttempts` on a container with `sectionWideCheckWork` that is inside another container with `sectionWideCheckWork` has no effect, as the number of attempts is controlled by the outer container. Set `maxNumAttempts` on the outer container instead.\n\n# $attributes is a list of attribute names; $attributesCount is its length.\nanswer-attributes-need-symbolic-equality =\n    { $attributesCount ->\n        [one] The { $attributes } attribute will have no effect without symbolicEquality set.\n       *[other] The { $attributes } attributes will have no effect without symbolicEquality set.\n    }\n\nanswer-invalid-type = Invalid type for answer: { $type }\n\n## `<module>`, `<conditionalContent>`, `<slider>`, `<pretzel>`\n\nmodule-attribute-child-needs-name = Since the component `<{ $component }>` does not have a name, it cannot be used for a module attribute\n\nmodule-attribute-name-already-defined = The component `<{ $component } name="{ $name }">` cannot be used as an attribute for a module because the `<module>` component type already has a "{ $name }" attribute defined.\n\nconditional-content-condition-ignored = Attribute `condition` is ignored on a `<conditionalContent>` component with case or else children.\n\nslider-markers-type-mismatch = Markers type doesn\'t match slider type.\n\npretzel-problem-needs-statement-and-answer = Invalid pretzel: each `<problem>` must contain one `<statement>` and one `<answer>`.\n\npretzel-circuit-first-problem-distractor = Invalid pretzel: in mode="circuit", the first `<problem>` cannot be a distractor.\n\n## Attribute values\n\n# $values is a list of the values that were rejected, each already in\n# backticks; $valuesCount is how many there were.\nattribute-invalid-values =\n    { $valuesCount ->\n        [one] Invalid value { $values } for attribute `{ $attribute }`; ignoring.\n       *[other] Invalid values { $values } for attribute `{ $attribute }`; ignoring.\n    }\n\nattribute-must-be-references = Invalid value `{ $value }` for attribute `{ $attribute }`. Attribute must be composed of references that begin with a `$`.\n\n# $names is a list of the rejected names, each already in single quotes.\nmath-input-invalid-function-names = <mathInput>: ignored invalid function name(s) in { $attribute }: { $names }. Each name\'s display segment must be at least 2 characters (letters or dashes); an optional `|<mathspeak alternative>` suffix may follow.\n\n## Building components from the source\n\n# Raised while the source is being turned into components, by throwing rather\n# than by building a record: the thrower is caught, the component becomes an\n# `_error`, and the diagnostic is re-raised from it.\n\ncomponent-type-invalid = Invalid component type: `<{ $componentType }>`\n\nattribute-repeated = Cannot repeat attribute { $attribute }.\n\nattribute-invalid-for-component = Invalid attribute "{ $attribute }" for a component of type `<{ $componentType }>`.\n\n## Style definition contrast\n\n# $context names the pair being compared, $mode which colour scheme it was\n# rendered in. Both are symbolic — the phrase is chosen here so a translator\n# can rewrite it, rather than being handed over already in English.\nstyle-definition-insufficient-contrast =\n    Style definition { $styleNumber } has insufficient contrast for { $context ->\n        [text-on-background] text color against background color\n        [high-contrast] high-contrast color against the canvas\n        [line] line color against the canvas\n        [marker] marker color against the canvas\n       *[text-on-canvas] text color against the canvas\n    }{ $mode ->\n        [dark] { " (dark mode)" }\n       *[light] { "" }\n    } ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; requires at least { $threshold }:1).\n\n# $suggestion says whether a concrete replacement colour could be computed.\n# The attribute names and colour values in the `available` branch are\n# DoenetML source, not prose, and stay as they are in every language.\nstyle-definition-dark-mode-text-background-contrast =\n    Although style definition { $styleNumber } has specified colors that provide sufficient contrast for light mode, the dark-mode colors derived from these values have insufficient contrast for the text color against the background color ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; requires at least { $threshold }:1). { $suggestion ->\n        [available] To ensure sufficient contrast in dark mode, either increase the light-mode contrast (e.g., set { $lightAttribute }="{ $lightColor }") or override the dark-mode color (e.g., set { $darkAttribute }="{ $darkColor }").\n       *[none] To ensure sufficient contrast in dark mode, increase the light-mode contrast or override the derived colors with textColorDarkMode and/or backgroundColorDarkMode.\n    }\n\nstyle-definition-dark-mode-text-canvas-contrast =\n    Although style definition { $styleNumber } has a specified text color that provides sufficient contrast for light mode, the dark-mode text color derived from this value has insufficient contrast against the canvas ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; requires at least { $threshold }:1). { $suggestion ->\n        [available] To ensure sufficient contrast in dark mode, either increase the light-mode contrast (e.g., set textColor="{ $lightColor }") or override the dark-mode color (e.g., set textColorDarkMode="{ $darkColor }").\n       *[none] To ensure sufficient contrast in dark mode, increase the light-mode contrast or override the derived color with textColorDarkMode.\n    }\n\nsection-multiple-style-palettes = A section can select only one <stylePalette>; using the last one.\n\n## Unique variants\n\n# Explanations of why a component\'s unique variants could not be worked out.\n# $component is the tag that could not be analyzed and stays as written; the\n# reason is a separate message per situation, so a host can tell them apart by\n# code and a translator sees a whole sentence rather than a fragment.\n\nvariant-num-to-select-not-non-negative-integer = cannot determine unique variants of { $component } as numToSelect isn\'t a non-negative integer.\n\nvariant-num-to-select-not-constant-number = cannot determine unique variants of { $component } as numToSelect isn\'t constant number.\n\nvariant-with-replacement-not-constant-boolean = cannot determine unique variants of { $component } as withReplacement isn\'t constant boolean.\n\nvariant-select-weight-disables-unique = Unique variants for select disabled if have an option with selectWeight or selectForVariants specified\n\nvariant-coprime-undetermined = cannot determine unique variants of { $component } as cannot determine coprime is always false.\n\n# $attribute is an attribute name (`from`, `to`, `step`, `sort`, `length`) and\n# stays as written.\nvariant-attribute-not-constant = cannot determine unique variants of { $component } as { $attribute } isn\'t a constant.\n\nvariant-attribute-not-number = cannot determine unique variants of { $component } as { $attribute } isn\'t a number.\n\n# $type is the sequence type the component was declared with. $expected names\n# what the value had to be, symbolically, because which one applies depends on\n# both the type and the attribute.\nvariant-attribute-wrong-type-for-sequence =\n    cannot determine unique variants of { $component } of { $type } type as { $attribute } isn\'t { $expected ->\n        [letters-combination] a combination of letters\n        [math-expression] a valid math expression\n        [integer] an integer\n       *[number] a number\n    }.\n\nvariant-length-not-integer = cannot determine unique variants of { $component } as length isn\'t an integer.\n\nvariant-sort-not-implemented = have not implemented unique variants of a { $component } with sort\n\nvariant-exclude-combinations-not-implemented = have not implemented unique variants of a { $component } with excludeCombinations\n\nvariant-math-exclude-not-implemented = have not implemented unique variants of a { $component } of type math with exclude\n\nvariant-non-constant-exclude-not-implemented = have not implemented unique variants of a { $component } with non-constant exclude\n\n## PreFigure conversion\n\n# $subject identifies the component the warning is about, already written as\n# `<tag>` or `<tag> (name)`. It is composed in code rather than here because\n# Fluent terms cannot take a variable as an argument, so a shared subject\n# fragment cannot be parameterized from the catalog. It holds only a tag name,\n# a component name and punctuation — never a word — which is why a descendant\n# with no type reads `<?>` rather than `<unknown>`.\n\nprefigure-descendant-unsupported = { $subject }: unsupported in graph prefigure renderer; descendant skipped.\n\nprefigure-descendant-invalid-geometry = { $subject }: non-finite or incomplete geometry; descendant skipped.\n\nprefigure-curve-label-omitted = { $subject }: labels are not supported on converted curve elements; label omitted.\n\nprefigure-curve-unsupported-definition-type = { $subject }: unsupported curve function definition type \'{ $definitionType }\'; descendant skipped.\n\nprefigure-region-flip-functions-unsupported = { $subject }: unsupported flipFunctions attribute on regionBetweenCurves; descendant skipped.\n\nprefigure-region-non-formula-child = { $subject }: only formula-typed child functions are supported on regionBetweenCurves; descendant skipped.\n\n# $labelKind says which family of object carried the label, since the advice\n# is the same but the object is not.\nprefigure-label-position-unsupported =\n    { $subject }: unsupported labelPosition \'{ $labelPosition }\' for { $labelKind ->\n        [line-family] line-family label\n       *[point] point label\n    }; default PreFigure alignment used.\n\nprefigure-fill-style-unsupported = { $subject }: fill style \'{ $fillStyle }\' is unsupported by PreFigure; falling back to a solid fill.\n\nprefigure-line-style-unknown = { $subject }: unknown line style \'{ $lineStyle }\' omitted from PreFigure output.\n\nprefigure-marker-style-mapped-to-diamond = { $subject }: marker style \'{ $markerStyle }\' mapped to PreFigure style \'diamond\'.\n\nprefigure-marker-style-unsupported = { $subject }: marker style \'{ $markerStyle }\' is unsupported by PreFigure; default style used.\n\n## PreFigure annotations\n\nannotation-ref-unresolvable = `<annotation>`: invalid `ref`; cannot resolve target. Annotation omitted.\n\nannotation-ref-multiple-targets = `<annotation>`: `ref` resolved to multiple targets; using the first target.\n\nannotation-ref-outside-graph = `<annotation>`: invalid `ref`; target is outside the containing graph. Annotation omitted.\n\nannotation-ref-unsupported-target = `<annotation>`: invalid `ref`; target is not a supported graphical object in prefigure conversion. Annotation omitted.\n\nannotation-text-missing = `<annotation>`: missing or empty `text`; emitting empty text.\n\n## Composites and references\n\n# $componentType is the type the composite was asked to create, when it is\n# known; `none` when the composite did not say.\ncomposite-circular-dependency =\n    { $componentType ->\n        [none] Circular dependency detected.\n       *[other] Circular dependency detected involving `<{ $componentType }>` component.\n    }\n\n# $reference is the reference as the author wrote it, already carrying its `$`.\nreference-no-referent = No referent found for reference: `{ $reference }`\n\nreference-multiple-referents = Multiple referents found for reference: `{ $reference }`\n\n## Children that do not match\n\nchildren-invalid-attribute-format = Invalid format for attribute { $attribute } of `<{ $componentType }>`.\n\n# $children is the list of child types that did not match, already joined.\nchildren-invalid = Invalid children for `<{ $componentType }>`: Found invalid children: { $children }\n\n## Falling back to a default\n\n# The attribute had a default to fall back to, and the message names it: the\n# component went on to behave as though the author had written that value, and\n# an author not told which one goes looking for the difference in the wrong\n# place.\nattribute-value-invalid-using-default = Invalid value `{ $value }` for attribute `{ $attribute }`, using value `{ $default }`\n\n# The same rejection where the attribute has no default to fall back to, so\n# nothing stood in for the value and the component behaves as though the\n# attribute had not been written. A separate message rather than the one above\n# with a blank in it: "using value `null`" would describe a substitution that\n# did not happen, and name a value no author could have typed. What follows is\n# usually a second message from the component itself, saying what it did\n# without the attribute.\nattribute-value-invalid-ignoring = Invalid value `{ $value }` for attribute `{ $attribute }`, ignoring it\n\n## Loading a DoenetML version\n\n# $fallback is the version that will be used instead, or `none` when the\n# embedding page named a standalone bundle of its own.\ndoenetml-version-not-found =\n    { $fallback ->\n        [none] DoenetML version { $version } not found.\n       *[other] DoenetML version { $version } not found. Falling back to version { $fallback }\n    }\n\n## Reading the DoenetML\n\n# The parser\'s own diagnostics: what the author sees before anything runs, and\n# for a beginner usually the first Doenet message they ever read.\n#\n# The parser writes its English beside the code rather than rendering it from\n# here, because `@doenet/parser` is inside the language-server bundle and a\n# catalog there is dead weight on the editor\'s critical path\n# (`packages/lsp/scripts/check-server-bundle.mjs` fails if one arrives). The\n# two copies are held together by a test in that package, which parses a\n# corpus and asserts every coded error renders to exactly what the parser\n# wrote — so a message edited here without its counterpart fails there.\n#\n# $tag, $value, $attribute and their relatives quote the author\'s own source\n# back at them and stay exactly as written. The `Invalid DoenetML: ` opening is\n# repeated in each message instead of being a shared term: a term a locale\n# forgets to define renders as its own name, and a prefix on fifteen messages\n# is not worth that failure mode.\n\nparse-invalid-doenetml = Invalid DoenetML: { $content }\n\nparse-tag-missing-close-tag = Invalid DoenetML: The tag `{ $tag }` has no closing tag. Expected a self-closing tag or a `</{ $tagName }>` tag.\n\nparse-tag-error = Invalid DoenetML: Error in tag `<{ $tagName }>`\n\nparse-attribute-missing-value = Invalid DoenetML: Invalid attribute `{ $attribute }` appears to be missing a value.\n\nparse-attribute-invalid = Invalid DoenetML: Invalid attribute `{ $attribute }`\n\nparse-attribute-value-invalid = Invalid DoenetML: Invalid attribute value `{ $value }`\n\n# $quote is the quote character that would balance the pair: `"` or `\'`.\nparse-attribute-value-quote-mismatch = Invalid DoenetML: Invalid attribute value `{ $value }`. The quote marks do not match. You appear to be missing a `{ $quote }`\n\nparse-open-tag-name-missing = Invalid DoenetML: Found a tag without a tag name, e.g. `<`\n\nparse-tag-not-closed = Invalid DoenetML: Tag `{ $tag }` was not closed (a `>` appears to be missing).\n\nparse-self-closing-tag-name-missing = Invalid DoenetML: Found a tag without a tag name `<{ $content }>`\n\nparse-self-closing-tag-not-closed = Invalid DoenetML: Tag `{ $tag }` was not closed (`/>` appears to be missing).\n\nparse-tag-invalid-attributes = Invalid DoenetML: Tag `{ $tag }` is not valid. It may have incorrect attributes.\n\nparse-close-tag-name-missing = Invalid DoenetML: Found a closing tag without a tag name, e.g. `</`\n\n# $attribute is the attribute name and $value the unquoted token that followed\n# it, shown reassembled the way the author should have written it.\nparse-attribute-value-unquoted = Attribute values must be enclosed in quotes: `{ $attribute }="{ $value }"`\n\nparse-close-tag-without-open-tag = Invalid DoenetML: Found closing tag `{ $tag }`, but no corresponding opening tag\n\nparse-close-tag-mismatched = Invalid DoenetML: Mismatched closing tag. Expected `</{ $expected }>`. Found `{ $found }`\n\n# The conversion\'s fall-through: the syntax tree held a node shape it has no\n# case for. Reaching an author means the grammar and the conversion have gone\n# out of step, which is a bug in Doenet rather than in their document — hence\n# `parser-` rather than the `parse-` of every message above, which is about\n# what the author wrote. They are still the one looking at it, so it is\n# translated like any other error. $node is the node\'s own name and stays as\n# it is.\nparser-node-unconvertible = Could not convert node { $node } to Dast node.\n\n## Names\n\n# $reason says which rule the name broke, as a key rather than a phrase, so the\n# whole sentence is translatable rather than assembled from two halves.\nname-attribute-invalid =\n    Invalid attribute name=\'{ $name }\'. { $reason ->\n        [characters] Names can contain only letters, numbers, underscores or hyphens.\n       *[start] Names must start with a letter.\n    }\n\ncomponent-name-invalid-start = Invalid component name "{ $name }". Names must start with a letter.\n\n## `<answer>` sugar\n\nanswer-video-watched-missing-video = Answer with type videoWatched must have a video attribute\n\nanswer-video-watched-video-not-reference = Answer with type videoWatched must have video attribute that is a reference\n\nanswer-name-not-single-text = Answer name attribute must have a single text child\n\n## Referencing another document\n\n# $attribute is the attribute the URI was written in (`copyFrom`, `extend`, …)\n# and stays as written; $uri is the author\'s own value.\n\nexternal-doenetml-recursion-limit = Unable to retrieve external DoenetML due to too many levels of recursion. Is there a circular reference?\n\nexternal-doenetml-unavailable = Unable to retrieve DoenetML from { $attribute }="{ $uri }"\n\nexternal-doenetml-type-mismatch = Invalid DoenetML retrieved from { $attribute }="{ $uri }": it did not match the component type "{ $componentType }"\n\n## Deprecated syntax\n\n# $from and $to are attribute names and $component a tag name; all three stay\n# as written. $component is `none` for a rename that applies to every component\n# accepting the attribute, where naming one would be wrong.\n#\n# The `[deprecation]` opening is a literal marker shared by all four messages,\n# not a word: leave it as it is.\n\ndeprecated-attribute-renamed =\n    { $component ->\n        [none] [deprecation] Attribute `{ $from }` is deprecated; use `{ $to }` instead.\n       *[other] [deprecation] Attribute `{ $from }` on `<{ $component }>` is deprecated; use `{ $to }` instead.\n    }\n\ndeprecated-attribute-renamed-conflict =\n    { $component ->\n        [none] [deprecation] Attribute `{ $from }` is deprecated and ignored because `{ $to }` is also specified.\n       *[other] [deprecation] Attribute `{ $from }` on `<{ $component }>` is deprecated and ignored because `{ $to }` is also specified.\n    }\n\ndeprecated-attribute-ignored = [deprecation] Attribute `{ $attribute }` on `<{ $component }>` is deprecated and ignored.\n\n# An attribute replaced by a child element rather than by another attribute:\n# $attribute and $component stay as written, and so does $child, which is the\n# tag name of the child to write instead.\n\ndeprecated-attribute-to-child = [deprecation] Attribute `{ $attribute }` on `<{ $component }>` is deprecated; use a `<{ $child }>` child instead.\n\n# One value of an attribute is deprecated while the attribute itself stays:\n# $value is what the author wrote and $to what to write instead, with\n# $attribute and $component naming where. All four stay as written.\n\ndeprecated-attribute-value-renamed = [deprecation] Value `{ $value }` of attribute `{ $attribute }` on `<{ $component }>` is deprecated; use `{ $to }` instead.\n\n\n## Language coverage\n\n# `<pluralize>` runs an English part-of-speech model over its text and puts the\n# nouns in the plural. There is no equivalent for an arbitrary language — a\n# correct plural needs that language\'s own morphology, and often its\n# dictionary — so in a document written in anything else the word is left as\n# the author typed it, and this says so rather than silently doing nothing.\n#\n# Raised only when there is nothing else to fall back on: a `pluralForm` is the\n# author supplying their own language\'s plural, and that is honored in every\n# language, which is why this can recommend it.\n#\n# $locale is the document\'s language tag, as declared.\npluralize-english-only = `<pluralize>` can only pluralize English, so its text is left unchanged in a document written in { $locale }. Write the plural form directly, or set it with the `pluralForm` attribute.\n\n\n## Checking against the schema\n\n# What the editor draws a squiggle under: the language server\'s own check of\n# the document against the DoenetML schema, run on every keystroke and\n# answered before anything is evaluated. A beginner meets these first, and\n# usually only these, because a document that does not pass them rarely gets\n# as far as producing a diagnostic from the core.\n#\n# `@doenet/lsp-tools` writes its English beside the code rather than rendering\n# it from here, for the same reason `@doenet/parser` does: it is inside the\n# language-server bundle, which `@doenet/codemirror` embeds verbatim and\n# starts as a blob worker, and a catalog on the editor\'s critical path is what\n# `packages/lsp/scripts/check-server-bundle.mjs` exists to reject. The two\n# copies are held together by a test in that package, which runs the checker\n# over a corpus and asserts every coded violation renders to exactly what the\n# checker wrote — so a message edited here without its counterpart fails\n# there.\n#\n# $tag, $parent and $attribute quote the author\'s own source back at them and\n# stay exactly as written; the angle brackets and backticks around them are\n# punctuation this catalog supplies, not part of the name.\n\nschema-element-unrecognized = Element `<{ $tag }>` is not a recognized Doenet element.\n\nschema-element-not-allowed-at-root = Element `<{ $tag }>` is not allowed at the root of the document.\n\nschema-element-not-allowed-inside = Element `<{ $tag }>` is not allowed inside of `<{ $parent }>`.\n\nschema-attribute-unrecognized = Element `<{ $tag }>` doesn\'t have an attribute called `{ $attribute }`.\n\n# $allowed is the attribute\'s permitted values, each already in double quotes\n# and joined for the reader\'s language. $isList says whether the attribute\n# takes several of them at once: one situation, two sentences, because the\n# reader has to be told they are choosing a whole list rather than a value.\nschema-attribute-value-not-allowed =\n    { $isList ->\n        [true] Attribute `{ $attribute }` of element `<{ $tag }>` must be a list whose items are each one of: { $allowed }\n       *[other] Attribute `{ $attribute }` of element `<{ $tag }>` must be one of: { $allowed }\n    }\n\n\n## The `<select>` family\'s error boxes\n##\n## The messages that replace the whole component with a red box rather than\n## warning beside it: nothing can be selected, so there is nothing to render.\n## They were the last uncoded `_error` path in the worker (#1581).\n##\n## Counts arrive as numbers rather than as text, so a language that agrees a\n## noun with them can select on them. English does not agree here — it says\n## "1 options" today and these messages reproduce it exactly, because the box\'s\n## text is what the existing suites pin.\n##\n## Being numbers, they are grouped: a count of 1500 renders as "1,500" in\n## English where the concatenated sentence these replaced wrote "1500". That is\n## the one way the English moved, and it moved in the right direction — these\n## are quantities, not identifiers like a line or a section number, which is\n## the distinction that decides between a number and a string everywhere in\n## these catalogs.\n##\n## Translators: component and attribute names — `selectFromSequence`,\n## `selectPrimeNumbers`, `from`, `to`, `step` — are DoenetML identifiers, not\n## words. They are written into these messages as they stand and must be left\n## in English exactly as written.\n\nselect-variant-name-option-count-mismatch = Invalid variant name for select.  Variant name { $variantName } appears in { $numOptions } options but number to select is { $numToSelect }.\n\nselect-variant-name-without-options = Some variants are specified for select but no options are specified for possible variant name: { $variantName }.\n\nselect-variant-name-not-possible = Variant name { $variantName } that is specified for select is not a possible variant name.\n\nselect-too-few-options = Cannot select { $numToSelect } components from only { $numOptions }.\n\nselect-from-sequence-too-few-values = Cannot select { $numToSelect } values from a sequence of length { $length }.\n\nselect-from-sequence-indices-count-mismatch = Number of indices specified for select must match number to select\n\nselect-from-sequence-indices-not-integers = All indices specified for select must be integers\n\nselect-from-sequence-index-excluded = Specified index of selectfromsequence that was excluded\n\nselect-from-sequence-indices-excluded-combination = Specified indices of selectfromsequence that was an excluded combination\n\nselect-from-sequence-coprime-not-positive-integers = Cannot select coprime combinations as not selecting positive integers.\n\n# Translators: from, to and step are attribute names. They are written into\n# the message rather than passed in because these three never vary — an\n# argument is for a name that changes from one call to the next.\nselect-from-sequence-coprime-common-factor = Cannot select coprime numbers. All possible values share a common factor. (Specified values of "from" or "to" must be coprime with "step".)\n\nselect-from-sequence-coprime-single-number = Cannot select coprime combinations from a single number that is not 1.\n\nselect-from-sequence-excluded-too-many-combinations = Excluded over 70% of combinations in selectFromSequence\n\n# The sibling of `select-from-sequence-coprime-common-factor`, and a different\n# situation rather than a rewording of it: that one is decided up front, from\n# the sequence\'s own arithmetic. This one is what is left after two hundred\n# draws found no coprime combination among values that could have supplied one.\nselect-from-sequence-coprime-none-found = Could not select coprime numbers. All possible values share a common factor.\n\nselect-from-sequence-too-few-unique-values = Cannot select { $numToSelect } unique values from sequence of length { $numPossibleValues }\n\nselect-prime-numbers-too-few-values = Cannot select { $numToSelect } values from a list of primes of length { $numValues }\n\nselect-prime-numbers-values-count-mismatch = Number of values specified for select must match number to select\n\nselect-prime-numbers-values-not-prime = All values specified for select prime number must be in the list of primes\n\nselect-prime-numbers-values-excluded-combination = Specified values of selectPrimeNumbers was an excluded combination\n\nselect-prime-numbers-excluded-too-many-combinations = Excluded over 70% of combinations in selectPrimeNumbers\n\n# Both flukes are shared by `<selectFromSequence>` and `<selectPrimeNumbers>`,\n# which say the same thing in the same words. Neither is reachable in practice\n# — each follows two hundred independent draws — but an unreachable box is\n# still a box, and it renders in whatever language the rest of the page does.\nselect-random-combination-fluke = By extremely unlikely fluke, couldn\'t select combination of random values\n\nselect-random-value-fluke = By extremely unlikely fluke, couldn\'t select random value\n\n## Inputs embedded in math\n\n# Translators: $component is the input\'s own DoenetML tag and stays in English,\n# as do the attribute names `inline`, `expanded` and `width`. An input written\n# inside `<m>` is drawn in the place it is written, inside the typeset\n# expression, which makes room for it as it grows. That needs a control small\n# enough to sit in a line of mathematics, with a width the expression can\n# measure, in an expression that is not drawn on a graph; $reason says which of\n# those this input fails. When it fails, the input is not shown at all, and the\n# expression is typeset with the input\'s value in its place — a text input\'s\n# text, a math input\'s mathematics — or with nothing there for a choice input.\nmath-embedded-input-shape-unsuitable =\n    { $reason ->\n        [not-inline] This `<{ $component }>` is not shown because it is inside math and is not `inline`. Add `inline` so it becomes a drop-down list, which fits inside an expression.\n        [expanded] This `<{ $component }>` is not shown because it is inside math and is `expanded`. Remove `expanded`; a multi-line box does not fit inside an expression.\n        [on-graph] This `<{ $component }>` is not shown because it is inside math drawn on a graph, which has no room for an input.\n       *[relative-width] This `<{ $component }>` is not shown because it is inside math and has a relative width. Give the width in absolute units, such as `px`, instead.\n    }\n\n## `<sampleRandomNumbers>` and `<selectRandomNumbers>`\n##\n## Translators: `mean`, `standardDeviation`, `variance`, `numTotal`,\n## `numSuccesses`, `numDraws`, `numTrials`, `probability` and `numSamples` are\n## DoenetML attribute names. They are written into these messages as they stand\n## and must be left in English exactly as written. Each of these names the\n## attribute the author has to change, so a message that translated one would\n## point at an attribute that does not exist.\n\n# The spread reaches the sampler as a standard deviation however it was written,\n# so a negative `variance` arrives here as a `standardDeviation` of NaN and the\n# message has to name both for the author to know what to edit.\nsample-gaussian-parameters-invalid =\n    Invalid mean ({ $mean }) or standardDeviation ({ $standardDeviation }) for a gaussian random variable. The mean must be a finite number, and the standardDeviation (or the variance it is derived from) must be finite and non-negative. No numbers can be sampled.\n\n# These three attributes are the only ones with no default, so leaving one out is\n# the commonest way to reach this message. Each arrives either as the number the\n# author wrote or as `not-set` for an attribute they left off entirely; translate\n# the "not set" wording, but leave the `not-set` key that selects it untouched.\nsample-hypergeometric-parameters-invalid =\n    Invalid numTotal ({ $numTotal ->\n        [not-set] not set\n       *[other] { $numTotal }\n    }), numSuccesses ({ $numSuccesses ->\n        [not-set] not set\n       *[other] { $numSuccesses }\n    }), or numDraws ({ $numDraws ->\n        [not-set] not set\n       *[other] { $numDraws }\n    }) for a hypergeometric random variable. numTotal must be a positive whole number, and numSuccesses and numDraws must be non-negative whole numbers no larger than numTotal. All three must also stay below about nine quadrillion, past which whole numbers can no longer be counted exactly.\n\n# $maxDraws is the largest number of random draws allowed for a single sample.\nsample-hypergeometric-draws-too-many =\n    Drawing { $numDraws } items from a population of { $numTotal } would need more than { $maxDraws } random draws for each sample, which would stop the page from responding. Reduce numDraws, or bring it closer to numTotal.\n\nsample-binomial-parameters-invalid =\n    Invalid numTrials ({ $numTrials }) or probability ({ $probability }) for a binomial random variable. numTrials must be a non-negative whole number below about nine quadrillion, past which whole numbers can no longer be counted exactly, and probability must be between 0 and 1.\n\n# $maxDraws is the largest number of random draws allowed for a single sample.\nsample-binomial-trials-too-many =\n    Running { $numTrials } trials would need more than { $maxDraws } random draws for each sample, which would stop the page from responding. Reduce numTrials.\n\nsample-poisson-mean-invalid =\n    Invalid mean ({ $mean }) for a poisson random variable. The mean must be a finite, non-negative number.\n\n# $maxDraws is the largest number of random draws allowed for a single sample.\nsample-poisson-mean-too-large =\n    A poisson mean of { $mean } would need more than { $maxDraws } random draws for each sample, which would stop the page from responding. Reduce the mean.\n\n# $distribution names the distribution being sampled, e.g. "binomial" or\n# "multivariate hypergeometric"; $draws is roughly how many random draws each value\n# needs. Raised by `<sampleRandomNumbers>`, `<selectRandomNumbers>` and\n# `<sampleMultivariateRandomNumber>`, which count values with `numSamples`,\n# `numToSelect` and one vector respectively, so the wording names no attribute.\nsample-distribution-slow =\n    Each value from this { $distribution } distribution needs about { $draws } random draws, so sampling may be slow. Reduce the distribution\'s parameters, or ask for fewer values, if the page feels sluggish.\n\n## List index operators\n\n# Raised by the index-returning list operators (`<indexOf>`, `<searchSorted>`)\n# when no `target` was given. $component names the tag the author wrote.\nindex-operator-missing-target =\n    `{ $component }` has no `target` to look for, so it cannot report a position and gives 0.\n\n# Raised when the operator had no values to look through — an empty list, or one\n# whose only children were references that produced nothing.\nindex-operator-no-values =\n    `{ $component }` has no values to look through, so it gives 0, which is not the index of any item.\n## `<sampleMultivariateRandomNumber>`\n##\n## Translators: `type`, `numInCategories` and `numDraws` are DoenetML attribute\n## names, and `hypergeometric` is one of the values `type` takes. They are written\n## into these messages as they stand and must be left in English exactly as\n## written. Each names the attribute the author has to change, so a message that\n## translated one would point at an attribute that does not exist.\n\n# Neither attribute has a default that names a population — numDraws has none at\n# all, and numInCategories falls back to a list with no categories in it — so\n# leaving one out is the commonest way to reach this message. Each arrives either\n# as the value the author wrote or as `not-set`: for numDraws when it is missing,\n# and for numInCategories when it names no categories, whether it was left off or\n# written empty. Translate the "not set" wording, but leave the `not-set` key that\n# selects it untouched.\nsample-multivariate-parameters-invalid =\n    Invalid numInCategories ({ $numInCategories ->\n        [not-set] not set\n       *[other] { $numInCategories }\n    }) or numDraws ({ $numDraws ->\n        [not-set] not set\n       *[other] { $numDraws }\n    }) for a multivariate hypergeometric random variable. numInCategories must list at least one category, each a non-negative whole number, and numDraws must be a non-negative whole number no larger than their total. Each category, that total, and numDraws must also stay below about nine quadrillion, past which whole numbers can no longer be counted exactly.\n\n# $maxDraws is the largest number of random draws allowed for a single sample.\n# Drawing nearly the whole population is as cheap as drawing almost none of it, so\n# raising numDraws is a fix as well as lowering it. "could need" rather than "would\n# need": each category is counted at the most its draw could cost, so the count\n# these parameters are refused on is an upper bound on the work they really take.\nsample-multivariate-draws-too-many =\n    Drawing { $numDraws } items from a population of { $numTotal } split into { $numCategories } categories could need more than { $maxDraws } random draws for each sample, which would stop the page from responding. Reduce numDraws, bring it closer to numTotal, or use fewer categories.\n\n# `type` has no default, so this is what leaving it off gets. A type the attribute\n# does not recognize falls back to no type at all and reaches this message too,\n# after a separate one naming the value that was rejected — hence "no distribution\n# was named" rather than wording that assumes the attribute is missing.\nsample-multivariate-type-not-specified =\n    No multivariate distribution was named for this random variable, so nothing was sampled. Give the type attribute the name of a distribution, such as `type="hypergeometric"`.\n\n## Counting operators\n\n# Raised by `<tally>` when the author named `categories` explicitly and some\n# values matched none of them, so those values were not counted anywhere. Info\n# rather than a warning: a list fed by an input legitimately holds\n# non-categories while a student is typing. It deliberately does not say how\n# many such values there were: the diagnostics queue is append-only and\n# deduplicates by message, so a count would leave one permanent entry behind\n# for every number of stray values the list passed through while being typed.\ntally-values-outside-categories =\n    Some values matched none of the declared categories, so they were not counted.\n\n# Raised by `<tally>` when `categories` names the same category more than once.\n# A warning rather than info: unlike a stray value, a repeated category is a\n# property of what the author wrote, so it stays true of a settled document. The\n# message says what the counts will be, since the behavior is defensible but not\n# what an author who repeated a category by accident expects.\ntally-repeated-category =\n    `categories` names the same category more than once. Each count reports the values equal to its own category, so the repeated ones all report the same number.\n\n# Raised by `<binCounts>` when no `bins` attribute was given, so there are no\n# intervals to count into. $component names the tag the author wrote.\nbin-counts-missing-bins =\n    `{ $component }` has no `bins` cut points, so there are no intervals to count into and it gives no counts.\n\n# Raised by `<binCounts>` when `bins` held fewer than the two cut points needed\n# to define a single interval. $count is how many were given, and can be 0 or 1,\n# so the sentence is worded to read for both without forking on the number.\nbin-counts-too-few-cut-points =\n    `bins` needs at least 2 cut points to define an interval, but received { $count }.\n\n# Raised by `<binCounts>` when its values are not all numeric, so they cannot be\n# placed between numeric cut points. $component names the tag the author wrote.\nbin-counts-values-not-numeric =\n    `{ $component }` can only count numeric values into bins, but not every value it was given is numeric. All counts are 0.\n\n# Raised by `<binCounts>` when the `bins` cut points do not climb: one is\n# smaller than the one before it, so a bin would run backwards and its count\n# would come out negative, or one is not a number at all, which has the same\n# effect. Equal adjacent cut points are accepted, so the message says "at least\n# as large as" rather than "increasing": what is rejected is a decrease, not a\n# failure to strictly increase. Between two interior cut points that names an\n# empty bin; at either end the outermost-edge rule can still put a value in it.\nbin-counts-cut-points-decreasing =\n    Each `bins` cut point must be a number at least as large as the one before it, but one is not a number or is smaller than its predecessor, so no counts were produced.\n\n## Charts\n\n# Raised by `<chart type="bar">` when a value is not a finite number, so it gets\n# no bar. The alternative reading of a missing bar is a value of zero, which the\n# author cannot distinguish by looking, so the absence is stated rather than left\n# to be inferred. No count: the queue is append-only and deduplicates by message,\n# and the number of such values changes as an input is typed into. (The message\n# key is `bar-chart-…` because a code names one situation forever and this one\n# was issued while the component was still spelled `<barChart>`.)\nbar-chart-values-not-drawable =\n    A bar chart draws no bar for a value that is not a finite number, so those places on the chart are empty rather than zero.\n\n# Raised by `<chart type="bar">` when `barWidth` is outside the (0, 1] range a\n# fraction of a bar\'s slot can take. $barWidth is what the author wrote.\nbar-chart-bar-width-invalid =\n    `barWidth` must be greater than 0 and at most 1, but { $barWidth } was given. Using 0.8 instead.\n\n# `type` has no default, so this is what `<chart>` on its own gets. A type the\n# attribute does not recognize falls back to no type at all and reaches this\n# message too, after a separate one naming the value that was rejected — hence\n# "no chart type was named" rather than wording that assumes the attribute is\n# missing.\nchart-type-not-specified =\n    No chart type was named, so nothing was drawn. Give the type attribute the name of a chart, such as `type="bar"`.\n\n# Raised by `<chart>` when values are written beside its `<series>` children.\n# A value outside every series belongs to no group of the data, so there is no\n# place on the chart to draw it; saying so matters because the alternative\n# reading of the missing bar is that the value was zero.\nchart-values-outside-series =\n    A chart with `<series>` children draws only the values inside them, so values written beside a series were not drawn. Move them into a series of their own.\n\n# Raised by `<chart type="line">` and `<chart type="scatter">` when a point\n# cannot be placed. Two situations reach it and the message covers both: a value\n# that is not a finite number, and a value with no `x` beside it — which is what\n# a series given fewer horizontal coordinates than values produces from the\n# position they run out. Neither is distinguishable by looking from having asked\n# for fewer points. No count: the queue deduplicates by message, and the number\n# changes as an input is typed into.\nchart-points-not-drawable =\n    A point needs a finite number for both coordinates, so values with no coordinate beside them, and coordinates with no value, were not drawn.\n';
 const editor = '# Editor and language-server surfaces: the footer, the diagnostics panel, the\n# variant picker, the accessibility button, and the context-help panel beside\n# them. Selected by `uiLocale`.\n#\n# The editor binds to *one* language, and it is the one the viewer below it\n# resolved rather than the one the surrounding host chrome uses: the panel\n# lists diagnostics rendered down there, where an authored `<document lang>` is\n# known, and a footer in one language above a panel in another reads worse than\n# either choice on its own (#1580).\n#\n# The LSP ships bundled with its DoenetML version, so these catalogs are\n# version-correct rather than always-latest.\n#\n# Message ids are lower-kebab-case Fluent identifiers, optionally with a\n# single `.attribute` suffix (`format-document`).\n\n\n## The viewer\'s controls\n##\n## `editor-update-viewer` names the button that recompiles the document. Its\n## word depends on whether the source changed or only the document\'s state\n## did, which is a distinction the code makes and a `$action` says: the button\n## is otherwise identical, and splitting it into two messages would let the two\n## drift.\n##\n## The keyboard hint is a separate branch rather than text appended after the\n## title, because where a shortcut sits in a sentence is not the same in every\n## language. `$shortcut` is a key combination and stays as written.\n##\n## The tooltip takes the word as `$word` rather than referencing the message\n## above it: a message reference resolves only inside its own bundle, so a\n## locale that translated the tooltip but not the word would render the\n## reference literally instead of falling back to English. This is the shape\n## `paginator-page-status` already uses.\n\n# Button label. "Update" recompiles after a source edit; "Reset" reverts\n# only the document\'s live state to match — same button, different verb.\n# Keep both forms short enough to fit a toolbar button.\neditor-update-viewer =\n    { $action ->\n        [reset] Reset\n       *[update] Update\n    }\n\n# Tooltip on the button above. { $word } is that button\'s own current label\n# ("Update" or "Reset"), so this reads as e.g. "Update Viewer" or\n# "Reset Viewer". { $shortcut } appends the keyboard shortcut when one exists.\neditor-update-viewer-title =\n    { $shortcut ->\n        [none] { $word } Viewer\n       *[other] { $word } Viewer { $shortcut }\n    }\n\n\n## The variant picker\n\n# Label for the variant picker control itself (a noun, like a field label).\neditor-variant = Variant\n\n# Placeholder text shown in the empty filter input, before the user types\n# anything — not a button or instruction.\neditor-variant-filter = Filter...\n\n# Button/action label: advances to the next variant in the list.\neditor-variant-next = Select next variant\n\n# Button/action label: goes back to the previous variant in the list.\neditor-variant-previous = Select previous variant\n\n\n## The accessibility status button\n##\n## `WCAG AA` is the name of the standard and is not translated, the way\n## `accessibility-heading-level-1` already leaves it.\n##\n## The tooltip and the label are separate messages rather than one with an\n## extra clause: the label counts the violations and the tooltip does not, and\n## a screen reader and a hover are different audiences.\n##\n## `$action` is whether clicking opens or closes the report — an interpolated\n## English verb before this, which no locale could reach and which no language\n## has to place where English does.\n\neditor-accessibility-title =\n    { $status ->\n        [violations] WCAG AA accessibility violation identified. Click to { $action ->\n            [close] close\n           *[open] open\n        } accessibility report.\n        [advisories] Click to { $action ->\n            [close] close\n           *[open] open\n        } accessibility report. No WCAG AA violations were found, but additional accessibility recommendations are available.\n       *[clean] Click to { $action ->\n            [close] close\n           *[open] open\n        } accessibility report. No accessibility issues were found.\n    }\n\neditor-accessibility-label =\n    { $status ->\n        [violations] WCAG AA accessibility violation identified. { $count ->\n            [one] { $count } WCAG AA violation\n           *[other] { $count } WCAG AA violations\n        } found. Click to { $action ->\n            [close] close\n           *[open] open\n        } accessibility report.\n        [advisories] No WCAG AA violations identified. { $count ->\n            [one] { $count } additional accessibility recommendation\n           *[other] { $count } additional accessibility recommendations\n        } found. Click to { $action ->\n            [close] close\n           *[open] open\n        } accessibility report.\n       *[clean] No WCAG AA violations identified. Click to { $action ->\n            [close] close\n           *[open] open\n        } accessibility report.\n    }\n\n# The word on the button itself, beside the icon, when there are violations.\neditor-accessibility-badge = WCAG\n\n\n## The footer\n##\n## `$version` is a version number and stays as written.\n\neditor-version-title = DoenetML version { $version }\n\neditor-tab-help = Context-sensitive help\n# The word beside the icon on that tab, which has room for one word.\neditor-tab-help-short = Context\neditor-tab-errors = Errors\neditor-tab-warnings = Warnings\neditor-tab-info = Info\neditor-tab-accessibility = Accessibility\neditor-tab-responses = Submitted responses\n\n# A tab\'s accessible name when it carries a count: "Errors: 3".\neditor-tab-with-count = { $label }: { $count }\n\neditor-options = Editor options\neditor-format-as-doenetml = Format as DoenetML\neditor-format-as-xml = Format as XML\n\n\n## The diagnostics panel\n\n# Where in the source a diagnostic was found. `$line` arrives as text, not as a\n# number: it identifies the line, so line 1234 is "#1234" and not "#1,234".\neditor-diagnostic-line = Line #{ $line }\n\neditor-no-errors = No Errors\neditor-no-warnings = No Warnings\neditor-no-info = No Info Diagnostics\n\neditor-show-info-annotations = Show info diagnostics in editor\neditor-show-accessibility-annotations = Show accessibility diagnostics in editor\n\n# Links into the documentation, which has no translated pages yet. The words\n# move; where they point does not (#1580).\neditor-accessibility-learn-more = Learn how Doenet approaches accessibility\n\n# The heading over the WCAG AA failures. The standard\'s name is a link, so it\n# arrives as an argument rather than being written into the sentence — the\n# brackets around it are this catalog\'s punctuation, and the link is the code\'s.\neditor-accessibility-violations-heading = Accessibility violations ({ $standard })\n\neditor-accessibility-other-heading = Other accessibility issues\neditor-none-found = None found\n\n\n## Submitted responses\n\neditor-no-responses = No submitted responses yet\neditor-response-answer-id = Answer Id\neditor-response-response = Response\neditor-response-credit = Credit\neditor-response-submitted = Submitted\n\n\n## The context-help panel\n##\n## The panel beside the diagnostics, which explains whatever the cursor is on.\n## It is the last of the surfaces the header above names.\n##\n## Several of these sentences have marked-up fragments in them — an element\n## name in `<code>`, a link, a rendered piece of inline markdown. Those arrive\n## as arguments and are put back as React nodes after the message is formatted,\n## so a translation owns the whole sentence including where each fragment sits\n## and the punctuation around it. A translation that drops one simply renders\n## without it rather than losing the sentence.\n##\n## Element names, attribute names and `styleNumber` are DoenetML identifiers\n## and stay as written. The descriptions and summaries the panel shows come\n## from the schema, which is generated from the documentation and is not\n## translated, and the values it resolves — a color\'s derived word, a\n## function name, a type — come from the language server in the same state.\n## What is here is the panel\'s own prose around them (#1580).\n\nhelp-placeholder = Place cursor on a tag name, attribute, or { $ref } for documentation.\n\nhelp-unsupported-ref-chain = Help for multi-part references like { $example } is not yet supported.\n\nhelp-unresolved-ref =\n    { $reason ->\n        [notFound] No referent found for reference: { $ref }.\n        [multiple] Multiple referents found for reference: { $ref }.\n       *[indeterminate] A referent for { $ref } could not be determined.\n    }\n\n# Both links end in an arrow, which is direction rather than punctuation and is\n# the same in every language this ships in — but it is inside the message, so a\n# language written right to left can turn it around.\nhelp-learn-about-references = Learn about references →\nhelp-reference-page = Reference page →\n\n# What can go where the cursor is. Two selectors joined: where the cursor sits,\n# and what the schema allows there.\nhelp-suggestions-header =\n    { $location ->\n        [inside] Inside { $element }\n       *[top] At the top level\n    }{ $allowed ->\n        [none] { " — nothing goes here." }\n        [text] { " — type text here." }\n        [text-and-components] { " — type text here, or try:" }\n       *[components] { " — things to try:" }\n    }\n\n# `$shortcut` is a key combination and stays as written. `$total` is a real\n# count, so a language that agrees a noun with it can select on it.\nhelp-suggestions-footer = Press { $shortcut } to see all { $total } components.\n\n# An element\'s name joined to its one-line summary. `$name` is empty where the\n# panel has already printed the name beside this — a suggestion in the list —\n# and only the separator is wanted, so the message has to read as punctuation\n# on its own.\nhelp-name-summary = { $name } — { $summary }\n\n# `$line` is text, not a number: it identifies a line, so line 1234 is "1234"\n# and not "1,234". `none` is how a position that is not known selects a\n# sentence without one rather than substituting an empty parenthesis.\nhelp-ref-is-reference =\n    { $line ->\n        [none] { $ref } is a reference to { $target }.\n       *[other] { $ref } is a reference to { $target } (line { $line }).\n    }\n\nhelp-ref-derived-from =\n    { $line ->\n        [none] Introduced by { $owner } as { $role }.\n       *[other] Introduced by { $owner } on line { $line } as { $role }.\n    }\n\nhelp-property-is-reference =\n    { $line ->\n        [none] { $ref } is a reference to the { $property } property of { $element }.\n       *[other] { $ref } is a reference to the { $property } property of { $element } (line { $line }).\n    }\n\n# The badge on the title row saying what kind of thing the panel is explaining.\nhelp-kind-attribute = attribute\nhelp-kind-snippet = snippet\nhelp-kind-array-entry = array entry\n\nhelp-default = Default:\nhelp-active-default = Active default:\n\n# Appended after the active default\'s value. `styleNumber` is the attribute\'s\n# own name and stays as written; the space and brackets around it do not.\nhelp-style-number-annotation = { " " }(styleNumber { $styleNumber })\n\nhelp-allowed-values =\n    { $perItem ->\n        [true] Allowed values (one per item):\n       *[other] Allowed values:\n    }\n\n# Heading for values the editor offers without requiring: the attribute accepts\n# others too, and nothing warns about them. Distinct from `help-allowed-values`\n# so a translation can pick a word that suggests rather than constrains.\nhelp-suggested-values = Suggested values:\n\nhelp-inserts = Inserts:\n\nhelp-coordinates =\n    { $count ->\n        [one] Coordinate:\n       *[other] Coordinates:\n    }\n\nhelp-type = Type:\n\nhelp-resolved-style = Resolved style (styleNumber { $styleNumber }):\n\nhelp-resolved-function-names = Resolved function names:\nhelp-reset-list = Reset list on this input:\nhelp-added-on-input = Added on this input:\nhelp-removed-on-input = Removed on this input:\n\n# The three names are attributes an author writes, so they stay as written.\nhelp-reset-overrides = { $reset } overrides { $additional } and { $removed }.\n\n# Length syntax for a `componentSize` attribute (`width`, `height`). The values\n# listed alongside this label are examples the panel renders as chips.\nhelp-accepted-sizes = Accepted sizes:\nhelp-size-units = A bare number is pixels. A percentage is a share of the width around the component.\n\n# For a `height`, which is offered no percentage: the note must not raise a form\n# the attribute does not support.\nhelp-size-units-absolute = A bare number is pixels.\n\n# For a width that picks a named `size` preset (`<graph>`, `<image>`, `<video>`):\n# a percentage there is a share of the largest width any component may take, not\n# of the space around this one.\nhelp-size-units-preset = A bare number is pixels, and a percentage is a share of the widest a component can be.\n\n# For a side-by-side `width`, which is offered no absolute form: the same rule,\n# the other way round.\nhelp-size-units-relative = A percentage is a share of the width around the component.\n\n# `size` names a sibling attribute an author writes, so it stays as written.\nhelp-size-snaps-to-preset = This width picks the nearest { $size } preset rather than being used exactly.\n';
 const CATALOG_NAMESPACES = [
   "chrome",
@@ -42891,6 +42891,7 @@ const DIAGNOSTIC_CODES = {
   "doenet-w0145": "invalid-type-ignored",
   "doenet-w0146": "chart-type-not-specified",
   "doenet-w0147": "chart-values-outside-series",
+  "doenet-w0148": "chart-points-not-drawable",
   "doenet-e0001": "pretzel-circuit-first-problem-distractor",
   "doenet-e0002": "component-type-invalid",
   "doenet-e0003": "attribute-repeated",
@@ -47297,7 +47298,7 @@ async function cidFromArrayBuffer(data) {
       await crypto.subtle.digest("SHA-256", new Uint8Array());
       digest = (data2) => crypto.subtle.digest("SHA-256", data2);
     } catch (e22) {
-      const sha256 = (await import("./sha256-DT5xJ2Hv-BafLAx3M-CN2yxnoD.js").then((n2) => n2.s)).default;
+      const sha256 = (await import("./sha256-DT5xJ2Hv-DP6T8brz-DxnN7i0e.js").then((n2) => n2.s)).default;
       digest = (data2) => sha256(data2, {
         asBytes: true
       });
@@ -93440,6 +93441,7 @@ function pointStyleAttributes({
 const CHART_MARGINS_BOTTOM_RIGHT_TOP = [30, 12, 16];
 const AXIS_LABEL_MARGIN_BASE = 14;
 const AXIS_LABEL_MARGIN_PER_CHARACTER = 9;
+const AXIS_LABEL_LINE_HEIGHT = 18;
 function fitMargins(available, near, far, budgetFraction = 1 / 2) {
   const total = near + far;
   const budget = Math.max(Math.floor(available * budgetFraction), 0);
@@ -93466,19 +93468,23 @@ function widestTickLabelLength(firstTick, lastTick, step) {
   }
   return widest;
 }
-function barChartLegendHasItems(geometry) {
+function chartLegendHasItems(geometry) {
   if (geometry === null) {
     return false;
   }
-  const seriesWithABar = new Set(geometry.bars.map((bar) => bar.seriesIndex));
+  const marks = "bars" in geometry ? geometry.bars : geometry.points ?? [];
+  const seriesWithAMark = new Set(marks.map((mark) => mark.seriesIndex));
   return geometry.series.some(
-    (oneSeries, seriesIndex) => seriesWithABar.has(seriesIndex) && labelMarkup({
+    (oneSeries, seriesIndex) => seriesWithAMark.has(seriesIndex) && labelMarkup({
       label: oneSeries.label,
       labelHasLatex: false
     }) !== null
   );
 }
 const TARGET_TICK_INTERVALS = 5;
+function midpoint(low, high) {
+  return low / 2 + high / 2;
+}
 function snapNumber(value) {
   return Number.isFinite(value) ? Number(value.toPrecision(12)) : value;
 }
@@ -93538,6 +93544,55 @@ function nextTickBeyond(value, step, direction) {
   const beyond = rounded === snapNumber(value) ? snapNumber(rounded + direction * step) : rounded;
   return Number.isFinite(beyond) ? beyond : value;
 }
+function autoAxisBounds({
+  low,
+  high,
+  minStep,
+  baseline
+}) {
+  function boundsFor(step) {
+    if (baseline === null) {
+      if (!(high > low)) {
+        const spread = low - step < low && high + step > high ? step : Math.max(
+          step,
+          niceTickStep(Math.abs(low) || 1, minStep)
+        );
+        const lowBound = snapNumber(low - spread);
+        const highBound = snapNumber(high + spread);
+        return [
+          Number.isFinite(lowBound) ? lowBound : low,
+          Number.isFinite(highBound) ? highBound : high
+        ];
+      }
+      return [
+        nextTickBeyond(low, step, -1),
+        nextTickBeyond(high, step, 1)
+      ];
+    }
+    return [
+      low >= baseline ? baseline : nextTickBeyond(low, step, -1),
+      high <= baseline ? snapNumber(baseline + step) : nextTickBeyond(high, step, 1)
+    ];
+  }
+  const [firstMin, firstMax] = boundsFor(
+    niceTickStep(high - low || 1, minStep)
+  );
+  return boundsFor(niceTickStep(firstMax - firstMin, minStep));
+}
+function reconcileBounds(requestedMin, requestedMax, autoMin, autoMax) {
+  const min2 = requestedMin ?? autoMin;
+  const max2 = requestedMax ?? autoMax;
+  if (!Number.isFinite(min2) || !Number.isFinite(max2) || !(min2 < max2)) {
+    return [autoMin, autoMax];
+  }
+  return [min2, max2];
+}
+function tickStepForBounds(min2, max2, wholeValues) {
+  return niceTickStep(
+    max2 - min2,
+    wholeValues && Number.isInteger(min2) && Number.isInteger(max2) ? 1 : 0
+  );
+}
 function computeBarChartGeometry({
   series,
   labels,
@@ -93622,27 +93677,17 @@ function computeBarChartGeometry({
       reachBelow = Math.min(reachBelow, bar.value);
     }
   }
-  function autoBoundsFor(step) {
-    return [
-      reachBelow >= 0 ? 0 : nextTickBeyond(reachBelow, step, -1),
-      reachAbove <= 0 ? step : nextTickBeyond(reachAbove, step, 1)
-    ];
-  }
-  const [firstMin, firstMax] = autoBoundsFor(
-    niceTickStep(reachAbove - reachBelow || 1, minStep)
-  );
-  const [autoYMin, autoYMax] = autoBoundsFor(
-    niceTickStep(firstMax - firstMin, minStep)
-  );
-  let yMin = yMinAttr ?? autoYMin;
-  let yMax = yMaxAttr ?? autoYMax;
-  if (!Number.isFinite(yMin) || !Number.isFinite(yMax) || !(yMin < yMax)) {
-    yMin = autoYMin;
-    yMax = autoYMax;
-  }
-  const tickStep = niceTickStep(
-    yMax - yMin,
-    wholeValues && Number.isInteger(yMin) && Number.isInteger(yMax) ? 1 : 0
+  const [autoYMin, autoYMax] = autoAxisBounds({
+    low: reachBelow,
+    high: reachAbove,
+    minStep,
+    baseline: 0
+  });
+  const [yMin, yMax] = reconcileBounds(
+    yMinAttr,
+    yMaxAttr,
+    autoYMin,
+    autoYMax
   );
   const slots = [];
   for (let ind = 0; ind < numSlots; ind++) {
@@ -93663,7 +93708,128 @@ function computeBarChartGeometry({
     // the first at the default width, and flush against it at
     // `barWidth="1"`.
     bounds: [0, yMin, numSlots + 1, yMax],
-    tickStep,
+    tickStep: tickStepForBounds(yMin, yMax, wholeValues),
+    undrawnValues
+  };
+}
+function computePointChartGeometry({
+  series,
+  labels,
+  xMinAttr,
+  xMaxAttr,
+  yMinAttr,
+  yMaxAttr
+}) {
+  const numericAxis = series.some((oneSeries) => oneSeries.x !== null);
+  const numSlots = series.reduce(
+    (widest, oneSeries) => Math.max(widest, oneSeries.values.length),
+    0
+  );
+  const points = [];
+  let undrawnValues = 0;
+  series.forEach((oneSeries, seriesIndex) => {
+    oneSeries.values.forEach((y2, ind) => {
+      const slot = ind + 1;
+      const x2 = numericAxis ? oneSeries.x?.[ind] ?? NaN : slot;
+      if (!Number.isFinite(x2) || !Number.isFinite(y2)) {
+        undrawnValues++;
+        return;
+      }
+      points.push({
+        seriesIndex,
+        x: x2,
+        y: y2,
+        slot: numericAxis ? null : slot,
+        label: numericAxis ? "" : labels[ind] ?? String(slot)
+      });
+    });
+    if (numericAxis) {
+      undrawnValues += Math.max(
+        0,
+        (oneSeries.x?.length ?? 0) - oneSeries.values.length
+      );
+    }
+  });
+  function wholeAlong(pick2) {
+    return points.every((point2) => Number.isInteger(pick2(point2)));
+  }
+  let low = 0;
+  let high = 0;
+  let first2 = true;
+  for (const point2 of points) {
+    if (first2) {
+      low = point2.y;
+      high = point2.y;
+      first2 = false;
+    } else {
+      low = Math.min(low, point2.y);
+      high = Math.max(high, point2.y);
+    }
+  }
+  const wholeY = wholeAlong((point2) => point2.y);
+  const [autoYMin, autoYMax] = autoAxisBounds({
+    low,
+    high,
+    minStep: wholeY ? 1 : 0,
+    baseline: null
+  });
+  const [yMin, yMax] = reconcileBounds(
+    yMinAttr,
+    yMaxAttr,
+    autoYMin,
+    autoYMax
+  );
+  if (!numericAxis) {
+    return {
+      series: series.map(({ label }) => ({ label })),
+      points,
+      slots: Array.from({ length: numSlots }, (_unused, ind) => ({
+        center: ind + 1,
+        label: labels[ind] ?? String(ind + 1)
+      })),
+      // The same horizontal extent a bar chart of the same categories
+      // gets, so a `<chart type>` switched between them does not move the
+      // data sideways. The vertical pair is the two charts' own: a bar
+      // chart's includes zero and this one's does not.
+      bounds: [0, yMin, numSlots + 1, yMax],
+      tickStep: tickStepForBounds(yMin, yMax, wholeY),
+      xTickStep: null,
+      undrawnValues
+    };
+  }
+  let xLow = 0;
+  let xHigh = 0;
+  let firstX = true;
+  for (const point2 of points) {
+    if (firstX) {
+      xLow = point2.x;
+      xHigh = point2.x;
+      firstX = false;
+    } else {
+      xLow = Math.min(xLow, point2.x);
+      xHigh = Math.max(xHigh, point2.x);
+    }
+  }
+  const wholeX = wholeAlong((point2) => point2.x);
+  const [autoXMin, autoXMax] = autoAxisBounds({
+    low: xLow,
+    high: xHigh,
+    minStep: wholeX ? 1 : 0,
+    baseline: null
+  });
+  const [xMin, xMax] = reconcileBounds(
+    xMinAttr,
+    xMaxAttr,
+    autoXMin,
+    autoXMax
+  );
+  return {
+    series: series.map(({ label }) => ({ label })),
+    points,
+    slots: null,
+    bounds: [xMin, yMin, xMax, yMax],
+    tickStep: tickStepForBounds(yMin, yMax, wholeY),
+    xTickStep: tickStepForBounds(xMin, xMax, wholeX),
     undrawnValues
   };
 }
@@ -93681,13 +93847,13 @@ const LEGEND_PLACEMENTS = {
   lowerright: { corner: "bottomRight", alignment: "nw" },
   lowerleft: { corner: "bottomLeft", alignment: "ne" }
 };
-function estimateLegendSize(labels) {
+function estimateLegendSize(labels, keyWidth) {
   const widest = labels.reduce(
     (widest2, label) => Math.max(widest2, estimateTextWidth(label)),
     0
   );
   return {
-    width: widest + LEGEND_FURNITURE_WIDTH,
+    width: widest + keyWidth,
     height: LEGEND_BOX_PADDING + labels.length * LEGEND_ITEM_HEIGHT
   };
 }
@@ -93715,7 +93881,8 @@ const SEMI_NARROW_CHARACTERS = 'ftr/\\{}"_?–';
 const WIDE_CHARACTERS = "mwMW@%";
 const BROAD_CHARACTERS = "GDUHNOQ&";
 const FULL_WIDTH_FIRST_CODE_POINT = 4352;
-const LEGEND_FURNITURE_WIDTH = 30;
+const LEGEND_SWATCH_KEY_WIDTH = 30;
+const LEGEND_LINE_KEY_WIDTH = 44;
 const LEGEND_ITEM_HEIGHT = 21;
 const LEGEND_BOX_PADDING = 3;
 const LEGEND_OUTSIDE_GAP = 8;
@@ -93723,9 +93890,24 @@ const LEGEND_ANCHOR_OFFSET = 4;
 const LEGEND_MARGIN_BUDGET = 2 / 3;
 const TITLE_SCALE = 1.4;
 const TITLE_MARGIN = 14 * TITLE_SCALE + 10;
-function createBarChartPrefigureXML({
-  geometry,
-  seriesRendering,
+function axisTicks(min2, max2, step) {
+  return {
+    first: tickAtOrBeyond(min2, step, 1),
+    last: tickAtOrBeyond(max2, step, -1),
+    step
+  };
+}
+function axisLabelsAttr({ first: first2, last: last2, step }) {
+  return `(${formatNumber$1(first2)},${formatNumber$1(step)},${formatNumber$1(last2)})`;
+}
+function axisLabelWidth(ticks) {
+  return AXIS_LABEL_MARGIN_PER_CHARACTER * widestTickLabelLength(ticks.first, ticks.last, ticks.step);
+}
+function assembleChartDiagram({
+  bounds,
+  yTicks,
+  xTicks,
+  slots,
   widthPx,
   heightPx,
   xLabel,
@@ -93735,41 +93917,59 @@ function createBarChartPrefigureXML({
   title,
   showLegend,
   legendPosition,
-  displayValues,
+  seriesRendering,
+  seriesLabels,
+  seriesElements,
+  seriesAnnotations,
+  seriesKeyHandles,
+  legendKeyWidth,
+  markOverhang,
+  overlayElements,
   shortDescription,
-  darkMode = false
+  darkMode
 }) {
-  const diagnostics2 = [];
-  const [xMin, yMin, xMax, yMax] = geometry.bounds;
+  const [xMin, yMin, xMax, yMax] = bounds;
   const bbox = `(${formatNumber$1(xMin)},${formatNumber$1(yMin)},${formatNumber$1(xMax)},${formatNumber$1(yMax)})`;
-  const step = geometry.tickStep;
-  const firstTick = tickAtOrBeyond(yMin, step, 1);
-  const lastTick = tickAtOrBeyond(yMax, step, -1);
-  const vlabels = `(${formatNumber$1(firstTick)},${formatNumber$1(step)},${formatNumber$1(lastTick)})`;
-  const [baseBottom, baseRight, baseTop] = CHART_MARGINS_BOTTOM_RIGHT_TOP;
-  const seriesWithABar = new Set(geometry.bars.map((bar) => bar.seriesIndex));
-  const legendLabels = geometry.series.map(
-    ({ label }, seriesIndex) => seriesWithABar.has(seriesIndex) ? label : ""
-  ).filter((label) => label !== "");
+  const [rawBottom, rawRight, rawTop] = CHART_MARGINS_BOTTOM_RIGHT_TOP;
+  const baseBottom = rawBottom + markOverhang;
+  const baseRight = rawRight + markOverhang;
+  const baseTop = rawTop + markOverhang;
+  const legendLabels = seriesLabels.filter(
+    (label, seriesIndex) => label !== "" && seriesKeyHandles[seriesIndex] !== null
+  );
   const legendDrawn = showLegend && legendLabels.length > 0;
   const placement = LEGEND_PLACEMENTS[legendPosition] ?? LEGEND_PLACEMENTS.outsideright;
-  const legendSize = estimateLegendSize(legendLabels);
+  const legendSize = estimateLegendSize(legendLabels, legendKeyWidth);
   const legendOutside = legendDrawn && "side" in placement;
-  let wantedRight = baseRight;
-  let wantedBottom = baseBottom;
+  const xLabelsOnTop = yMax <= 0;
+  const yLabelsOnRight = xMax <= 0;
+  const yLabelBand = AXIS_LABEL_MARGIN_BASE + axisLabelWidth(yTicks);
+  const xLabelBand = baseBottom;
+  const halfWidestXLabel = xTicks ? Math.ceil(axisLabelWidth(xTicks) / 2) : 0;
+  const rightOfPlot = yLabelsOnRight ? yLabelBand : 0;
+  let wantedRight = Math.max(
+    baseRight,
+    halfWidestXLabel,
+    rightOfPlot
+  );
+  let wantedBottom = xLabelsOnTop ? baseTop : xLabelBand;
   const legendOnRight = legendOutside && placement.side === "right";
   const legendOnBottom = legendOutside && placement.side === "bottom";
   if (legendOnRight) {
     wantedRight = Math.max(
-      baseRight,
-      LEGEND_ANCHOR_OFFSET + legendSize.width + LEGEND_OUTSIDE_GAP
+      wantedRight,
+      rightOfPlot + LEGEND_ANCHOR_OFFSET + legendSize.width + LEGEND_OUTSIDE_GAP
     );
   } else if (legendOnBottom) {
-    wantedBottom = baseBottom + LEGEND_ANCHOR_OFFSET + legendSize.height + LEGEND_OUTSIDE_GAP;
+    wantedBottom += LEGEND_ANCHOR_OFFSET + legendSize.height + LEGEND_OUTSIDE_GAP;
   }
   const titleText = labelMarkup({ label: title, labelHasLatex: false });
-  const wantedTop = baseTop + (titleText ? TITLE_MARGIN : 0);
-  const wantedLeft = AXIS_LABEL_MARGIN_BASE + AXIS_LABEL_MARGIN_PER_CHARACTER * widestTickLabelLength(firstTick, lastTick, step);
+  const wantedTop = (xLabelsOnTop ? xLabelBand : baseTop) + (titleText ? TITLE_MARGIN : 0);
+  const wantedLeft = Math.max(
+    yLabelsOnRight ? 0 : yLabelBand,
+    halfWidestXLabel,
+    markOverhang
+  );
   const [marginLeft, marginRight] = fitMargins(
     widthPx,
     wantedLeft,
@@ -93786,6 +93986,12 @@ function createBarChartPrefigureXML({
   const innerHeight = heightPx - marginBottom - marginTop;
   const dimensions = `(${formatNumber$1(innerWidth)},${formatNumber$1(innerHeight)})`;
   const margins = `[${marginLeft},${marginBottom},${marginRight},${marginTop}]`;
+  const finiteScale = (span, pixels) => {
+    const scale = span / (pixels || 1);
+    return Number.isFinite(scale) ? scale : 0;
+  };
+  const unitsPerPixelX = finiteScale(xMax - xMin, innerWidth);
+  const unitsPerPixelY = finiteScale(yMax - yMin, innerHeight);
   const strokeAttr = darkModeAxisStrokeAttr(darkMode);
   const axisLabelElements = [];
   const xLabelText = labelMarkup({
@@ -93794,7 +94000,7 @@ function createBarChartPrefigureXML({
   });
   if (xLabelText) {
     axisLabelElements.push(
-      `<xlabel alignment="nw" ${THEME_AWARE_LABEL_COLOR_ATTR}>${xLabelText}</xlabel>`
+      `<xlabel alignment="${xLabelsOnTop ? "sw" : "nw"}" ${THEME_AWARE_LABEL_COLOR_ATTR}>${xLabelText}</xlabel>`
     );
   }
   const yLabelText = labelMarkup({
@@ -93802,57 +94008,24 @@ function createBarChartPrefigureXML({
     labelHasLatex: yLabelHasLatex
   });
   if (yLabelText) {
+    const secondLine = xLabelsOnTop && yLabelsOnRight && xLabelText ? ` offset="(0,-${AXIS_LABEL_LINE_HEIGHT})"` : "";
     axisLabelElements.push(
-      `<ylabel alignment="se" ${THEME_AWARE_LABEL_COLOR_ATTR}>${yLabelText}</ylabel>`
+      `<ylabel alignment="${yLabelsOnRight ? "sw" : "se"}"${secondLine} ${THEME_AWARE_LABEL_COLOR_ATTR}>${yLabelText}</ylabel>`
     );
   }
   const axesInner = axisLabelElements.join("");
-  const axesAttrs = `axes="all" decorations="no" vlabels="${escapeXml(vlabels)}"${strokeAttr}`;
+  const hlabelsAttr = xTicks ? ` hlabels="${escapeXml(axisLabelsAttr(xTicks))}"` : "";
+  const axesAttrs = `axes="all" decorations="no" vlabels="${escapeXml(axisLabelsAttr(yTicks))}"${hlabelsAttr}${strokeAttr}`;
   const axesElement = axesInner ? `<axes ${axesAttrs}>${axesInner}</axes>` : `<axes ${axesAttrs} />`;
   const elements = [];
-  for (const slot of geometry.slots) {
+  for (const slot of slots ?? []) {
     elements.push(
       `<tick-mark axis="horizontal" location="${formatNumber$1(slot.center)}"${strokeAttr} ${THEME_AWARE_LABEL_COLOR_ATTR}>${escapeXml(slot.label)}</tick-mark>`
     );
   }
-  const groupSeries = geometry.series.length > 1;
-  const seriesStyleAttrs = geometry.series.map(
-    (_unused, seriesIndex) => styleAttributes({
-      selectedStyle: seriesRendering[seriesIndex]?.selectedStyle,
-      diagnostics: diagnostics2,
-      warningPrefix: "<chart>"
-    }).join(" ")
-  );
-  const seriesElements = geometry.series.map(() => []);
-  const seriesAnnotations = geometry.series.map(() => []);
-  const seriesKeyHandles = geometry.series.map(() => null);
-  const valueLabelElements = [];
-  for (const bar of geometry.bars) {
-    const handle = `bar-${bar.seriesIndex + 1}-${bar.slot}`;
-    if (seriesKeyHandles[bar.seriesIndex] === null) {
-      seriesKeyHandles[bar.seriesIndex] = handle;
-    }
-    const barAttrs = seriesStyleAttrs[bar.seriesIndex] ?? "";
-    const lowerLeft = `(${formatNumber$1(bar.lowerLeft[0])},${formatNumber$1(bar.lowerLeft[1])})`;
-    const barDimensions = `(${formatNumber$1(bar.dimensions[0])},${formatNumber$1(bar.dimensions[1])})`;
-    seriesElements[bar.seriesIndex].push(
-      `<rectangle at="${escapeXml(handle)}" lower-left="${escapeXml(lowerLeft)}" dimensions="${escapeXml(barDimensions)}" cliptobbox="yes"${barAttrs ? ` ${barAttrs}` : ""} />`
-    );
-    if (displayValues) {
-      const alignment = bar.value < 0 ? "south" : "north";
-      const barTop = bar.value < 0 ? bar.lowerLeft[1] : bar.lowerLeft[1] + bar.dimensions[1];
-      const anchorX = bar.lowerLeft[0] + bar.dimensions[0] / 2;
-      const anchor = `(${formatNumber$1(snapNumber(anchorX))},${formatNumber$1(snapNumber(barTop))})`;
-      valueLabelElements.push(
-        `<label anchor="${escapeXml(anchor)}" alignment="${alignment}" ${THEME_AWARE_LABEL_COLOR_ATTR}>${escapeXml(formatNumber$1(bar.value) ?? "")}</label>`
-      );
-    }
-    seriesAnnotations[bar.seriesIndex].push(
-      `<annotation ref="${escapeXml(handle)}" text="${escapeXml(`${bar.label}: ${formatNumber$1(bar.value)}`)}" />`
-    );
-  }
+  const groupSeries = seriesLabels.length > 1;
   const annotationElements = [];
-  geometry.series.forEach((oneSeries, seriesIndex) => {
+  seriesLabels.forEach((seriesLabel, seriesIndex) => {
     if (!groupSeries) {
       elements.push(...seriesElements[seriesIndex]);
       annotationElements.push(...seriesAnnotations[seriesIndex]);
@@ -93862,15 +94035,15 @@ function createBarChartPrefigureXML({
     elements.push(
       `<group at="${escapeXml(groupHandle)}">${seriesElements[seriesIndex].join("")}</group>`
     );
-    const seriesName = oneSeries.label || seriesRendering[seriesIndex]?.unlabeledName || `${seriesIndex + 1}`;
+    const seriesName = seriesLabel || seriesRendering[seriesIndex]?.unlabeledName || `${seriesIndex + 1}`;
     annotationElements.push(
       `<annotation ref="${escapeXml(groupHandle)}" text="${escapeXml(seriesName)}">${seriesAnnotations[seriesIndex].join("")}</annotation>`
     );
   });
-  const legendItems = geometry.series.map((oneSeries, seriesIndex) => {
+  const legendItems = seriesLabels.map((seriesLabel, seriesIndex) => {
     const handle = seriesKeyHandles[seriesIndex];
     const text = labelMarkup({
-      label: oneSeries.label,
+      label: seriesLabel,
       labelHasLatex: seriesRendering[seriesIndex]?.labelHasLatex
     });
     if (handle === null || !text) {
@@ -93880,19 +94053,13 @@ function createBarChartPrefigureXML({
   }).filter((item) => item !== null);
   let legendElement = "";
   if (legendDrawn && legendItems.length > 0) {
-    const finiteScale = (span, pixels) => {
-      const scale = span / (pixels || 1);
-      return Number.isFinite(scale) ? scale : 0;
-    };
-    const unitsPerPixelX = finiteScale(xMax - xMin, innerWidth);
-    const unitsPerPixelY = finiteScale(yMax - yMin, innerHeight);
     let anchorX;
     let anchorY;
     if (!("side" in placement)) {
       anchorX = placement.corner.endsWith("Right") ? xMax : xMin;
       anchorY = placement.corner.startsWith("top") ? yMax : yMin;
     } else if (placement.side === "right") {
-      const overhangRight = LEGEND_ANCHOR_OFFSET + legendSize.width + LEGEND_OUTSIDE_GAP;
+      const overhangRight = rightOfPlot + LEGEND_ANCHOR_OFFSET + legendSize.width + LEGEND_OUTSIDE_GAP;
       const overhangBottom = LEGEND_ANCHOR_OFFSET + legendSize.height + LEGEND_OUTSIDE_GAP;
       const pullLeft = Math.min(
         Math.max(overhangRight - marginRight, 0),
@@ -93905,14 +94072,14 @@ function createBarChartPrefigureXML({
         Math.max(overhangBottom - (innerHeight + marginBottom), 0),
         marginTop
       );
-      anchorX = xMax - pullLeft * unitsPerPixelX;
+      anchorX = xMax + (rightOfPlot - pullLeft) * unitsPerPixelX;
       anchorY = yMax + pullUp * unitsPerPixelY;
     } else {
       const belowAxis = Math.max(
         marginBottom - LEGEND_OUTSIDE_GAP - legendSize.height - LEGEND_ANCHOR_OFFSET,
         -(marginTop + innerHeight)
       );
-      anchorX = (xMin + xMax) / 2;
+      anchorX = midpoint(xMin, xMax);
       anchorY = yMin - belowAxis * unitsPerPixelY;
     }
     const anchor = `(${formatNumber$1(anchorX)},${formatNumber$1(anchorY)})`;
@@ -93921,13 +94088,221 @@ function createBarChartPrefigureXML({
   let titleElement = "";
   let captionElement = "";
   if (titleText) {
-    const anchor = `(${formatNumber$1((xMin + xMax) / 2)},${formatNumber$1(yMax)})`;
+    const anchor = `(${formatNumber$1(midpoint(xMin, xMax))},${formatNumber$1(
+      yMax + (xLabelsOnTop ? xLabelBand : 0) * unitsPerPixelY
+    )})`;
     titleElement = `<label anchor="${escapeXml(anchor)}" alignment="north" scale="${TITLE_SCALE}" ${THEME_AWARE_LABEL_COLOR_ATTR}>${titleText}</label>`;
     captionElement = `<caption>${titleText}</caption>`;
   }
   const figureAnnotationText = shortDescription ? ` text="${escapeXml(shortDescription)}"` : "";
   const annotationsElement = `<annotations><annotation ref="figure"${figureAnnotationText}>${annotationElements.join("")}</annotation></annotations>`;
-  const xml = `<diagram dimensions="${escapeXml(dimensions)}" margins="${escapeXml(margins)}"><coordinates bbox="${escapeXml(bbox)}">${axesElement}${elements.join("")}${valueLabelElements.join("")}${titleElement}${legendElement}</coordinates>${captionElement}${annotationsElement}</diagram>`;
+  const xml = `<diagram dimensions="${escapeXml(dimensions)}" margins="${escapeXml(margins)}"><coordinates bbox="${escapeXml(bbox)}">${axesElement}${elements.join("")}${overlayElements.join("")}${titleElement}${legendElement}</coordinates>${captionElement}${annotationsElement}</diagram>`;
+  return xml;
+}
+function createBarChartPrefigureXML({
+  geometry,
+  seriesRendering,
+  widthPx,
+  heightPx,
+  xLabel,
+  xLabelHasLatex,
+  yLabel,
+  yLabelHasLatex,
+  title,
+  showLegend,
+  legendPosition,
+  displayValues,
+  shortDescription,
+  darkMode = false
+}) {
+  const diagnostics2 = [];
+  const [, yMin, , yMax] = geometry.bounds;
+  const seriesStyleAttrs = geometry.series.map(
+    (_unused, seriesIndex) => styleAttributes({
+      selectedStyle: seriesRendering[seriesIndex]?.selectedStyle,
+      diagnostics: diagnostics2,
+      warningPrefix: "<chart>"
+    }).join(" ")
+  );
+  const seriesElements = geometry.series.map(() => []);
+  const seriesAnnotations = geometry.series.map(() => []);
+  const seriesKeyHandles = geometry.series.map(() => null);
+  const valueLabelElements = [];
+  for (const bar of geometry.bars) {
+    const handle = `bar-${bar.seriesIndex + 1}-${bar.slot}`;
+    if (seriesKeyHandles[bar.seriesIndex] === null) {
+      seriesKeyHandles[bar.seriesIndex] = handle;
+    }
+    const barAttrs = seriesStyleAttrs[bar.seriesIndex] ?? "";
+    const lowerLeft = `(${formatNumber$1(bar.lowerLeft[0])},${formatNumber$1(bar.lowerLeft[1])})`;
+    const barDimensions = `(${formatNumber$1(bar.dimensions[0])},${formatNumber$1(bar.dimensions[1])})`;
+    seriesElements[bar.seriesIndex].push(
+      `<rectangle at="${escapeXml(handle)}" lower-left="${escapeXml(lowerLeft)}" dimensions="${escapeXml(barDimensions)}" cliptobbox="yes"${barAttrs ? ` ${barAttrs}` : ""} />`
+    );
+    if (displayValues) {
+      const alignment = bar.value < 0 ? "south" : "north";
+      const barTop = bar.value < 0 ? bar.lowerLeft[1] : bar.lowerLeft[1] + bar.dimensions[1];
+      const anchorX = bar.lowerLeft[0] + bar.dimensions[0] / 2;
+      const anchor = `(${formatNumber$1(snapNumber(anchorX))},${formatNumber$1(snapNumber(barTop))})`;
+      valueLabelElements.push(
+        `<label anchor="${escapeXml(anchor)}" alignment="${alignment}" ${THEME_AWARE_LABEL_COLOR_ATTR}>${escapeXml(formatNumber$1(bar.value) ?? "")}</label>`
+      );
+    }
+    seriesAnnotations[bar.seriesIndex].push(
+      `<annotation ref="${escapeXml(handle)}" text="${escapeXml(`${bar.label}: ${formatNumber$1(bar.value)}`)}" />`
+    );
+  }
+  const xml = assembleChartDiagram({
+    bounds: geometry.bounds,
+    yTicks: axisTicks(yMin, yMax, geometry.tickStep),
+    xTicks: null,
+    slots: geometry.slots,
+    widthPx,
+    heightPx,
+    xLabel,
+    xLabelHasLatex,
+    yLabel,
+    yLabelHasLatex,
+    title,
+    showLegend,
+    legendPosition,
+    seriesRendering,
+    seriesLabels: geometry.series.map(({ label }) => label),
+    seriesElements,
+    seriesAnnotations,
+    seriesKeyHandles,
+    legendKeyWidth: LEGEND_SWATCH_KEY_WIDTH,
+    // A bar is drawn inside the box and clipped to it.
+    markOverhang: 0,
+    overlayElements: valueLabelElements,
+    shortDescription,
+    darkMode
+  });
+  return { xml, diagnostics: diagnostics2 };
+}
+const MARKER_OVERHANG = 7;
+function pointCoordinates(point2) {
+  return `(${formatNumber$1(point2.x)},${formatNumber$1(point2.y)})`;
+}
+function pointInBounds(point2, [xMin, yMin, xMax, yMax]) {
+  return point2.x >= xMin && point2.x <= xMax && point2.y >= yMin && point2.y <= yMax;
+}
+function createPointChartPrefigureXML({
+  geometry,
+  shape,
+  seriesRendering,
+  markers,
+  widthPx,
+  heightPx,
+  xLabel,
+  xLabelHasLatex,
+  yLabel,
+  yLabelHasLatex,
+  title,
+  showLegend,
+  legendPosition,
+  displayValues,
+  shortDescription,
+  darkMode = false
+}) {
+  const diagnostics2 = [];
+  const [xMin, yMin, xMax, yMax] = geometry.bounds;
+  const drawMarkers = shape === "scatter" || markers;
+  const drawLine = shape === "line";
+  const seriesElements = geometry.series.map(() => []);
+  const seriesAnnotations = geometry.series.map(() => []);
+  const seriesKeyHandles = geometry.series.map(() => null);
+  const valueLabelElements = [];
+  const pointsBySeries = geometry.series.map(() => []);
+  for (const point2 of geometry.points) {
+    pointsBySeries[point2.seriesIndex]?.push(point2);
+  }
+  pointsBySeries.forEach((seriesPoints, seriesIndex) => {
+    const selectedStyle = seriesRendering[seriesIndex]?.selectedStyle;
+    if (drawLine && seriesPoints.length > 0) {
+      const lineAttrs = styleAttributes({
+        selectedStyle,
+        diagnostics: diagnostics2,
+        warningPrefix: "<chart>",
+        includeFill: false
+      }).join(" ");
+      const handle = `line-${seriesIndex + 1}`;
+      const coordinates = seriesPoints.map(pointCoordinates).join(",");
+      seriesElements[seriesIndex].push(
+        `<polygon at="${escapeXml(handle)}" points="${escapeXml(`[${coordinates}]`)}" closed="no" cliptobbox="yes"${lineAttrs ? ` ${lineAttrs}` : ""} />`
+      );
+      seriesKeyHandles[seriesIndex] = handle;
+      if (!drawMarkers) {
+        const rendering = seriesRendering[seriesIndex];
+        seriesAnnotations[seriesIndex].push(
+          `<annotation ref="${escapeXml(handle)}" text="${escapeXml(
+            rendering?.label || rendering?.unlabeledName || `${seriesIndex + 1}`
+          )}" />`
+        );
+      }
+    }
+    if (displayValues) {
+      for (const point2 of seriesPoints) {
+        if (!pointInBounds(point2, geometry.bounds)) {
+          continue;
+        }
+        valueLabelElements.push(
+          `<label anchor="${escapeXml(pointCoordinates(point2))}" alignment="north" ${THEME_AWARE_LABEL_COLOR_ATTR}>${escapeXml(formatNumber$1(point2.y) ?? "")}</label>`
+        );
+      }
+    }
+    if (!drawMarkers) {
+      return;
+    }
+    const pointAttrs = pointStyleAttributes({
+      selectedStyle,
+      diagnostics: diagnostics2,
+      warningPrefix: "<chart>"
+    }).join(" ");
+    seriesPoints.forEach((point2, ind) => {
+      if (!pointInBounds(point2, geometry.bounds)) {
+        return;
+      }
+      const handle = `point-${seriesIndex + 1}-${ind + 1}`;
+      if (seriesKeyHandles[seriesIndex] === null) {
+        seriesKeyHandles[seriesIndex] = handle;
+      }
+      seriesElements[seriesIndex].push(
+        `<point at="${escapeXml(handle)}" p="${escapeXml(pointCoordinates(point2))}"${pointAttrs ? ` ${pointAttrs}` : ""} />`
+      );
+      const spoken = point2.label ? `${point2.label}: ${formatNumber$1(point2.y)}` : `${formatNumber$1(point2.x)}, ${formatNumber$1(point2.y)}`;
+      seriesAnnotations[seriesIndex].push(
+        `<annotation ref="${escapeXml(handle)}" text="${escapeXml(spoken)}" />`
+      );
+    });
+  });
+  const xml = assembleChartDiagram({
+    bounds: geometry.bounds,
+    yTicks: axisTicks(yMin, yMax, geometry.tickStep),
+    xTicks: geometry.xTickStep === null ? null : axisTicks(xMin, xMax, geometry.xTickStep),
+    slots: geometry.slots,
+    widthPx,
+    heightPx,
+    xLabel,
+    xLabelHasLatex,
+    yLabel,
+    yLabelHasLatex,
+    title,
+    showLegend,
+    legendPosition,
+    seriesRendering,
+    seriesLabels: geometry.series.map(({ label }) => label),
+    seriesElements,
+    seriesAnnotations,
+    seriesKeyHandles,
+    // A line chart keys its legend off the line, which PreFigure draws as
+    // a segment rather than a swatch, and a segment is wider.
+    legendKeyWidth: drawLine ? LEGEND_LINE_KEY_WIDTH : LEGEND_SWATCH_KEY_WIDTH,
+    markOverhang: drawMarkers ? MARKER_OVERHANG : 0,
+    overlayElements: valueLabelElements,
+    shortDescription,
+    darkMode
+  });
   return { xml, diagnostics: diagnostics2 };
 }
 function returnShortDescriptionStateVariableDefinition({
@@ -93995,6 +94370,7 @@ class Chart extends BlockComponent {
       returnSizeAttributes({ componentName: "chart" })
     );
     attributes.type = {
+      groupName: "marks",
       description: "Which chart to draw. Required; there is no default, and `<chart>` with no type draws nothing.",
       createComponentOfType: "text",
       createStateVariable: "type",
@@ -94006,6 +94382,14 @@ class Chart extends BlockComponent {
         {
           value: "bar",
           description: "A bar chart: one bar per value, standing on a baseline of zero, under a horizontal axis of category names."
+        },
+        {
+          value: "line",
+          description: "A line chart: a path through each series' values in the order given, under category names or against an `x` of their own."
+        },
+        {
+          value: "scatter",
+          description: "A scatter plot: one point per value, against an `x` of its own, or under category names where no series carries one."
         }
       ]
     };
@@ -94016,17 +94400,20 @@ class Chart extends BlockComponent {
       defaultValue: DEFAULT_ASPECT_RATIO
     };
     attributes.categories = {
+      groupName: "axes",
       createComponentOfType: "textList",
-      description: "The label under each bar. Defaults to the bar's position, 1, 2, 3 and so on.",
+      description: "The label under each position on the horizontal axis. Defaults to the position itself, 1, 2, 3 and so on. Not used where a series carries an `x`, which puts the chart on a numeric axis instead.",
       highlighted: true
     };
     attributes.barWidth = {
+      groupName: "marks",
       description: "How much of each category's slot the bars fill: greater than 0 and at most 1, so the bars may fill their slot but must have some width. The rest is the gap to the next category. With several series side by side, they divide this between them.",
       createComponentOfType: "number",
       createStateVariable: "barWidthAttr",
       defaultValue: DEFAULT_BAR_WIDTH
     };
     attributes.layout = {
+      groupName: "marks",
       description: "How the bars of several series share a category's slot.",
       createComponentOfType: "text",
       createStateVariable: "layout",
@@ -94049,13 +94436,15 @@ class Chart extends BlockComponent {
       ]
     };
     attributes.legend = {
-      description: 'Whether to draw a legend naming the series. One is drawn when a series carries a `<label>`; `legend="false"` suppresses it.',
+      groupName: "legend",
+      description: 'Whether to draw a legend naming the series. A legend is drawn when a series carries a `<label>`; `legend="false"` suppresses it.',
       createComponentOfType: "boolean",
       createStateVariable: "legend",
       defaultValue: true,
       public: true
     };
     attributes.legendPosition = {
+      groupName: "legend",
       description: "Where the legend sits.",
       createComponentOfType: "text",
       createStateVariable: "legendPosition",
@@ -94089,25 +94478,56 @@ class Chart extends BlockComponent {
         }
       ]
     };
+    attributes.xMin = {
+      groupName: "axes",
+      description: "Leftmost value shown on the horizontal axis, for a chart with a numeric one. Defaults to the first tick below the smallest `x`. If `xMin` and `xMax` do not describe a box — both finite, with `xMin` below `xMax` — the axis is chosen from the data instead.",
+      createComponentOfType: "number",
+      createStateVariable: "xMinAttr",
+      defaultValue: null
+    };
+    attributes.xMax = {
+      groupName: "axes",
+      description: "Rightmost value shown on the horizontal axis, for a chart with a numeric one. Defaults to the first tick above the largest `x`. If `xMin` and `xMax` do not describe a box — both finite, with `xMin` below `xMax` — the axis is chosen from the data instead.",
+      createComponentOfType: "number",
+      createStateVariable: "xMaxAttr",
+      defaultValue: null
+    };
     attributes.yMin = {
-      description: "Lowest value shown on the vertical axis. Defaults to 0, or to the first tick past the smallest value when some are negative, so that bar does not touch the bottom of the frame. Ignored, along with `yMax`, unless it is a finite number below it.",
+      groupName: "axes",
+      description: "Lowest value shown on the vertical axis. Defaults to 0 for a bar chart, whose bars are measured from it, or to the first tick past the smallest value — which is what a bar chart with negative values gets, and what a line or scatter chart always gets. If `yMin` and `yMax` do not describe a box — both finite, with `yMin` below `yMax` — the axis is chosen from the data instead.",
       createComponentOfType: "number",
       createStateVariable: "yMinAttr",
       defaultValue: null
     };
     attributes.yMax = {
-      description: "Highest value shown on the vertical axis. Defaults to the next tick above the tallest bar. Ignored, along with `yMin`, unless it is a finite number above it.",
+      groupName: "axes",
+      description: "Highest value shown on the vertical axis. Defaults to the next tick above the largest value. If `yMin` and `yMax` do not describe a box — both finite, with `yMin` below `yMax` — the axis is chosen from the data instead.",
       createComponentOfType: "number",
       createStateVariable: "yMaxAttr",
       defaultValue: null
     };
     attributes.displayValues = {
-      description: "Whether to print each bar's value at its far end — above a bar that rises, below one that falls.",
+      groupName: "marks",
+      description: "Whether to print each value beside its mark: at a bar's far end — above one that rises, below one that falls — and above a line or scatter chart's point.",
       createComponentOfType: "boolean",
       createStateVariable: "displayValues",
       defaultValue: false,
       public: true
     };
+    attributes.markers = {
+      groupName: "marks",
+      description: "Whether a line chart draws a marker at each of its points. A scatter plot is its markers, so it always draws them.",
+      createComponentOfType: "boolean",
+      createStateVariable: "markers",
+      defaultValue: true,
+      public: true,
+      // Alongside `layout`, which is the same thing for a bar chart: the
+      // one control over how a type arranges what it draws. Turning
+      // markers off also costs a screen reader the ability to walk the
+      // series point by point, which is not a trade to make from a
+      // collapsed section of the table.
+      highlighted: true
+    };
     attributes.showBorder = {
       description: "Whether to render a border around the chart.",
       createComponentOfType: "boolean",
@@ -94246,6 +94666,7 @@ class Chart extends BlockComponent {
       }
     };
     stateVariableDefinitions.barWidth = {
+      groupName: "marks",
       description: "How much of its slot each bar fills: greater than 0 and at most 1.",
       public: true,
       shadowingInstructions: {
@@ -94321,6 +94742,7 @@ class Chart extends BlockComponent {
             "label",
             "labelHasLatex",
             "values",
+            "x",
             "selectedStyle",
             "hiddenIgnoreParent"
           ]
@@ -94348,6 +94770,12 @@ class Chart extends BlockComponent {
                   values: numericValuesFromValueChildren(
                     valueChildren
                   ),
+                  // Bare values carry no coordinates, so the
+                  // horizontal axis stays categorical — which
+                  // is what makes `<chart type="line">4 9 2`
+                  // draw a line over three categories rather
+                  // than refuse for want of an `x`.
+                  x: null,
                   selectedStyle: dependencyValues.selectedStyle,
                   unlabeledName: contentTranslator(
                     dependencyValues
@@ -94364,6 +94792,10 @@ class Chart extends BlockComponent {
           label: child.stateValues.label,
           labelHasLatex: child.stateValues.labelHasLatex,
           values: child.stateValues.values,
+          // Null on a series that gave none, which is what puts
+          // the chart on a categorical axis rather than a
+          // numeric one.
+          x: child.stateValues.x,
           selectedStyle: child.stateValues.selectedStyle,
           // Built here, where the document's language is known.
           // The drawing has no way to ask, and a bare position
@@ -94385,6 +94817,8 @@ class Chart extends BlockComponent {
       }
     };
     stateVariableDefinitions.numSeries = {
+      groupName: "data",
+      highlighted: true,
       description: "How many series the chart draws.",
       public: true,
       shadowingInstructions: {
@@ -94401,6 +94835,8 @@ class Chart extends BlockComponent {
       })
     };
     stateVariableDefinitions.values = {
+      groupName: "data",
+      highlighted: true,
       description: "Every value charted, series by series.",
       public: true,
       isArray: true,
@@ -94442,6 +94878,7 @@ class Chart extends BlockComponent {
       }
     };
     stateVariableDefinitions.categories = {
+      groupName: "axes",
       description: "The label under each bar, in order.",
       public: true,
       isArray: true,
@@ -94487,6 +94924,7 @@ class Chart extends BlockComponent {
       }
     };
     stateVariableDefinitions.title = {
+      groupName: "marks",
       description: "The chart's title, or the empty string when it has none.",
       public: true,
       shadowingInstructions: {
@@ -94509,6 +94947,7 @@ class Chart extends BlockComponent {
       }
     };
     stateVariableDefinitions.showLegend = {
+      groupName: "legend",
       description: "Whether a legend is drawn.",
       public: true,
       shadowingInstructions: {
@@ -94527,9 +94966,7 @@ class Chart extends BlockComponent {
       definition({ dependencyValues }) {
         return {
           setValue: {
-            showLegend: dependencyValues.legend && barChartLegendHasItems(
-              dependencyValues.chartGeometry
-            )
+            showLegend: dependencyValues.legend && chartLegendHasItems(dependencyValues.chartGeometry)
           }
         };
       }
@@ -94557,6 +94994,14 @@ class Chart extends BlockComponent {
           dependencyType: "stateVariable",
           variableName: "layout"
         },
+        xMinAttr: {
+          dependencyType: "stateVariable",
+          variableName: "xMinAttr"
+        },
+        xMaxAttr: {
+          dependencyType: "stateVariable",
+          variableName: "xMaxAttr"
+        },
         yMinAttr: {
           dependencyType: "stateVariable",
           variableName: "yMinAttr"
@@ -94567,7 +95012,8 @@ class Chart extends BlockComponent {
         }
       }),
       definition({ dependencyValues }) {
-        if (dependencyValues.type !== "bar") {
+        const { type } = dependencyValues;
+        if (type !== "bar" && type !== "line" && type !== "scatter") {
           return {
             setValue: { chartGeometry: null },
             sendDiagnostics: [
@@ -94578,34 +95024,95 @@ class Chart extends BlockComponent {
             ]
           };
         }
-        const geometry = computeBarChartGeometry({
+        if (type === "bar") {
+          const geometry2 = computeBarChartGeometry({
+            series: dependencyValues.seriesData.map(
+              ({ label, values: values2 }) => ({ label, values: values2 })
+            ),
+            labels: dependencyValues.categories,
+            barWidth: dependencyValues.barWidth,
+            layout: dependencyValues.layout,
+            yMinAttr: dependencyValues.yMinAttr,
+            yMaxAttr: dependencyValues.yMaxAttr
+          });
+          return {
+            setValue: { chartGeometry: geometry2 },
+            // A value that is not a finite number gets no bar.
+            // Saying so matters because the alternative reading of
+            // a missing bar is a value of zero, and the author
+            // cannot tell the two apart by looking. The message
+            // carries no count, so the append-only diagnostics
+            // queue holds one of it however often the values
+            // change.
+            sendDiagnostics: geometry2.undrawnValues > 0 ? [
+              codedDiagnostic({
+                type: "warning",
+                code: "doenet-w0144"
+              })
+            ] : []
+          };
+        }
+        const geometry = computePointChartGeometry({
           series: dependencyValues.seriesData.map(
-            ({ label, values: values2 }) => ({ label, values: values2 })
+            ({ label, values: values2, x: x2 }) => ({ label, values: values2, x: x2 })
           ),
           labels: dependencyValues.categories,
-          barWidth: dependencyValues.barWidth,
-          layout: dependencyValues.layout,
+          xMinAttr: dependencyValues.xMinAttr,
+          xMaxAttr: dependencyValues.xMaxAttr,
           yMinAttr: dependencyValues.yMinAttr,
           yMaxAttr: dependencyValues.yMaxAttr
         });
         return {
           setValue: { chartGeometry: geometry },
-          // A value that is not a finite number gets no bar. Saying
-          // so matters because the alternative reading of a missing
-          // bar is a value of zero, and the author cannot tell the
-          // two apart by looking. The message carries no count, so
-          // the append-only diagnostics queue holds one of it however
-          // often the values change.
+          // A point needs both of its coordinates, so this covers a
+          // value that is not a finite number *and* a value whose
+          // `x` ran out — the second of which is what a series given
+          // fewer coordinates than values produces, and is otherwise
+          // indistinguishable from having asked for fewer points.
           sendDiagnostics: geometry.undrawnValues > 0 ? [
             codedDiagnostic({
               type: "warning",
-              code: "doenet-w0144"
+              code: "doenet-w0148"
             })
           ] : []
         };
       }
     };
+    stateVariableDefinitions.xMin = {
+      groupName: "axes",
+      description: "The leftmost value shown on the horizontal axis, or null when it is not a numeric axis.",
+      public: true,
+      shadowingInstructions: {
+        createComponentOfType: "number"
+      },
+      additionalStateVariablesDefined: [
+        {
+          variableName: "xMax",
+          groupName: "axes",
+          description: "The rightmost value shown on the horizontal axis, or null when it is not a numeric axis.",
+          public: true,
+          shadowingInstructions: {
+            createComponentOfType: "number"
+          }
+        }
+      ],
+      returnDependencies: () => ({
+        chartGeometry: {
+          dependencyType: "stateVariable",
+          variableName: "chartGeometry"
+        }
+      }),
+      definition({ dependencyValues }) {
+        const geometry = dependencyValues.chartGeometry;
+        if (!geometry || geometry.slots) {
+          return { setValue: { xMin: null, xMax: null } };
+        }
+        const [xMin, , xMax] = geometry.bounds;
+        return { setValue: { xMin, xMax } };
+      }
+    };
     stateVariableDefinitions.yMin = {
+      groupName: "axes",
       description: "The lowest value shown on the vertical axis, or null when there is no chart to draw.",
       public: true,
       shadowingInstructions: {
@@ -94614,6 +95121,7 @@ class Chart extends BlockComponent {
       additionalStateVariablesDefined: [
         {
           variableName: "yMax",
+          groupName: "axes",
           description: "The highest value shown on the vertical axis, or null when there is no chart to draw.",
           public: true,
           shadowingInstructions: {
@@ -94672,6 +95180,14 @@ class Chart extends BlockComponent {
           dependencyType: "stateVariable",
           variableName: "yLabelHasLatex"
         },
+        type: {
+          dependencyType: "stateVariable",
+          variableName: "type"
+        },
+        markers: {
+          dependencyType: "stateVariable",
+          variableName: "markers"
+        },
         title: {
           dependencyType: "stateVariable",
           variableName: "title"
@@ -94708,7 +95224,7 @@ class Chart extends BlockComponent {
         }
         const darkMode = dependencyValues.document?.stateValues.theme === "dark";
         const widthPx = dependencyValues.width?.size ?? 425;
-        const { xml, diagnostics: diagnostics2 } = createBarChartPrefigureXML({
+        const shared = {
           geometry: dependencyValues.chartGeometry,
           // Resolved here rather than in the geometry, which is
           // renderer-neutral and has no view of the page's theme:
@@ -94742,6 +95258,11 @@ class Chart extends BlockComponent {
           displayValues: dependencyValues.displayValues,
           shortDescription: dependencyValues.shortDescription,
           darkMode
+        };
+        const { xml, diagnostics: diagnostics2 } = dependencyValues.type === "bar" ? createBarChartPrefigureXML(shared) : createPointChartPrefigureXML({
+          ...shared,
+          shape: dependencyValues.type,
+          markers: dependencyValues.markers
         });
         return {
           setValue: { prefigureXML: xml },
@@ -95264,6 +95785,11 @@ class Series extends BaseComponent {
       createStateVariable: "styleNumberAttr",
       defaultValue: null
     };
+    attributes.x = {
+      createComponentOfType: "numberList",
+      description: "The horizontal coordinate of each value, for a chart whose marks are placed by measurement. Without it a series is drawn under `categories`, at 1, 2, 3 and so on.",
+      highlighted: true
+    };
     return attributes;
   }
   // Include children that can be added by the sugar below.
@@ -95337,6 +95863,27 @@ class Series extends BaseComponent {
       stateVariableDefinitions,
       returnSelectedStyleStateVariableDefinition()
     );
+    stateVariableDefinitions.x = {
+      description: "The horizontal coordinate of each value, or null when the series has none.",
+      public: true,
+      shadowingInstructions: {
+        createComponentOfType: "numberList"
+      },
+      returnDependencies: () => ({
+        xAttr: {
+          dependencyType: "attributeComponent",
+          attributeName: "x",
+          variableNames: ["numbers"]
+        }
+      }),
+      definition({ dependencyValues }) {
+        return {
+          setValue: {
+            x: dependencyValues.xAttr?.stateValues.numbers ?? null
+          }
+        };
+      }
+    };
     stateVariableDefinitions.values = {
       description: "The values in this series, in order.",
       public: true,
@@ -135088,7 +135635,7 @@ class LineSegment extends GraphicalComponent {
         desiredStateVariableValues,
         dependencyValues
       }) {
-        let midpoint = [];
+        let midpoint2 = [];
         let dir = [];
         let epoint1 = dependencyValues.endpoints[0];
         let epoint2 = dependencyValues.endpoints[1];
@@ -135104,7 +135651,7 @@ class LineSegment extends GraphicalComponent {
             all_numeric = false;
             break;
           }
-          midpoint.push((v1 + v2) / 2);
+          midpoint2.push((v1 + v2) / 2);
           dir.push(v1 - v2);
         }
         if (!all_numeric) {
@@ -135121,12 +135668,12 @@ class LineSegment extends GraphicalComponent {
         for (let dim = 0; dim < dependencyValues.numDimensions; dim++) {
           desiredEndpoint1.push(
             Context.fromAst(
-              midpoint[dim] + dir[dim] * halfDesiredlength
+              midpoint2[dim] + dir[dim] * halfDesiredlength
             )
           );
           desiredEndpoint2.push(
             Context.fromAst(
-              midpoint[dim] - dir[dim] * halfDesiredlength
+              midpoint2[dim] - dir[dim] * halfDesiredlength
             )
           );
         }
@@ -135450,7 +135997,7 @@ class LineSegment extends GraphicalComponent {
         };
       },
       arrayDefinitionByKey({ globalDependencyValues, arrayKeys }) {
-        let midpoint = {};
+        let midpoint2 = {};
         let ep1 = globalDependencyValues.endpoints[0];
         let ep2 = globalDependencyValues.endpoints[1];
         for (let arrayKey of arrayKeys) {
@@ -135458,16 +136005,16 @@ class LineSegment extends GraphicalComponent {
           let v1 = ep1[dim].evaluate_to_constant();
           let v2 = ep2[dim].evaluate_to_constant();
           if (Number.isFinite(v1) && Number.isFinite(v2)) {
-            midpoint[arrayKey] = Context.fromAst((v1 + v2) / 2);
+            midpoint2[arrayKey] = Context.fromAst((v1 + v2) / 2);
           } else {
-            midpoint[arrayKey] = Context.fromAst([
+            midpoint2[arrayKey] = Context.fromAst([
               "/",
               ["+", ep1[dim].tree, ep2[dim].tree],
               2
             ]);
           }
         }
-        return { setValue: { midpoint } };
+        return { setValue: { midpoint: midpoint2 } };
       },
       inverseArrayDefinitionByKey({
         desiredStateVariableValues,
@@ -139873,7 +140420,7 @@ class RegularPolygon extends Polygon {
             vertex2[0] - vertex1[0],
             vertex2[1] - vertex1[1]
           ];
-          let midpoint = [
+          let midpoint2 = [
             (vertex1[0] + vertex2[0]) / 2,
             (vertex1[1] + vertex2[1]) / 2
           ];
@@ -139886,8 +140433,8 @@ class RegularPolygon extends Polygon {
             sideVector[0] / sideLength
           ];
           center = [
-            midpoint[0] + inradiusDirection[0] * inradius,
-            midpoint[1] + inradiusDirection[1] * inradius
+            midpoint2[0] + inradiusDirection[0] * inradius,
+            midpoint2[1] + inradiusDirection[1] * inradius
           ];
           unconstrainedDirectionWithRadius = [
             vertex1[0] - center[0],
@@ -162693,10 +163240,10 @@ let Graph$1 = class Graph extends BlockComponent {
         dependencyValues
       }) {
         let desiredScale = desiredStateVariableValues[scaleStateVariable];
-        let midpoint = dependencyValues[minDependency] / 2 + dependencyValues[maxDependency] / 2;
-        let desiredMin = midpoint - desiredScale / 2;
-        let desiredMax = midpoint + desiredScale / 2;
-        if (!Number.isFinite(desiredScale) || desiredScale <= 0 || !Number.isFinite(midpoint) || !Number.isFinite(desiredMin) || !Number.isFinite(desiredMax)) {
+        let midpoint2 = dependencyValues[minDependency] / 2 + dependencyValues[maxDependency] / 2;
+        let desiredMin = midpoint2 - desiredScale / 2;
+        let desiredMax = midpoint2 + desiredScale / 2;
+        if (!Number.isFinite(desiredScale) || desiredScale <= 0 || !Number.isFinite(midpoint2) || !Number.isFinite(desiredMin) || !Number.isFinite(desiredMax)) {
           return { success: false };
         }
         return {
@@ -243717,4 +244264,4 @@ export {
   getDefaultExportFromCjs$1 as g,
   updateSyntaxFromV06toV07 as u
 };
-//# sourceMappingURL=index-O78gHXM_.js.map
+//# sourceMappingURL=index-tiXXndOE.js.map