@doenet/v06-to-v07 0.7.21-dev.378 → 0.7.21-dev.380

package/{index-5ZTpiqA9.js → index-wqA0T-Hr.js}

@@ -472,9 +472,9 @@ function join$2(...segments) {
       joined = joined === void 0 ? segments[index2] : joined + "/" + segments[index2];
     }
   }
-  return joined === void 0 ? "." : normalize$1(joined);
+  return joined === void 0 ? "." : normalize$2(joined);
 }
-function normalize$1(path) {
+function normalize$2(path) {
   assertPath$3(path);
   const absolute = path.codePointAt(0) === 47;
   let value = normalizeString$2(path, !absolute);
@@ -8847,9 +8847,9 @@ function join$1(...segments) {
       joined = joined === void 0 ? segments[index2] : joined + "/" + segments[index2];
     }
   }
-  return joined === void 0 ? "." : normalize(joined);
+  return joined === void 0 ? "." : normalize$1(joined);
 }
-function normalize(path) {
+function normalize$1(path) {
   assertPath$1(path);
   const absolute = path.codePointAt(0) === 47;
   let value = normalizeString$1(path, !absolute);
@@ -38388,8 +38388,8 @@ 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 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. `$column` is the\n# authored name of the data column being summarized and is never translated.\n# The table's own headings (`mean`, `stdev`, `quartile1`, …) are the statistic\n# ids an author references, not prose, and stay in place.\nsummary-statistics-caption = Summary statistics of { $column }\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# Banner above a document that compiled with at least one error in it.\ndocument-contains-errors = This document contains errors!\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 = The document viewer could not be started. Please reload the page.\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`). English has no agreement and ignores it; a\n## language that inflects selects on it.\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    .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.\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.\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.\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';
-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# $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## 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\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\nattribute-value-invalid-using-default = Invalid value `{ $value }` for attribute `{ $attribute }`, using value `{ $default }`\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 three 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';
+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`). English has no agreement and ignores it; a\n## language that inflects selects on it.\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    .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.\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.\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.\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## 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';
+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# $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## 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\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\nattribute-value-invalid-using-default = Invalid value `{ $value }` for attribute `{ $attribute }`, using value `{ $default }`\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 three 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\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";
 const editor = "# Editor and language-server surfaces: formatter labels, completion detail\n# text, hover help. Selected by `uiLocale`.\n#\n# Intentionally empty in i18n Phase 0 (#1515). A later phase moves the editor\n# strings into this file; note that the LSP ships bundled with its DoenetML\n# version, so these catalogs are 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";
 const CATALOG_NAMESPACES = [
   "chrome",
@@ -38413,6 +38413,115 @@ const EN_CATALOGS = {
   editor
 };
 const EN_CATALOG_SOURCE = combineCatalogs(EN_CATALOGS);
+function intlLocale(locale) {
+  try {
+    Intl.getCanonicalLocales(locale);
+    return locale;
+  } catch {
+    return DEFAULT_LOCALE;
+  }
+}
+const DECIMAL_LITERAL = /^(-?\d+)(?:\.(\d+))?$/;
+function formatDecimalString(locale, value) {
+  const match2 = DECIMAL_LITERAL.exec(value);
+  if (match2 === null) {
+    return value;
+  }
+  const [, integerPart, fractionPart] = match2;
+  const tag2 = intlLocale(locale);
+  const grouped = groupIntegerPart(tag2, integerPart);
+  if (fractionPart === void 0) {
+    return grouped;
+  }
+  return `${grouped}${decimalSeparator(tag2)}${localizeDigits(tag2, fractionPart)}`;
+}
+function groupIntegerPart(tag2, integerPart) {
+  const negative = integerPart.startsWith("-");
+  const { prefix, suffix, separator, primary, secondary } = numberPattern(
+    tag2,
+    negative
+  );
+  const digits2 = Array.from(
+    localizeDigits(tag2, integerPart.slice(negative ? 1 : 0))
+  );
+  const groups = [];
+  let size2 = primary;
+  let end = digits2.length;
+  while (end > size2) {
+    groups.unshift(digits2.slice(end - size2, end).join(""));
+    end -= size2;
+    size2 = secondary;
+  }
+  groups.unshift(digits2.slice(0, end).join(""));
+  return prefix + groups.join(separator) + suffix;
+}
+const GROUPING_PROBE = "1111111111111111";
+function numberPattern(tag2, negative) {
+  const parts = new Intl.NumberFormat(tag2, {
+    // `true` is `"always"`. The probe is long enough that `"auto"` would
+    // group it too, so this changes nothing here and only states what is
+    // being asked for: where a group boundary falls, not whether some
+    // particular number is given any.
+    //
+    // That second question is answered by {@link groupIntegerPart}, which
+    // groups from a thousand up in every locale — what `<intComma>` has
+    // always done, and not what CLDR would do left alone: Spanish,
+    // Italian, Polish, Hungarian, Bulgarian, Slovenian, Latvian, Estonian
+    // and European Portuguese all suppress the separator in a bare
+    // four-digit number, though German does not.
+    useGrouping: true,
+    maximumFractionDigits: 0
+    // The string overload: `Intl.NumberFormat` reads a decimal string
+    // exactly. TypeScript's `lib.es5` signature predates it, hence the cast.
+  }).formatToParts(
+    (negative ? "-" : "") + GROUPING_PROBE
+  );
+  const groups = [];
+  let prefix = "";
+  let suffix = "";
+  let separator = "";
+  for (const part of parts) {
+    if (part.type === "integer") {
+      groups.push(Array.from(part.value).length);
+      suffix = "";
+    } else if (part.type === "group") {
+      separator = part.value;
+    } else if (groups.length === 0) {
+      prefix += part.value;
+    } else {
+      suffix += part.value;
+    }
+  }
+  const primary = groups[groups.length - 1];
+  return {
+    prefix,
+    suffix,
+    separator,
+    primary,
+    secondary: groups[groups.length - 2] ?? primary
+  };
+}
+function decimalSeparator(tag2) {
+  return new Intl.NumberFormat(tag2).formatToParts(1.1).find((part) => part.type === "decimal")?.value ?? ".";
+}
+function localizeDigits(tag2, digits2) {
+  const format2 = new Intl.NumberFormat(tag2, { useGrouping: false });
+  if (format2.format(0) === "0") {
+    return digits2;
+  }
+  const localDigits = Array.from(
+    { length: 10 },
+    (_2, digit) => format2.format(digit)
+  );
+  return Array.from(digits2, (digit) => localDigits[Number(digit)]).join("");
+}
+const LIST_TYPES = ["conjunction", "disjunction", "unit"];
+function listFormatFor(locale, type) {
+  return new Intl.ListFormat(intlLocale(locale), {
+    style: "long",
+    type: LIST_TYPES.includes(type) ? type : "conjunction"
+  });
+}
 function lookupPattern(bundle, key) {
   const separator = key.indexOf(".");
   const id2 = separator === -1 ? key : key.slice(0, separator);
@@ -38426,16 +38535,8 @@ function lookupPattern(bundle, key) {
   }
   return message.attributes[attribute] ?? null;
 }
-function intlFormattingLocale(locale) {
-  try {
-    Intl.getCanonicalLocales(locale);
-    return locale;
-  } catch {
-    return DEFAULT_LOCALE;
-  }
-}
 function createChainLink(locale, source, useIsolating, onError) {
-  const bundle = new FluentBundle(intlFormattingLocale(locale), {
+  const bundle = new FluentBundle(intlLocale(locale), {
     useIsolating
   });
   const errors = bundle.addResource(new FluentResource(source));
@@ -38748,8 +38849,8 @@ function normalizeLocaleTag(tag2) {
   }
 }
 const esChrome = "# Spanish viewer chrome. Translated from `locales/en/chrome.ftl`, which is the\n# source of truth: `lint:i18n` rejects a key that does not exist there, and\n# reports a key that exists there but not here as missing coverage.\n#\n# Message ids are never translated — only the text to the right of `=`.\n#\n# Register: impersonal throughout — infinitives and bare nouns, never a `tú`\n# or `usted` verb form. The viewer does not know how formally a deployment\n# addresses its readers, and an impersonal label is correct for both.\n\n\n## Answer submission\n\nanswer-checking = Comprobando...\nanswer-submitting = Enviando...\n\nanswer-checking-status = Comprobando la respuesta\nanswer-submitting-status = Enviando la respuesta\n\nanswer-correct = Correcto\nanswer-incorrect = Incorrecto\n\nanswer-response-saved = Respuesta guardada\n\n# Spanish typographic convention puts a space before the percent sign.\nanswer-percent-credit = { $percent } % de crédito\nanswer-percent-correct = { $percent } % correcto\nanswer-percent-short = { $percent } %\n\nmax-credit-available = Crédito máximo disponible: { $percent } %\n\nattempts-remaining =\n    { $count ->\n        [0] no quedan intentos\n        [one] queda { $count } intento\n       *[other] quedan { $count } intentos\n    }\n\nvalidation-correct = (Correcto)\nvalidation-incorrect = (Incorrecto)\nvalidation-partially-correct = (Parcialmente correcto)\n\n# `Mostrar` is the infinitive, per the register note above.\nanswer-show-responses =\n    { $count ->\n        [one] Mostrar { $count } respuesta a { $answerId }\n       *[other] Mostrar { $count } respuestas a { $answerId }\n    }\n\n\n## Disclosure panels\n\nfeedback-heading = Comentarios\n\ncollapsible-click-to-open = (clic para abrir)\ncollapsible-click-to-close = (clic para cerrar)\ncollapsible-initializing = Inicializando...\n\nfootnote-show = Mostrar la nota al pie\nfootnote-hide = Ocultar la nota al pie\n\ndescription-more-information = más información\n\n\n## Controls\n\nslider-previous = Anterior\nslider-next = Siguiente\n\nkeyboard-open = Abrir el teclado\nkeyboard-close = Cerrar el teclado\n\nmatrix-remove-row = Eliminar fila\nmatrix-add-row = Añadir fila\nmatrix-remove-column = Eliminar columna\nmatrix-add-column = Añadir columna\n\nsubset-add-remove-points = Añadir/Eliminar puntos\nsubset-toggle-points-intervals = Alternar puntos e intervalos\nsubset-move-points = Mover puntos\nsubset-clear = Borrar\n\norbital-add-row = Añadir fila\norbital-remove-row = Eliminar fila\norbital-add-box = Añadir casilla\norbital-remove-box = Eliminar casilla\norbital-add-up-arrow = Añadir flecha hacia arriba\norbital-add-down-arrow = Añadir flecha hacia abajo\norbital-remove-arrow = Eliminar flecha\n\norbital-row-label = Etiqueta de la fila { $row }\n\npretzel-answer = Respuesta\n\nsummary-statistics-caption = Resumen estadístico de { $column }\n\n\n## Math input\n\nmath-input-preview-region = vista previa de la expresión matemática\nmath-input-preview = Vista previa\nmath-input-invalid-expression = Expresión no válida:\n\n\n## Document status\n\nviewer-initializing = Inicializando...\n\n\n## Errors\n\nerror-heading = Error\n\ndocument-contains-errors = ¡Este documento contiene errores!\n\nsomething-went-wrong = Algo salió mal.\n\n# Follows `error-heading` and a colon, so it begins in lower case, as in\n# English. The instruction is an infinitive, per the register note above.\nrenderer-load-failed = no se pudo cargar un componente. Recargar la página.\n\ncore-start-failed = No se pudo iniciar el visor del documento. Recargar la página.\n";
-const esContent = "# Spanish content catalog: the prose the core computes into the document.\n# Selected by `documentLocale` — the language the activity was written in.\n#\n# Spanish inflects. Adjectives follow their noun and agree with it in gender,\n# so every adjective below selects on `$gender`, the gender of the noun it\n# describes, and the composition messages put the noun first. Neither is\n# expressible by substituting into the English word order, which is why the\n# catalog controls the order and not the code.\n\n\n## Vocabulario de estilos\n\ncolor =\n    .black =\n        { $gender ->\n            [f] negra\n           *[m] negro\n        }\n    .white =\n        { $gender ->\n            [f] blanca\n           *[m] blanco\n        }\n    .gray = gris\n    .red =\n        { $gender ->\n            [f] roja\n           *[m] rojo\n        }\n    .orange = naranja\n    .yellow =\n        { $gender ->\n            [f] amarilla\n           *[m] amarillo\n        }\n    .green = verde\n    .cyan = cian\n    .blue = azul\n    .purple =\n        { $gender ->\n            [f] morada\n           *[m] morado\n        }\n    .pink = rosa\n    .brown = marrón\n\nline-width =\n    .thick =\n        { $gender ->\n            [f] gruesa\n           *[m] grueso\n        }\n    .thin =\n        { $gender ->\n            [f] delgada\n           *[m] delgado\n        }\n\nline-style =\n    .dashed =\n        { $gender ->\n            [f] discontinua\n           *[m] discontinuo\n        }\n    .dotted =\n        { $gender ->\n            [f] punteada\n           *[m] punteado\n        }\n\n# Sintagmas nominales: van detrás de «con» y no concuerdan con nada.\nfill-style =\n    .horizontal = líneas horizontales\n    .vertical = líneas verticales\n    .diagonal = líneas diagonales\n    .backdiagonal = líneas diagonales inversas\n    .dots = puntos\n    .diamonds = rombos\n\nnoun =\n    .line = línea\n    .line-segment = segmento\n    .ray = semirrecta\n    .vector = vector\n    .curve = curva\n    .function = función\n    .parabola = parábola\n    .polyline = polilínea\n    .polygon = polígono\n    .triangle = triángulo\n    .rectangle = rectángulo\n    .circle = círculo\n    .region = región\n    .point = punto\n    .square = cuadrado\n    .diamond = rombo\n    .cross = cruz\n    .plus = signo más\n\n# El nombre se parte: «polígono regular» lleva los adjetivos y «de 5 lados»\n# cierra el sintagma detrás de ellos. Si el complemento fuera delante, los\n# adjetivos quedarían separados del nombre con el que concuerdan («polígono\n# regular de 5 lados grueso rojo»).\nnoun-regular-polygon =\n    { $part ->\n        [tail] de { $numSides } lados\n       *[head] polígono regular\n    }\n\n# Además de los nombres de arriba, `$noun` puede ser «regular-polygon» (el\n# nombre que compone `noun-regular-polygon`) o el núcleo de un sintagma que no\n# se nombra en la descripción: «border», «fill», «text» y «background». Todos\n# ellos son masculinos en español —polígono, borde, relleno, texto, fondo—, así\n# que caen en el caso por defecto.\nnoun-gender =\n    { $noun ->\n        [line] f\n        [ray] f\n        [curve] f\n        [function] f\n        [parabola] f\n        [polyline] f\n        [region] f\n        [cross] f\n       *[other] m\n    }\n\n\n## Composición de estilos\n\nstyle-stroke =\n    { $parts ->\n        [width-style-color] { $lineStyle } { $width } { $color }\n        [width-color] { $width } { $color }\n        [style-color] { $lineStyle } { $color }\n        [width-style] { $lineStyle } { $width }\n        [width] { $width }\n        [style] { $lineStyle }\n       *[color] { $color }\n    }\n\n# El nombre va delante y los adjetivos detrás: «línea discontinua gruesa roja».\n# El complemento del nombre, si lo hay, cierra el sintagma: «polígono regular\n# grueso rojo de 5 lados».\nstyle-with-noun =\n    { $parts ->\n        [noun-tail] { $noun } { $description } { $nounTail }\n       *[noun] { $noun } { $description }\n    }\n\nstyle-filled-word =\n    { $gender ->\n        [f] rellena\n       *[m] relleno\n    }\n\nstyle-filled =\n    { $parts ->\n        [pattern] { $color } { $filled } con { $pattern }\n       *[plain] { $color } { $filled }\n    }\n\n# Aquí el complemento va pegado al nombre, y no al final como en\n# `style-with-noun`: «relleno de …» se lee como «lleno de …», así que «relleno\n# de 5 lados» diría otra cosa. «Polígono regular de 5 lados azul relleno».\nstyle-filled-with-noun =\n    { $parts ->\n        [pattern] { $noun } { $color } { $filled } con { $pattern }\n        [plain-tail] { $noun } { $nounTail } { $color } { $filled }\n        [pattern-tail] { $noun } { $nounTail } { $color } { $filled } con { $pattern }\n       *[plain] { $noun } { $color } { $filled }\n    }\n\n# «borde» es masculino, así que los adjetivos del borde concuerdan con él y no\n# con la figura que rodea.\nstyle-border-clause =\n    { $parts ->\n        [with-article] con un borde { $border }\n        [and] y borde { $border }\n        [and-article] y un borde { $border }\n       *[with] con borde { $border }\n    }\n\n# «de color» evita tener que concordar el color con un patrón en plural.\nstyle-fill =\n    { $parts ->\n        [pattern] { $pattern } de color { $color }\n       *[plain] { $color }\n    }\n\nstyle-unfilled = sin relleno\n\nstyle-text =\n    { $parts ->\n        [background] { $color } con un fondo { $background }\n       *[plain] { $color }\n    }\n\nstyle-background-none = ninguno\n";
-const esDiagnostics = '# Advertencias y errores mostrados a quien lee o escribe el documento.\n# Seleccionados por `uiLocale`.\n#\n# Los nombres de atributos y componentes de DoenetML (`through`, `endpoint`,\n# `numDimensions`, …) forman parte del lenguaje y se dejan en inglés.\n\n## `<lineSegment>`\n\nline-segment-attributes-ignored-with-endpoints =\n    { $attributesCount ->\n        [one] { $attributes } se ignora cuando se especifican los dos extremos\n       *[other] { $attributes } se ignoran cuando se especifican los dos extremos\n    }\n\nline-segment-attributes-ignored-with-endpoint-and-midpoint =\n    { $attributesCount ->\n        [one] { $attributes } se ignora cuando se especifican un extremo y el punto medio\n       *[other] { $attributes } se ignoran cuando se especifican un extremo y el punto medio\n    }\n\nline-segment-midpoint-offset-without-midpoint = midpointOffset no tiene efecto sin un punto medio\n\n## `<line>`\n\n# «Recta», no «línea», aunque `noun.line` en content.ftl diga «línea»: no es\n# una incoherencia, sino la diferencia entre describir el trazo dibujado («una\n# línea azul gruesa») y hablar del objeto geométrico, que en matemáticas es\n# una recta —de ahí «la ecuación de la recta».\n\nline-points-undetermined-dimensions = La recta pasa por puntos de dimensiones indeterminadas.\n\nline-points-too-few-dimensions = La recta debe pasar por puntos de al menos dos dimensiones.\n\nline-points-depend-on-variables = La recta pasa por puntos que dependen de las variables: { $variables }.\n\n# Enumeradas con coma en vez de «y»: las variables de <line> son `x` e `y` por\n# omisión, y «en las variables x y y» sería a la vez incorrecto (ante el sonido\n# /i/ la conjunción es «e») e ilegible. La coma es correcta sea cual sea el\n# nombre de la variable, que aquí no se conoce de antemano.\nline-equation-invalid-format = Formato no válido para la ecuación de la recta en las variables { $variable1 }, { $variable2 }.\n\n## `<ray>`\n\nray-overprescribed-through = La semirrecta está determinada por through, endpoint y direction. Se ignora el through especificado.\n\nray-dimension-mismatch = Discrepancia de numDimensions en la semirrecta.\n\n## `<vector>`\n\nvector-overprescribed-head = El vector está determinado por head, tail y displacement. Se ignora el head especificado.\n\nvector-dimension-mismatch = Discrepancia de numDimensions en el vector.\n\n## Atraer y restringir\n\nattract-to-without-nearest-point = No se puede atraer a un `<{ $component }>` porque no tiene la variable de estado nearestPoint.\n\nconstrain-to-without-nearest-point = No se puede restringir a un `<{ $component }>` porque no tiene la variable de estado nearestPoint.\n\nconstrain-to-interior-without-nearest-point = No se puede restringir al interior de un `<{ $component }>` porque no tiene la variable de estado nearestPoint.\n\n## `<choiceInput>`\n\nchoice-input-label-position-ignored = labelPosition se ignora en un choiceInput que no es inline\n\n## Ordenar hijos por índice\n\nchoice-input-indices-count-mismatch = Se ignoran los índices especificados para choiceInput porque su cantidad no coincide con la cantidad de hijos choice.\n\npretzel-indices-count-mismatch = Se ignoran los índices especificados para problem porque su cantidad no coincide con la cantidad de hijos problem.\n\nshuffle-indices-count-mismatch = Se ignoran los índices especificados para shuffle porque su cantidad no coincide con la cantidad de componentes.\n\nindices-ignored-out-of-range = Se ignoran los índices especificados para { $component } porque algunos están fuera de rango.\n\npretzel-indices-repeated = Se ignoran los índices especificados para pretzel porque algunos están repetidos.\n\npretzel-circuit-first-index = Se ignoran los índices especificados para pretzel en modo circuit porque el primer índice debe ser 1.\n\n## `<shuffle>` y `<sort>`\n\nstring-children-need-type = Para que `<{ $component }>` funcione con hijos de texto, se debe especificar el atributo `type`.\n\ninvalid-type-defaulting-to-math = Tipo no válido { $type } para el componente { $component }. Debe ser math, text, number o boolean. Se usa math.\n\nstring-not-valid-component-to-arrange = La cadena "{ $value }" no es un componente válido para { $component }. Se ignora.\n\n## Tipos y variables\n\ninvalid-type-defaulting-to-number = Tipo no válido { $type }, se establece el tipo en number.\n\ninvalid-variable-value = Valor no válido de una variable: `{ $value }`\n\n## Variantes\n\nvariant-index-must-be-number = El índice de variante { $index } debe ser un número\n\nvariant-index-must-be-integer = El índice de variante { $index } debe ser un número entero\n\n## `<sideBySide>`\n\nside-by-side-absolute-widths = `<{ $component }>` no está implementado para medidas absolutas. Los anchos se establecen como relativos.\n\nside-by-side-absolute-margins = `<{ $component }>` no está implementado para medidas absolutas. Los márgenes se establecen como relativos.\n\nside-by-side-no-block-child = `<{ $component }>` no es válido: debe tener al menos un hijo de bloque.\n\n## `<label>`\n\nlabel-for-ignored-on-graphical = Se ignora el atributo `for` en un `<label>` gráfico.\n\nlabel-for-must-resolve-to-one = El atributo `for` de `<label>` debe corresponder exactamente a un componente.\n\nlabel-for-unresolved = No se pudo resolver el atributo `for` de `<label>` a un componente.\n\nlabel-for-answer-with-authored-inputs = El atributo `for` de `<label>` hace referencia a un `<answer>` con entradas escritas explícitamente; haz referencia a la entrada directamente.\n\nlabel-for-answer-without-input = El atributo `for` de `<label>` hace referencia a un `<answer>` que no tiene ninguna entrada que etiquetar.\n\nlabel-for-must-reference-input-or-answer = El atributo `for` de `<label>` debe hacer referencia a una entrada o a un `<answer>`.\n\n## Accesibilidad\n\naccessibility-short-description-or-decorative = Por accesibilidad, `<{ $component }>` debe tener una descripción breve o estar marcado como decorativo.\n\naccessibility-video-short-description = Por accesibilidad, `<video>` debe tener una descripción breve.\n\naccessibility-input-short-description-or-label = Por accesibilidad, `<{ $component }>` debe tener una descripción breve o una etiqueta.\n\naccessibility-answer-input-short-description-or-label = Por accesibilidad, la entrada creada por un `<answer>` debe tener una descripción breve o una etiqueta.\n\naccessibility-short-description-contains-math = Las descripciones breves no deben contener componentes matemáticos como `<{ $component }>`. Expresa las matemáticas con palabras.\n\naccessibility-section-title-insufficient-contrast =\n    { $mode ->\n        [dark] { $colorName } no tiene suficiente contraste con el texto del encabezado de sección (modo oscuro) ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; se requiere al menos { $threshold }:1).\n       *[other] { $colorName } no tiene suficiente contraste con el texto del encabezado de sección ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; se requiere al menos { $threshold }:1).\n    }\n\n## `<circle>`\n\ncircle-through-points-non-numerical = No está implementado un `<circle>` que pase por { $count } puntos cuando los puntos no tienen valores numéricos.\n\ncircle-too-many-through-points = No se puede calcular una circunferencia que pase por más de 3 puntos.\n\ncircle-overprescribed-radius-center-points = No se puede calcular una circunferencia con radio, centro y puntos de paso especificados a la vez.\n\ncircle-center-with-multiple-points = No se puede calcular una circunferencia con centro especificado que pase por más de 1 punto.\n\ncircle-radius-too-small = No se puede calcular la circunferencia: dado que la distancia entre los dos puntos es { $distance }, el radio especificado { $radius } es demasiado pequeño.\n\ncircle-radius-with-many-points = No se puede crear una circunferencia que pase por más de dos puntos con un radio especificado.\n\ncircle-invalid-center-or-through-points = El centro o los puntos de paso de la circunferencia no son válidos.\n\ncircle-radius-center-with-multiple-points = No se puede calcular el radio de una circunferencia con centro especificado que pase por más de 1 punto.\n\ncircle-change-radius-non-numerical = No se puede cambiar el radio de una circunferencia con puntos de paso no numéricos\n\ncircle-radius-with-points-non-numerical = No se puede crear una circunferencia que pase por más de un punto con un radio especificado cuando no hay valores numéricos.\n\ncircle-change-center-non-numerical = No está implementado cambiar el centro de una circunferencia que pasa por puntos con valores no numéricos.\n\n## `<function>`\n\nfunction-domain-insufficient-dimensions =\n    { $intervals ->\n        [one] Dimensiones insuficientes para el dominio de la función. El dominio tiene { $intervals } intervalo pero la función tiene { $inputs ->\n            [one] { $inputs } entrada\n           *[other] { $inputs } entradas\n        }.\n       *[other] Dimensiones insuficientes para el dominio de la función. El dominio tiene { $intervals } intervalos pero la función tiene { $inputs ->\n            [one] { $inputs } entrada\n           *[other] { $inputs } entradas\n        }.\n    }\n\nfunction-domain-invalid-format = Formato no válido para el dominio de la función.\n\nfunction-ignoring-non-numerical =\n    { $type ->\n        [maximum] Se ignora el máximo no numérico de la función.\n        [minimum] Se ignora el mínimo no numérico de la función.\n        [extremum] Se ignora el extremo no numérico de la función.\n        [point] Se ignora el punto no numérico de la función.\n        [slope] Se ignora la pendiente no numérica de la función.\n       *[other] Se ignora { $type } no numérico de la función.\n    }\n\nfunction-ignoring-empty =\n    { $type ->\n        [maximum] Se ignora el máximo vacío de la función.\n        [minimum] Se ignora el mínimo vacío de la función.\n        [extremum] Se ignora el extremo vacío de la función.\n        [point] Se ignora el punto vacío de la función.\n       *[other] Se ignora { $type } vacío de la función.\n    }\n\nfunction-points-too-close = La función contiene dos puntos demasiado próximos entre sí. No se puede definir la función.\n\nfunction-iterates-input-output-mismatch =\n    { $inputs ->\n        [one] Las iteraciones de una función solo son posibles si el número de entradas es igual al número de salidas. Esta función tiene { $inputs } entrada y { $outputs ->\n            [one] { $outputs } salida\n           *[other] { $outputs } salidas\n        }.\n       *[other] Las iteraciones de una función solo son posibles si el número de entradas es igual al número de salidas. Esta función tiene { $inputs } entradas y { $outputs ->\n            [one] { $outputs } salida\n           *[other] { $outputs } salidas\n        }.\n    }\n\n## `<sequence>`\n\nsequence-invalid-length = Longitud de la secuencia no válida. Debe ser un entero no negativo.\n\nsequence-invalid-step = Paso de la secuencia no válido. Debe ser un número para una secuencia de tipo { $type }.\n\nsequence-invalid-endpoint-number = El valor de "{ $attribute }" de la secuencia numérica no es válido. Debe ser un número.\n\nsequence-invalid-endpoint-letters = El valor de "{ $attribute }" de la secuencia de letras no es válido. Debe ser una combinación de letras.\n\nsequence-invalid-endpoint = El valor de "{ $attribute }" de la secuencia no es válido.\n\nselect-from-sequence-coprime-not-numbers = Se ignora coprime porque no se están seleccionando números\n\nselect-from-sequence-coprime-with-exclude-combinations = Se ignora coprime porque se especificó excludeCombinations\n\n## Resolución de `target`\n\ntarget-not-found = Destino no válido para `<{ $source }>`: no se encuentra el destino.\n\ntarget-state-variable-not-found = Destino no válido para `<{ $source }>`: no se encuentra una variable de estado llamada "{ $property }" en un `<{ $component }>`.\n\n## `<odeSystem>`\n\node-system-variables-match-independent = Las variables de `<odeSystem>` deben ser distintas de la variable independiente.\n\node-system-duplicate-variable-names = No se pueden definir las funciones del lado derecho de la EDO con nombres de variables dependientes repetidos.\n\node-system-rhs-function-error = No se puede definir la función del lado derecho de la EDO. Error al crear la función de mathjs.\n\n## `<angle>`, `<parabola>` e `<intersection>`\n\nangle-too-many-lines = No se puede definir un ángulo entre { $count } rectas\n\nangle-invalid-through-point = Punto no válido en through de `<angle>`\n\nparabola-vertex-too-many-points = No está implementada una parábola con vértice que pase por más de 1 punto.\n\nparabola-too-many-points = No está implementada una parábola que pase por más de 3 puntos.\n\nintersection-too-many-items = No está implementada la intersección de más de dos objetos\n\n## Otros componentes matemáticos\n\nionic-compound-not-two-ions = No está implementado el compuesto iónico para algo distinto de dos iones.\n\nionic-compound-needs-cation-and-anion = El compuesto iónico solo está implementado para un catión y un anión.\n\nsolve-equations-cannot-evaluate = No se puede resolver la ecuación porque no se pudo evaluar: { $equation }\n\nmath-operators-operand-number-required = Se debe especificar operandNumber al extraer un operando matemático.\n\neigen-decomposition-failed = No se pudieron calcular los valores propios de la matriz\n\n## Renderizador PreFigure\n\nprefigure-x-label-position-unsupported = `<graph>`: xLabelPosition="left" no es compatible con el renderizador prefigure; se usa el comportamiento de posición derecha.\n\nprefigure-y-label-position-unsupported = `<graph>`: yLabelPosition="bottom" no es compatible con el renderizador prefigure; se usa el comportamiento de posición superior.\n\nprefigure-invalid-axis-bounds = `<graph>`: los límites de los ejes no son válidos para la conversión a prefigure; se usa el bbox predeterminado (-10,-10,10,10).\n\nprefigure-invalid-width = `<graph>`: el ancho no es válido para la conversión a prefigure; se usa el ancho de diagrama predeterminado 425.\n\nprefigure-invalid-aspect-ratio = `<graph>`: aspectRatio no es válido para la conversión a prefigure; se usa la relación de aspecto predeterminada 1.\n\nprefigure-annotations-not-rendered = `<graph>`: las anotaciones no se representan si no se usa el renderizador PreFigure.\n\nmultiple-annotations-children = Se encontraron varios hijos `<annotations>` en `<graph>`; se ignoran todos menos el último.\n\n## Referencias a otros componentes\n\ncopy-unrecognized-component-type = No se puede extender ni copiar un tipo de componente desconocido: { $type }.\n\ncopy-prop-not-found = No se encontró la propiedad { $property } en un componente de tipo { $component }\n\ncollect-no-source = No se encontró ninguna fuente para collect.\n\ncollect-invalid-component-type = No se pueden recolectar componentes de tipo `<{ $component }>` porque no es un tipo de componente válido.\n\nreference-index-unavailable = No se puede referenciar el índice `{ $reference }`\n\n## `<callAction>`\n\ncomponent-action-unavailable = No se puede llamar a { $action } en el componente `{ $reference }`\n\n## `<dataFrame>`\n\ndata-frame-inconsistent-row-lengths = Los datos tienen una forma no válida.  Las filas tienen longitudes distintas. Encontrado en componentIdx :{ $componentIdx }\n\ndata-frame-duplicate-column-names = Los datos tienen nombres de columna repetidos.  Encontrado en componentIdx :{ $componentIdx }\n\ndata-frame-missing-column-name = A los datos les falta el nombre de una columna.  Encontrado en componentIdx :{ $componentIdx }\n\n## `<answer>` y puntuación\n\nanswer-award-depends-on-own-response = Un award de esta respuesta depende de la respuesta enviada por el propio answer, lo que provocará un comportamiento inesperado.\n\nanswer-max-num-attempts-in-section-wide-check-work = Establecer `maxNumAttempts` en un `<answer>` dentro de un contenedor con `sectionWideCheckWork` no tiene efecto, porque el número de intentos lo controla el contenedor. Establece `maxNumAttempts` en el contenedor.\n\nnested-section-wide-check-work-max-num-attempts = Establecer `maxNumAttempts` en un contenedor con `sectionWideCheckWork` que está dentro de otro contenedor con `sectionWideCheckWork` no tiene efecto, porque el número de intentos lo controla el contenedor exterior. Establece `maxNumAttempts` en el contenedor exterior.\n\nanswer-attributes-need-symbolic-equality =\n    { $attributesCount ->\n        [one] El atributo { $attributes } no tendrá efecto si no se establece symbolicEquality.\n       *[other] Los atributos { $attributes } no tendrán efecto si no se establece symbolicEquality.\n    }\n\nanswer-invalid-type = Tipo no válido para answer: { $type }\n\n## `<module>`, `<conditionalContent>`, `<slider>` y pretzel\n\nmodule-attribute-child-needs-name = Como el componente `<{ $component }>` no tiene nombre, no se puede usar como atributo de módulo\n\nmodule-attribute-name-already-defined = El componente `<{ $component } name="{ $name }">` no se puede usar como atributo de un módulo porque el tipo de componente `<module>` ya tiene definido un atributo "{ $name }".\n\nconditional-content-condition-ignored = Se ignora el atributo `condition` en un `<conditionalContent>` que tiene hijos case o else.\n\nslider-markers-type-mismatch = El tipo de los marcadores no coincide con el tipo del slider.\n\npretzel-problem-needs-statement-and-answer = Pretzel no válido: cada `<problem>` debe contener un `<statement>` y un `<answer>`.\n\npretzel-circuit-first-problem-distractor = Pretzel no válido: en mode="circuit", el primer `<problem>` no puede ser un distractor.\n\n## Valores de atributos\n\nattribute-invalid-values =\n    { $valuesCount ->\n        [one] Valor no válido { $values } para el atributo `{ $attribute }`; se ignora.\n       *[other] Valores no válidos { $values } para el atributo `{ $attribute }`; se ignoran.\n    }\n\nattribute-must-be-references = Valor no válido `{ $value }` para el atributo `{ $attribute }`. El atributo debe estar compuesto de referencias que empiecen por `$`.\n\nmath-input-invalid-function-names = <mathInput>: se ignoran nombres de función no válidos en { $attribute }: { $names }. El segmento visible de cada nombre debe tener al menos 2 caracteres (letras o guiones); puede añadirse un sufijo opcional `|<alternativa de mathspeak>`.\n\n## Construcción de componentes a partir del código fuente\n\ncomponent-type-invalid = Tipo de componente no válido: `<{ $componentType }>`\n\nattribute-repeated = No se puede repetir el atributo { $attribute }.\n\nattribute-invalid-for-component = Atributo "{ $attribute }" no válido para un componente de tipo `<{ $componentType }>`.\n\n## Contraste de las definiciones de estilo\n\nstyle-definition-insufficient-contrast =\n    La definición de estilo { $styleNumber } no tiene suficiente contraste para { $context ->\n        [text-on-background] el color del texto sobre el color de fondo\n        [high-contrast] el color de alto contraste sobre el lienzo\n        [line] el color de las líneas sobre el lienzo\n        [marker] el color de los marcadores sobre el lienzo\n       *[text-on-canvas] el color del texto sobre el lienzo\n    }{ $mode ->\n        [dark] { " (modo oscuro)" }\n       *[light] { "" }\n    } ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; se requiere al menos { $threshold }:1).\n\nstyle-definition-dark-mode-text-background-contrast =\n    Aunque la definición de estilo { $styleNumber } especifica colores con suficiente contraste en modo claro, los colores de modo oscuro derivados de esos valores no tienen suficiente contraste entre el color del texto y el color de fondo ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; se requiere al menos { $threshold }:1). { $suggestion ->\n        [available] Para lograr suficiente contraste en modo oscuro, aumenta el contraste en modo claro (por ejemplo, con { $lightAttribute }="{ $lightColor }") o define el color de modo oscuro (por ejemplo, con { $darkAttribute }="{ $darkColor }").\n       *[none] Para lograr suficiente contraste en modo oscuro, aumenta el contraste en modo claro o sustituye los colores derivados mediante textColorDarkMode o backgroundColorDarkMode.\n    }\n\nstyle-definition-dark-mode-text-canvas-contrast =\n    Aunque la definición de estilo { $styleNumber } especifica un color de texto con suficiente contraste en modo claro, el color de texto de modo oscuro derivado de ese valor no tiene suficiente contraste sobre el lienzo ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; se requiere al menos { $threshold }:1). { $suggestion ->\n        [available] Para lograr suficiente contraste en modo oscuro, aumenta el contraste en modo claro (por ejemplo, con textColor="{ $lightColor }") o define el color de modo oscuro (por ejemplo, con textColorDarkMode="{ $darkColor }").\n       *[none] Para lograr suficiente contraste en modo oscuro, aumenta el contraste en modo claro o sustituye el color derivado mediante textColorDarkMode.\n    }\n\nsection-multiple-style-palettes = Una sección solo puede seleccionar un <stylePalette>; se usará el último.\n\n## Variantes únicas\n\nvariant-num-to-select-not-non-negative-integer = no se pueden determinar las variantes únicas de { $component } porque numToSelect no es un entero no negativo.\n\nvariant-num-to-select-not-constant-number = no se pueden determinar las variantes únicas de { $component } porque numToSelect no es un número constante.\n\nvariant-with-replacement-not-constant-boolean = no se pueden determinar las variantes únicas de { $component } porque withReplacement no es un booleano constante.\n\nvariant-select-weight-disables-unique = Las variantes únicas quedan desactivadas en select si alguna opción especifica selectWeight o selectForVariants\n\nvariant-coprime-undetermined = no se pueden determinar las variantes únicas de { $component } porque no se puede determinar si coprime es siempre falso.\n\nvariant-attribute-not-constant = no se pueden determinar las variantes únicas de { $component } porque { $attribute } no es constante.\n\nvariant-attribute-not-number = no se pueden determinar las variantes únicas de { $component } porque { $attribute } no es un número.\n\nvariant-attribute-wrong-type-for-sequence =\n    no se pueden determinar las variantes únicas de { $component } de tipo { $type } porque { $attribute } no es { $expected ->\n        [letters-combination] una combinación de letras\n        [math-expression] una expresión matemática válida\n        [integer] un entero\n       *[number] un número\n    }.\n\nvariant-length-not-integer = no se pueden determinar las variantes únicas de { $component } porque length no es un entero.\n\nvariant-sort-not-implemented = no se han implementado las variantes únicas de un { $component } con sort\n\nvariant-exclude-combinations-not-implemented = no se han implementado las variantes únicas de un { $component } con excludeCombinations\n\nvariant-math-exclude-not-implemented = no se han implementado las variantes únicas de un { $component } de tipo math con exclude\n\nvariant-non-constant-exclude-not-implemented = no se han implementado las variantes únicas de un { $component } con exclude no constante\n\n## Conversión a PreFigure\n\nprefigure-descendant-unsupported = { $subject }: no se admite en el renderizador prefigure de gráficos; se omite el descendiente.\n\nprefigure-descendant-invalid-geometry = { $subject }: geometría no finita o incompleta; se omite el descendiente.\n\nprefigure-curve-label-omitted = { $subject }: las etiquetas no se admiten en los elementos de curva convertidos; se omite la etiqueta.\n\nprefigure-curve-unsupported-definition-type = { $subject }: tipo de definición de función de curva no admitido \'{ $definitionType }\'; se omite el descendiente.\n\nprefigure-region-flip-functions-unsupported = { $subject }: atributo flipFunctions no admitido en regionBetweenCurves; se omite el descendiente.\n\nprefigure-region-non-formula-child = { $subject }: en regionBetweenCurves solo se admiten funciones hijas de tipo fórmula; se omite el descendiente.\n\nprefigure-label-position-unsupported =\n    { $subject }: labelPosition \'{ $labelPosition }\' no admitido para { $labelKind ->\n        [line-family] una etiqueta de la familia de líneas\n       *[point] una etiqueta de punto\n    }; se usa la alineación predeterminada de PreFigure.\n\nprefigure-fill-style-unsupported = { $subject }: PreFigure no admite el estilo de relleno \'{ $fillStyle }\'; se usa un relleno sólido.\n\nprefigure-line-style-unknown = { $subject }: estilo de línea desconocido \'{ $lineStyle }\'; se omite de la salida de PreFigure.\n\nprefigure-marker-style-mapped-to-diamond = { $subject }: el estilo de marcador \'{ $markerStyle }\' se asigna al estilo \'diamond\' de PreFigure.\n\nprefigure-marker-style-unsupported = { $subject }: PreFigure no admite el estilo de marcador \'{ $markerStyle }\'; se usa el estilo predeterminado.\n\n## Anotaciones de PreFigure\n\nannotation-ref-unresolvable = `<annotation>`: `ref` no válido; no se puede resolver el destino. Se omite la anotación.\n\nannotation-ref-multiple-targets = `<annotation>`: `ref` se resolvió a varios destinos; se usa el primero.\n\nannotation-ref-outside-graph = `<annotation>`: `ref` no válido; el destino está fuera del gráfico que lo contiene. Se omite la anotación.\n\nannotation-ref-unsupported-target = `<annotation>`: `ref` no válido; el destino no es un objeto gráfico admitido en la conversión a prefigure. Se omite la anotación.\n\nannotation-text-missing = `<annotation>`: falta `text` o está vacío; se emite texto vacío.\n\n## Composites y referencias\n\ncomposite-circular-dependency =\n    { $componentType ->\n        [none] Se detectó una dependencia circular.\n       *[other] Se detectó una dependencia circular en la que participa un componente `<{ $componentType }>`.\n    }\n\nreference-no-referent = No se encontró ningún referente para la referencia: `{ $reference }`\n\nreference-multiple-referents = Se encontraron varios referentes para la referencia: `{ $reference }`\n\n## Hijos que no coinciden\n\nchildren-invalid-attribute-format = Formato no válido para el atributo { $attribute } de `<{ $componentType }>`.\n\nchildren-invalid = Hijos no válidos para `<{ $componentType }>`: se encontraron hijos no válidos: { $children }\n\n## Se recurre a un valor predeterminado\n\nattribute-value-invalid-using-default = Valor no válido `{ $value }` para el atributo `{ $attribute }`; se usa el valor `{ $default }`\n\n## Carga de una versión de DoenetML\n\ndoenetml-version-not-found =\n    { $fallback ->\n        [none] No se encontró la versión { $version } de DoenetML.\n       *[other] No se encontró la versión { $version } de DoenetML. Se recurrirá a la versión { $fallback }\n    }\n\n## Lectura del DoenetML\n\n# Estos mensajes citan el propio texto del autor —`$tag`, `$value`,\n# `$attribute`…—, que se reproduce tal cual.\n\nparse-invalid-doenetml = DoenetML no válido: { $content }\n\nparse-tag-missing-close-tag = DoenetML no válido: la etiqueta `{ $tag }` no tiene etiqueta de cierre. Se esperaba una etiqueta autocerrada o una etiqueta `</{ $tagName }>`.\n\nparse-tag-error = DoenetML no válido: error en la etiqueta `<{ $tagName }>`\n\nparse-attribute-missing-value = DoenetML no válido: parece que al atributo `{ $attribute }` le falta un valor.\n\nparse-attribute-invalid = DoenetML no válido: atributo no válido `{ $attribute }`\n\nparse-attribute-value-invalid = DoenetML no válido: valor de atributo no válido `{ $value }`\n\n# $quote es la comilla que cerraría el par: `"` o `\'`.\nparse-attribute-value-quote-mismatch = DoenetML no válido: valor de atributo no válido `{ $value }`. Las comillas no coinciden. Parece que falta una `{ $quote }`\n\nparse-open-tag-name-missing = DoenetML no válido: se encontró una etiqueta sin nombre, por ejemplo `<`\n\nparse-tag-not-closed = DoenetML no válido: la etiqueta `{ $tag }` no se cerró (parece que falta un `>`).\n\nparse-self-closing-tag-name-missing = DoenetML no válido: se encontró una etiqueta sin nombre `<{ $content }>`\n\nparse-self-closing-tag-not-closed = DoenetML no válido: la etiqueta `{ $tag }` no se cerró (parece que falta `/>`).\n\nparse-tag-invalid-attributes = DoenetML no válido: la etiqueta `{ $tag }` no es válida. Puede que tenga atributos incorrectos.\n\nparse-close-tag-name-missing = DoenetML no válido: se encontró una etiqueta de cierre sin nombre, por ejemplo `</`\n\nparse-attribute-value-unquoted = Los valores de los atributos deben ir entre comillas: `{ $attribute }="{ $value }"`\n\nparse-close-tag-without-open-tag = DoenetML no válido: se encontró la etiqueta de cierre `{ $tag }`, pero no hay ninguna etiqueta de apertura que le corresponda\n\nparse-close-tag-mismatched = DoenetML no válido: la etiqueta de cierre no coincide. Se esperaba `</{ $expected }>`. Se encontró `{ $found }`\n\nparser-node-unconvertible = No se pudo convertir el nodo { $node } en un nodo Dast.\n\n## Nombres\n\nname-attribute-invalid =\n    Atributo name=\'{ $name }\' no válido. { $reason ->\n        [characters] Los nombres solo pueden contener letras, números, guiones bajos o guiones.\n       *[start] Los nombres deben empezar por una letra.\n    }\n\ncomponent-name-invalid-start = Nombre de componente "{ $name }" no válido. Los nombres deben empezar por una letra.\n\n## Azúcar sintáctico de `<answer>`\n\nanswer-video-watched-missing-video = Un `<answer>` de tipo videoWatched debe tener un atributo video\n\nanswer-video-watched-video-not-reference = Un `<answer>` de tipo videoWatched debe tener un atributo video que sea una referencia\n\nanswer-name-not-single-text = El atributo name de `<answer>` debe tener un único hijo de texto\n\n## Referencias a otro documento\n\nexternal-doenetml-recursion-limit = No se pudo obtener el DoenetML externo por exceso de niveles de recursión. ¿Hay alguna referencia circular?\n\nexternal-doenetml-unavailable = No se pudo obtener el DoenetML de { $attribute }="{ $uri }"\n\nexternal-doenetml-type-mismatch = El DoenetML obtenido de { $attribute }="{ $uri }" no es válido: no coincide con el tipo de componente "{ $componentType }"\n\n## Sintaxis obsoleta\n\n# `[deprecation]` es una marca literal que abre los tres mensajes; se deja\n# igual. $component es `none` cuando el cambio de nombre vale para todos los\n# componentes que aceptan el atributo y nombrar uno sería engañoso.\n\ndeprecated-attribute-renamed =\n    { $component ->\n        [none] [deprecation] El atributo `{ $from }` está obsoleto; usa `{ $to }` en su lugar.\n       *[other] [deprecation] El atributo `{ $from }` de `<{ $component }>` está obsoleto; usa `{ $to }` en su lugar.\n    }\n\ndeprecated-attribute-renamed-conflict =\n    { $component ->\n        [none] [deprecation] El atributo `{ $from }` está obsoleto y se ignora porque también se especificó `{ $to }`.\n       *[other] [deprecation] El atributo `{ $from }` de `<{ $component }>` está obsoleto y se ignora porque también se especificó `{ $to }`.\n    }\n\ndeprecated-attribute-ignored = [deprecation] El atributo `{ $attribute }` de `<{ $component }>` está obsoleto y se ignora.\n';
+const esContent = "# Spanish content catalog: the prose the core computes into the document.\n# Selected by `documentLocale` — the language the activity was written in.\n#\n# Spanish inflects. Adjectives follow their noun and agree with it in gender,\n# so every adjective below selects on `$gender`, the gender of the noun it\n# describes, and the composition messages put the noun first. Neither is\n# expressible by substituting into the English word order, which is why the\n# catalog controls the order and not the code.\n\n\n## Vocabulario de estilos\n\ncolor =\n    .black =\n        { $gender ->\n            [f] negra\n           *[m] negro\n        }\n    .white =\n        { $gender ->\n            [f] blanca\n           *[m] blanco\n        }\n    .gray = gris\n    .red =\n        { $gender ->\n            [f] roja\n           *[m] rojo\n        }\n    .orange = naranja\n    .yellow =\n        { $gender ->\n            [f] amarilla\n           *[m] amarillo\n        }\n    .green = verde\n    .cyan = cian\n    .blue = azul\n    .purple =\n        { $gender ->\n            [f] morada\n           *[m] morado\n        }\n    .pink = rosa\n    .brown = marrón\n\nline-width =\n    .thick =\n        { $gender ->\n            [f] gruesa\n           *[m] grueso\n        }\n    .thin =\n        { $gender ->\n            [f] delgada\n           *[m] delgado\n        }\n\nline-style =\n    .dashed =\n        { $gender ->\n            [f] discontinua\n           *[m] discontinuo\n        }\n    .dotted =\n        { $gender ->\n            [f] punteada\n           *[m] punteado\n        }\n\n# Sintagmas nominales: van detrás de «con» y no concuerdan con nada.\nfill-style =\n    .horizontal = líneas horizontales\n    .vertical = líneas verticales\n    .diagonal = líneas diagonales\n    .backdiagonal = líneas diagonales inversas\n    .dots = puntos\n    .diamonds = rombos\n\nnoun =\n    .line = línea\n    .line-segment = segmento\n    .ray = semirrecta\n    .vector = vector\n    .curve = curva\n    .function = función\n    .parabola = parábola\n    .polyline = polilínea\n    .polygon = polígono\n    .triangle = triángulo\n    .rectangle = rectángulo\n    .circle = círculo\n    .region = región\n    .point = punto\n    .square = cuadrado\n    .diamond = rombo\n    .cross = cruz\n    .plus = signo más\n\n# El nombre se parte: «polígono regular» lleva los adjetivos y «de 5 lados»\n# cierra el sintagma detrás de ellos. Si el complemento fuera delante, los\n# adjetivos quedarían separados del nombre con el que concuerdan («polígono\n# regular de 5 lados grueso rojo»).\nnoun-regular-polygon =\n    { $part ->\n        [tail] de { $numSides } lados\n       *[head] polígono regular\n    }\n\n# Además de los nombres de arriba, `$noun` puede ser «regular-polygon» (el\n# nombre que compone `noun-regular-polygon`) o el núcleo de un sintagma que no\n# se nombra en la descripción: «border», «fill», «text» y «background». Todos\n# ellos son masculinos en español —polígono, borde, relleno, texto, fondo—, así\n# que caen en el caso por defecto.\nnoun-gender =\n    { $noun ->\n        [line] f\n        [ray] f\n        [curve] f\n        [function] f\n        [parabola] f\n        [polyline] f\n        [region] f\n        [cross] f\n       *[other] m\n    }\n\n\n## Composición de estilos\n\nstyle-stroke =\n    { $parts ->\n        [width-style-color] { $lineStyle } { $width } { $color }\n        [width-color] { $width } { $color }\n        [style-color] { $lineStyle } { $color }\n        [width-style] { $lineStyle } { $width }\n        [width] { $width }\n        [style] { $lineStyle }\n       *[color] { $color }\n    }\n\n# El nombre va delante y los adjetivos detrás: «línea discontinua gruesa roja».\n# El complemento del nombre, si lo hay, cierra el sintagma: «polígono regular\n# grueso rojo de 5 lados».\nstyle-with-noun =\n    { $parts ->\n        [noun-tail] { $noun } { $description } { $nounTail }\n       *[noun] { $noun } { $description }\n    }\n\nstyle-filled-word =\n    { $gender ->\n        [f] rellena\n       *[m] relleno\n    }\n\nstyle-filled =\n    { $parts ->\n        [pattern] { $color } { $filled } con { $pattern }\n       *[plain] { $color } { $filled }\n    }\n\n# Aquí el complemento va pegado al nombre, y no al final como en\n# `style-with-noun`: «relleno de …» se lee como «lleno de …», así que «relleno\n# de 5 lados» diría otra cosa. «Polígono regular de 5 lados azul relleno».\nstyle-filled-with-noun =\n    { $parts ->\n        [pattern] { $noun } { $color } { $filled } con { $pattern }\n        [plain-tail] { $noun } { $nounTail } { $color } { $filled }\n        [pattern-tail] { $noun } { $nounTail } { $color } { $filled } con { $pattern }\n       *[plain] { $noun } { $color } { $filled }\n    }\n\n# «borde» es masculino, así que los adjetivos del borde concuerdan con él y no\n# con la figura que rodea.\nstyle-border-clause =\n    { $parts ->\n        [with-article] con un borde { $border }\n        [and] y borde { $border }\n        [and-article] y un borde { $border }\n       *[with] con borde { $border }\n    }\n\n# «de color» evita tener que concordar el color con un patrón en plural.\nstyle-fill =\n    { $parts ->\n        [pattern] { $pattern } de color { $color }\n       *[plain] { $color }\n    }\n\nstyle-unfilled = sin relleno\n\nstyle-text =\n    { $parts ->\n        [background] { $color } con un fondo { $background }\n       *[plain] { $color }\n    }\n\nstyle-background-none = ninguno\n\n\n## Palabras booleanas\n##\n## `true` y `false` siguen siendo sintaxis de DoenetML y no se traducen; aquí\n## solo se traduce la palabra que lee quien usa el documento.\n\nboolean-true = verdadero\nboolean-false = falso\n\n\n## Botones de respuesta\n\nanswer-submit-label = Revisar\nanswer-submit-label-no-correctness = Enviar respuesta\n\n\n## Funciones definidas a trozos\n\npiecewise-condition-or = o\npiecewise-condition-if = si\npiecewise-condition-otherwise = en otro caso\n";
+const esDiagnostics = '# Advertencias y errores mostrados a quien lee o escribe el documento.\n# Seleccionados por `uiLocale`.\n#\n# Los nombres de atributos y componentes de DoenetML (`through`, `endpoint`,\n# `numDimensions`, …) forman parte del lenguaje y se dejan en inglés.\n\n## `<lineSegment>`\n\nline-segment-attributes-ignored-with-endpoints =\n    { $attributesCount ->\n        [one] { $attributes } se ignora cuando se especifican los dos extremos\n       *[other] { $attributes } se ignoran cuando se especifican los dos extremos\n    }\n\nline-segment-attributes-ignored-with-endpoint-and-midpoint =\n    { $attributesCount ->\n        [one] { $attributes } se ignora cuando se especifican un extremo y el punto medio\n       *[other] { $attributes } se ignoran cuando se especifican un extremo y el punto medio\n    }\n\nline-segment-midpoint-offset-without-midpoint = midpointOffset no tiene efecto sin un punto medio\n\n## `<line>`\n\n# «Recta», no «línea», aunque `noun.line` en content.ftl diga «línea»: no es\n# una incoherencia, sino la diferencia entre describir el trazo dibujado («una\n# línea azul gruesa») y hablar del objeto geométrico, que en matemáticas es\n# una recta —de ahí «la ecuación de la recta».\n\nline-points-undetermined-dimensions = La recta pasa por puntos de dimensiones indeterminadas.\n\nline-points-too-few-dimensions = La recta debe pasar por puntos de al menos dos dimensiones.\n\nline-points-depend-on-variables = La recta pasa por puntos que dependen de las variables: { $variables }.\n\n# Enumeradas con coma en vez de «y»: las variables de <line> son `x` e `y` por\n# omisión, y «en las variables x y y» sería a la vez incorrecto (ante el sonido\n# /i/ la conjunción es «e») e ilegible. La coma es correcta sea cual sea el\n# nombre de la variable, que aquí no se conoce de antemano.\nline-equation-invalid-format = Formato no válido para la ecuación de la recta en las variables { $variable1 }, { $variable2 }.\n\n## `<ray>`\n\nray-overprescribed-through = La semirrecta está determinada por through, endpoint y direction. Se ignora el through especificado.\n\nray-dimension-mismatch = Discrepancia de numDimensions en la semirrecta.\n\n## `<vector>`\n\nvector-overprescribed-head = El vector está determinado por head, tail y displacement. Se ignora el head especificado.\n\nvector-dimension-mismatch = Discrepancia de numDimensions en el vector.\n\n## Atraer y restringir\n\nattract-to-without-nearest-point = No se puede atraer a un `<{ $component }>` porque no tiene la variable de estado nearestPoint.\n\nconstrain-to-without-nearest-point = No se puede restringir a un `<{ $component }>` porque no tiene la variable de estado nearestPoint.\n\nconstrain-to-interior-without-nearest-point = No se puede restringir al interior de un `<{ $component }>` porque no tiene la variable de estado nearestPoint.\n\n## `<choiceInput>`\n\nchoice-input-label-position-ignored = labelPosition se ignora en un choiceInput que no es inline\n\n## Ordenar hijos por índice\n\nchoice-input-indices-count-mismatch = Se ignoran los índices especificados para choiceInput porque su cantidad no coincide con la cantidad de hijos choice.\n\npretzel-indices-count-mismatch = Se ignoran los índices especificados para problem porque su cantidad no coincide con la cantidad de hijos problem.\n\nshuffle-indices-count-mismatch = Se ignoran los índices especificados para shuffle porque su cantidad no coincide con la cantidad de componentes.\n\nindices-ignored-out-of-range = Se ignoran los índices especificados para { $component } porque algunos están fuera de rango.\n\npretzel-indices-repeated = Se ignoran los índices especificados para pretzel porque algunos están repetidos.\n\npretzel-circuit-first-index = Se ignoran los índices especificados para pretzel en modo circuit porque el primer índice debe ser 1.\n\n## `<shuffle>` y `<sort>`\n\nstring-children-need-type = Para que `<{ $component }>` funcione con hijos de texto, se debe especificar el atributo `type`.\n\ninvalid-type-defaulting-to-math = Tipo no válido { $type } para el componente { $component }. Debe ser math, text, number o boolean. Se usa math.\n\nstring-not-valid-component-to-arrange = La cadena "{ $value }" no es un componente válido para { $component }. Se ignora.\n\n## Tipos y variables\n\ninvalid-type-defaulting-to-number = Tipo no válido { $type }, se establece el tipo en number.\n\ninvalid-variable-value = Valor no válido de una variable: `{ $value }`\n\n## Variantes\n\nvariant-index-must-be-number = El índice de variante { $index } debe ser un número\n\nvariant-index-must-be-integer = El índice de variante { $index } debe ser un número entero\n\n## `<sideBySide>`\n\nside-by-side-absolute-widths = `<{ $component }>` no está implementado para medidas absolutas. Los anchos se establecen como relativos.\n\nside-by-side-absolute-margins = `<{ $component }>` no está implementado para medidas absolutas. Los márgenes se establecen como relativos.\n\nside-by-side-no-block-child = `<{ $component }>` no es válido: debe tener al menos un hijo de bloque.\n\n## `<label>`\n\nlabel-for-ignored-on-graphical = Se ignora el atributo `for` en un `<label>` gráfico.\n\nlabel-for-must-resolve-to-one = El atributo `for` de `<label>` debe corresponder exactamente a un componente.\n\nlabel-for-unresolved = No se pudo resolver el atributo `for` de `<label>` a un componente.\n\nlabel-for-answer-with-authored-inputs = El atributo `for` de `<label>` hace referencia a un `<answer>` con entradas escritas explícitamente; haz referencia a la entrada directamente.\n\nlabel-for-answer-without-input = El atributo `for` de `<label>` hace referencia a un `<answer>` que no tiene ninguna entrada que etiquetar.\n\nlabel-for-must-reference-input-or-answer = El atributo `for` de `<label>` debe hacer referencia a una entrada o a un `<answer>`.\n\n## Accesibilidad\n\naccessibility-short-description-or-decorative = Por accesibilidad, `<{ $component }>` debe tener una descripción breve o estar marcado como decorativo.\n\naccessibility-video-short-description = Por accesibilidad, `<video>` debe tener una descripción breve.\n\naccessibility-input-short-description-or-label = Por accesibilidad, `<{ $component }>` debe tener una descripción breve o una etiqueta.\n\naccessibility-answer-input-short-description-or-label = Por accesibilidad, la entrada creada por un `<answer>` debe tener una descripción breve o una etiqueta.\n\naccessibility-short-description-contains-math = Las descripciones breves no deben contener componentes matemáticos como `<{ $component }>`. Expresa las matemáticas con palabras.\n\naccessibility-section-title-insufficient-contrast =\n    { $mode ->\n        [dark] { $colorName } no tiene suficiente contraste con el texto del encabezado de sección (modo oscuro) ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; se requiere al menos { $threshold }:1).\n       *[other] { $colorName } no tiene suficiente contraste con el texto del encabezado de sección ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; se requiere al menos { $threshold }:1).\n    }\n\n## `<circle>`\n\ncircle-through-points-non-numerical = No está implementado un `<circle>` que pase por { $count } puntos cuando los puntos no tienen valores numéricos.\n\ncircle-too-many-through-points = No se puede calcular una circunferencia que pase por más de 3 puntos.\n\ncircle-overprescribed-radius-center-points = No se puede calcular una circunferencia con radio, centro y puntos de paso especificados a la vez.\n\ncircle-center-with-multiple-points = No se puede calcular una circunferencia con centro especificado que pase por más de 1 punto.\n\ncircle-radius-too-small = No se puede calcular la circunferencia: dado que la distancia entre los dos puntos es { $distance }, el radio especificado { $radius } es demasiado pequeño.\n\ncircle-radius-with-many-points = No se puede crear una circunferencia que pase por más de dos puntos con un radio especificado.\n\ncircle-invalid-center-or-through-points = El centro o los puntos de paso de la circunferencia no son válidos.\n\ncircle-radius-center-with-multiple-points = No se puede calcular el radio de una circunferencia con centro especificado que pase por más de 1 punto.\n\ncircle-change-radius-non-numerical = No se puede cambiar el radio de una circunferencia con puntos de paso no numéricos\n\ncircle-radius-with-points-non-numerical = No se puede crear una circunferencia que pase por más de un punto con un radio especificado cuando no hay valores numéricos.\n\ncircle-change-center-non-numerical = No está implementado cambiar el centro de una circunferencia que pasa por puntos con valores no numéricos.\n\n## `<function>`\n\nfunction-domain-insufficient-dimensions =\n    { $intervals ->\n        [one] Dimensiones insuficientes para el dominio de la función. El dominio tiene { $intervals } intervalo pero la función tiene { $inputs ->\n            [one] { $inputs } entrada\n           *[other] { $inputs } entradas\n        }.\n       *[other] Dimensiones insuficientes para el dominio de la función. El dominio tiene { $intervals } intervalos pero la función tiene { $inputs ->\n            [one] { $inputs } entrada\n           *[other] { $inputs } entradas\n        }.\n    }\n\nfunction-domain-invalid-format = Formato no válido para el dominio de la función.\n\nfunction-ignoring-non-numerical =\n    { $type ->\n        [maximum] Se ignora el máximo no numérico de la función.\n        [minimum] Se ignora el mínimo no numérico de la función.\n        [extremum] Se ignora el extremo no numérico de la función.\n        [point] Se ignora el punto no numérico de la función.\n        [slope] Se ignora la pendiente no numérica de la función.\n       *[other] Se ignora { $type } no numérico de la función.\n    }\n\nfunction-ignoring-empty =\n    { $type ->\n        [maximum] Se ignora el máximo vacío de la función.\n        [minimum] Se ignora el mínimo vacío de la función.\n        [extremum] Se ignora el extremo vacío de la función.\n        [point] Se ignora el punto vacío de la función.\n       *[other] Se ignora { $type } vacío de la función.\n    }\n\nfunction-points-too-close = La función contiene dos puntos demasiado próximos entre sí. No se puede definir la función.\n\nfunction-iterates-input-output-mismatch =\n    { $inputs ->\n        [one] Las iteraciones de una función solo son posibles si el número de entradas es igual al número de salidas. Esta función tiene { $inputs } entrada y { $outputs ->\n            [one] { $outputs } salida\n           *[other] { $outputs } salidas\n        }.\n       *[other] Las iteraciones de una función solo son posibles si el número de entradas es igual al número de salidas. Esta función tiene { $inputs } entradas y { $outputs ->\n            [one] { $outputs } salida\n           *[other] { $outputs } salidas\n        }.\n    }\n\n## `<sequence>`\n\nsequence-invalid-length = Longitud de la secuencia no válida. Debe ser un entero no negativo.\n\nsequence-invalid-step = Paso de la secuencia no válido. Debe ser un número para una secuencia de tipo { $type }.\n\nsequence-invalid-endpoint-number = El valor de "{ $attribute }" de la secuencia numérica no es válido. Debe ser un número.\n\nsequence-invalid-endpoint-letters = El valor de "{ $attribute }" de la secuencia de letras no es válido. Debe ser una combinación de letras.\n\nsequence-invalid-endpoint = El valor de "{ $attribute }" de la secuencia no es válido.\n\nselect-from-sequence-coprime-not-numbers = Se ignora coprime porque no se están seleccionando números\n\nselect-from-sequence-coprime-with-exclude-combinations = Se ignora coprime porque se especificó excludeCombinations\n\n## Resolución de `target`\n\ntarget-not-found = Destino no válido para `<{ $source }>`: no se encuentra el destino.\n\ntarget-state-variable-not-found = Destino no válido para `<{ $source }>`: no se encuentra una variable de estado llamada "{ $property }" en un `<{ $component }>`.\n\n## `<odeSystem>`\n\node-system-variables-match-independent = Las variables de `<odeSystem>` deben ser distintas de la variable independiente.\n\node-system-duplicate-variable-names = No se pueden definir las funciones del lado derecho de la EDO con nombres de variables dependientes repetidos.\n\node-system-rhs-function-error = No se puede definir la función del lado derecho de la EDO. Error al crear la función de mathjs.\n\n## `<angle>`, `<parabola>` e `<intersection>`\n\nangle-too-many-lines = No se puede definir un ángulo entre { $count } rectas\n\nangle-invalid-through-point = Punto no válido en through de `<angle>`\n\nparabola-vertex-too-many-points = No está implementada una parábola con vértice que pase por más de 1 punto.\n\nparabola-too-many-points = No está implementada una parábola que pase por más de 3 puntos.\n\nintersection-too-many-items = No está implementada la intersección de más de dos objetos\n\n## Otros componentes matemáticos\n\nionic-compound-not-two-ions = No está implementado el compuesto iónico para algo distinto de dos iones.\n\nionic-compound-needs-cation-and-anion = El compuesto iónico solo está implementado para un catión y un anión.\n\nsolve-equations-cannot-evaluate = No se puede resolver la ecuación porque no se pudo evaluar: { $equation }\n\nmath-operators-operand-number-required = Se debe especificar operandNumber al extraer un operando matemático.\n\neigen-decomposition-failed = No se pudieron calcular los valores propios de la matriz\n\n## Renderizador PreFigure\n\nprefigure-x-label-position-unsupported = `<graph>`: xLabelPosition="left" no es compatible con el renderizador prefigure; se usa el comportamiento de posición derecha.\n\nprefigure-y-label-position-unsupported = `<graph>`: yLabelPosition="bottom" no es compatible con el renderizador prefigure; se usa el comportamiento de posición superior.\n\nprefigure-invalid-axis-bounds = `<graph>`: los límites de los ejes no son válidos para la conversión a prefigure; se usa el bbox predeterminado (-10,-10,10,10).\n\nprefigure-invalid-width = `<graph>`: el ancho no es válido para la conversión a prefigure; se usa el ancho de diagrama predeterminado 425.\n\nprefigure-invalid-aspect-ratio = `<graph>`: aspectRatio no es válido para la conversión a prefigure; se usa la relación de aspecto predeterminada 1.\n\nprefigure-annotations-not-rendered = `<graph>`: las anotaciones no se representan si no se usa el renderizador PreFigure.\n\nmultiple-annotations-children = Se encontraron varios hijos `<annotations>` en `<graph>`; se ignoran todos menos el último.\n\n## Referencias a otros componentes\n\ncopy-unrecognized-component-type = No se puede extender ni copiar un tipo de componente desconocido: { $type }.\n\ncopy-prop-not-found = No se encontró la propiedad { $property } en un componente de tipo { $component }\n\ncollect-no-source = No se encontró ninguna fuente para collect.\n\ncollect-invalid-component-type = No se pueden recolectar componentes de tipo `<{ $component }>` porque no es un tipo de componente válido.\n\nreference-index-unavailable = No se puede referenciar el índice `{ $reference }`\n\n## `<callAction>`\n\ncomponent-action-unavailable = No se puede llamar a { $action } en el componente `{ $reference }`\n\n## `<dataFrame>`\n\ndata-frame-inconsistent-row-lengths = Los datos tienen una forma no válida.  Las filas tienen longitudes distintas. Encontrado en componentIdx :{ $componentIdx }\n\ndata-frame-duplicate-column-names = Los datos tienen nombres de columna repetidos.  Encontrado en componentIdx :{ $componentIdx }\n\ndata-frame-missing-column-name = A los datos les falta el nombre de una columna.  Encontrado en componentIdx :{ $componentIdx }\n\n## `<answer>` y puntuación\n\nanswer-award-depends-on-own-response = Un award de esta respuesta depende de la respuesta enviada por el propio answer, lo que provocará un comportamiento inesperado.\n\nanswer-max-num-attempts-in-section-wide-check-work = Establecer `maxNumAttempts` en un `<answer>` dentro de un contenedor con `sectionWideCheckWork` no tiene efecto, porque el número de intentos lo controla el contenedor. Establece `maxNumAttempts` en el contenedor.\n\nnested-section-wide-check-work-max-num-attempts = Establecer `maxNumAttempts` en un contenedor con `sectionWideCheckWork` que está dentro de otro contenedor con `sectionWideCheckWork` no tiene efecto, porque el número de intentos lo controla el contenedor exterior. Establece `maxNumAttempts` en el contenedor exterior.\n\nanswer-attributes-need-symbolic-equality =\n    { $attributesCount ->\n        [one] El atributo { $attributes } no tendrá efecto si no se establece symbolicEquality.\n       *[other] Los atributos { $attributes } no tendrán efecto si no se establece symbolicEquality.\n    }\n\nanswer-invalid-type = Tipo no válido para answer: { $type }\n\n## `<module>`, `<conditionalContent>`, `<slider>` y pretzel\n\nmodule-attribute-child-needs-name = Como el componente `<{ $component }>` no tiene nombre, no se puede usar como atributo de módulo\n\nmodule-attribute-name-already-defined = El componente `<{ $component } name="{ $name }">` no se puede usar como atributo de un módulo porque el tipo de componente `<module>` ya tiene definido un atributo "{ $name }".\n\nconditional-content-condition-ignored = Se ignora el atributo `condition` en un `<conditionalContent>` que tiene hijos case o else.\n\nslider-markers-type-mismatch = El tipo de los marcadores no coincide con el tipo del slider.\n\npretzel-problem-needs-statement-and-answer = Pretzel no válido: cada `<problem>` debe contener un `<statement>` y un `<answer>`.\n\npretzel-circuit-first-problem-distractor = Pretzel no válido: en mode="circuit", el primer `<problem>` no puede ser un distractor.\n\n## Valores de atributos\n\nattribute-invalid-values =\n    { $valuesCount ->\n        [one] Valor no válido { $values } para el atributo `{ $attribute }`; se ignora.\n       *[other] Valores no válidos { $values } para el atributo `{ $attribute }`; se ignoran.\n    }\n\nattribute-must-be-references = Valor no válido `{ $value }` para el atributo `{ $attribute }`. El atributo debe estar compuesto de referencias que empiecen por `$`.\n\nmath-input-invalid-function-names = <mathInput>: se ignoran nombres de función no válidos en { $attribute }: { $names }. El segmento visible de cada nombre debe tener al menos 2 caracteres (letras o guiones); puede añadirse un sufijo opcional `|<alternativa de mathspeak>`.\n\n## Construcción de componentes a partir del código fuente\n\ncomponent-type-invalid = Tipo de componente no válido: `<{ $componentType }>`\n\nattribute-repeated = No se puede repetir el atributo { $attribute }.\n\nattribute-invalid-for-component = Atributo "{ $attribute }" no válido para un componente de tipo `<{ $componentType }>`.\n\n## Contraste de las definiciones de estilo\n\nstyle-definition-insufficient-contrast =\n    La definición de estilo { $styleNumber } no tiene suficiente contraste para { $context ->\n        [text-on-background] el color del texto sobre el color de fondo\n        [high-contrast] el color de alto contraste sobre el lienzo\n        [line] el color de las líneas sobre el lienzo\n        [marker] el color de los marcadores sobre el lienzo\n       *[text-on-canvas] el color del texto sobre el lienzo\n    }{ $mode ->\n        [dark] { " (modo oscuro)" }\n       *[light] { "" }\n    } ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; se requiere al menos { $threshold }:1).\n\nstyle-definition-dark-mode-text-background-contrast =\n    Aunque la definición de estilo { $styleNumber } especifica colores con suficiente contraste en modo claro, los colores de modo oscuro derivados de esos valores no tienen suficiente contraste entre el color del texto y el color de fondo ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; se requiere al menos { $threshold }:1). { $suggestion ->\n        [available] Para lograr suficiente contraste en modo oscuro, aumenta el contraste en modo claro (por ejemplo, con { $lightAttribute }="{ $lightColor }") o define el color de modo oscuro (por ejemplo, con { $darkAttribute }="{ $darkColor }").\n       *[none] Para lograr suficiente contraste en modo oscuro, aumenta el contraste en modo claro o sustituye los colores derivados mediante textColorDarkMode o backgroundColorDarkMode.\n    }\n\nstyle-definition-dark-mode-text-canvas-contrast =\n    Aunque la definición de estilo { $styleNumber } especifica un color de texto con suficiente contraste en modo claro, el color de texto de modo oscuro derivado de ese valor no tiene suficiente contraste sobre el lienzo ({ NUMBER($ratio, minimumFractionDigits: 2, maximumFractionDigits: 2) }:1; se requiere al menos { $threshold }:1). { $suggestion ->\n        [available] Para lograr suficiente contraste en modo oscuro, aumenta el contraste en modo claro (por ejemplo, con textColor="{ $lightColor }") o define el color de modo oscuro (por ejemplo, con textColorDarkMode="{ $darkColor }").\n       *[none] Para lograr suficiente contraste en modo oscuro, aumenta el contraste en modo claro o sustituye el color derivado mediante textColorDarkMode.\n    }\n\nsection-multiple-style-palettes = Una sección solo puede seleccionar un <stylePalette>; se usará el último.\n\n## Variantes únicas\n\nvariant-num-to-select-not-non-negative-integer = no se pueden determinar las variantes únicas de { $component } porque numToSelect no es un entero no negativo.\n\nvariant-num-to-select-not-constant-number = no se pueden determinar las variantes únicas de { $component } porque numToSelect no es un número constante.\n\nvariant-with-replacement-not-constant-boolean = no se pueden determinar las variantes únicas de { $component } porque withReplacement no es un booleano constante.\n\nvariant-select-weight-disables-unique = Las variantes únicas quedan desactivadas en select si alguna opción especifica selectWeight o selectForVariants\n\nvariant-coprime-undetermined = no se pueden determinar las variantes únicas de { $component } porque no se puede determinar si coprime es siempre falso.\n\nvariant-attribute-not-constant = no se pueden determinar las variantes únicas de { $component } porque { $attribute } no es constante.\n\nvariant-attribute-not-number = no se pueden determinar las variantes únicas de { $component } porque { $attribute } no es un número.\n\nvariant-attribute-wrong-type-for-sequence =\n    no se pueden determinar las variantes únicas de { $component } de tipo { $type } porque { $attribute } no es { $expected ->\n        [letters-combination] una combinación de letras\n        [math-expression] una expresión matemática válida\n        [integer] un entero\n       *[number] un número\n    }.\n\nvariant-length-not-integer = no se pueden determinar las variantes únicas de { $component } porque length no es un entero.\n\nvariant-sort-not-implemented = no se han implementado las variantes únicas de un { $component } con sort\n\nvariant-exclude-combinations-not-implemented = no se han implementado las variantes únicas de un { $component } con excludeCombinations\n\nvariant-math-exclude-not-implemented = no se han implementado las variantes únicas de un { $component } de tipo math con exclude\n\nvariant-non-constant-exclude-not-implemented = no se han implementado las variantes únicas de un { $component } con exclude no constante\n\n## Conversión a PreFigure\n\nprefigure-descendant-unsupported = { $subject }: no se admite en el renderizador prefigure de gráficos; se omite el descendiente.\n\nprefigure-descendant-invalid-geometry = { $subject }: geometría no finita o incompleta; se omite el descendiente.\n\nprefigure-curve-label-omitted = { $subject }: las etiquetas no se admiten en los elementos de curva convertidos; se omite la etiqueta.\n\nprefigure-curve-unsupported-definition-type = { $subject }: tipo de definición de función de curva no admitido \'{ $definitionType }\'; se omite el descendiente.\n\nprefigure-region-flip-functions-unsupported = { $subject }: atributo flipFunctions no admitido en regionBetweenCurves; se omite el descendiente.\n\nprefigure-region-non-formula-child = { $subject }: en regionBetweenCurves solo se admiten funciones hijas de tipo fórmula; se omite el descendiente.\n\nprefigure-label-position-unsupported =\n    { $subject }: labelPosition \'{ $labelPosition }\' no admitido para { $labelKind ->\n        [line-family] una etiqueta de la familia de líneas\n       *[point] una etiqueta de punto\n    }; se usa la alineación predeterminada de PreFigure.\n\nprefigure-fill-style-unsupported = { $subject }: PreFigure no admite el estilo de relleno \'{ $fillStyle }\'; se usa un relleno sólido.\n\nprefigure-line-style-unknown = { $subject }: estilo de línea desconocido \'{ $lineStyle }\'; se omite de la salida de PreFigure.\n\nprefigure-marker-style-mapped-to-diamond = { $subject }: el estilo de marcador \'{ $markerStyle }\' se asigna al estilo \'diamond\' de PreFigure.\n\nprefigure-marker-style-unsupported = { $subject }: PreFigure no admite el estilo de marcador \'{ $markerStyle }\'; se usa el estilo predeterminado.\n\n## Anotaciones de PreFigure\n\nannotation-ref-unresolvable = `<annotation>`: `ref` no válido; no se puede resolver el destino. Se omite la anotación.\n\nannotation-ref-multiple-targets = `<annotation>`: `ref` se resolvió a varios destinos; se usa el primero.\n\nannotation-ref-outside-graph = `<annotation>`: `ref` no válido; el destino está fuera del gráfico que lo contiene. Se omite la anotación.\n\nannotation-ref-unsupported-target = `<annotation>`: `ref` no válido; el destino no es un objeto gráfico admitido en la conversión a prefigure. Se omite la anotación.\n\nannotation-text-missing = `<annotation>`: falta `text` o está vacío; se emite texto vacío.\n\n## Composites y referencias\n\ncomposite-circular-dependency =\n    { $componentType ->\n        [none] Se detectó una dependencia circular.\n       *[other] Se detectó una dependencia circular en la que participa un componente `<{ $componentType }>`.\n    }\n\nreference-no-referent = No se encontró ningún referente para la referencia: `{ $reference }`\n\nreference-multiple-referents = Se encontraron varios referentes para la referencia: `{ $reference }`\n\n## Hijos que no coinciden\n\nchildren-invalid-attribute-format = Formato no válido para el atributo { $attribute } de `<{ $componentType }>`.\n\nchildren-invalid = Hijos no válidos para `<{ $componentType }>`: se encontraron hijos no válidos: { $children }\n\n## Se recurre a un valor predeterminado\n\nattribute-value-invalid-using-default = Valor no válido `{ $value }` para el atributo `{ $attribute }`; se usa el valor `{ $default }`\n\n## Carga de una versión de DoenetML\n\ndoenetml-version-not-found =\n    { $fallback ->\n        [none] No se encontró la versión { $version } de DoenetML.\n       *[other] No se encontró la versión { $version } de DoenetML. Se recurrirá a la versión { $fallback }\n    }\n\n## Lectura del DoenetML\n\n# Estos mensajes citan el propio texto del autor —`$tag`, `$value`,\n# `$attribute`…—, que se reproduce tal cual.\n\nparse-invalid-doenetml = DoenetML no válido: { $content }\n\nparse-tag-missing-close-tag = DoenetML no válido: la etiqueta `{ $tag }` no tiene etiqueta de cierre. Se esperaba una etiqueta autocerrada o una etiqueta `</{ $tagName }>`.\n\nparse-tag-error = DoenetML no válido: error en la etiqueta `<{ $tagName }>`\n\nparse-attribute-missing-value = DoenetML no válido: parece que al atributo `{ $attribute }` le falta un valor.\n\nparse-attribute-invalid = DoenetML no válido: atributo no válido `{ $attribute }`\n\nparse-attribute-value-invalid = DoenetML no válido: valor de atributo no válido `{ $value }`\n\n# $quote es la comilla que cerraría el par: `"` o `\'`.\nparse-attribute-value-quote-mismatch = DoenetML no válido: valor de atributo no válido `{ $value }`. Las comillas no coinciden. Parece que falta una `{ $quote }`\n\nparse-open-tag-name-missing = DoenetML no válido: se encontró una etiqueta sin nombre, por ejemplo `<`\n\nparse-tag-not-closed = DoenetML no válido: la etiqueta `{ $tag }` no se cerró (parece que falta un `>`).\n\nparse-self-closing-tag-name-missing = DoenetML no válido: se encontró una etiqueta sin nombre `<{ $content }>`\n\nparse-self-closing-tag-not-closed = DoenetML no válido: la etiqueta `{ $tag }` no se cerró (parece que falta `/>`).\n\nparse-tag-invalid-attributes = DoenetML no válido: la etiqueta `{ $tag }` no es válida. Puede que tenga atributos incorrectos.\n\nparse-close-tag-name-missing = DoenetML no válido: se encontró una etiqueta de cierre sin nombre, por ejemplo `</`\n\nparse-attribute-value-unquoted = Los valores de los atributos deben ir entre comillas: `{ $attribute }="{ $value }"`\n\nparse-close-tag-without-open-tag = DoenetML no válido: se encontró la etiqueta de cierre `{ $tag }`, pero no hay ninguna etiqueta de apertura que le corresponda\n\nparse-close-tag-mismatched = DoenetML no válido: la etiqueta de cierre no coincide. Se esperaba `</{ $expected }>`. Se encontró `{ $found }`\n\nparser-node-unconvertible = No se pudo convertir el nodo { $node } en un nodo Dast.\n\n## Nombres\n\nname-attribute-invalid =\n    Atributo name=\'{ $name }\' no válido. { $reason ->\n        [characters] Los nombres solo pueden contener letras, números, guiones bajos o guiones.\n       *[start] Los nombres deben empezar por una letra.\n    }\n\ncomponent-name-invalid-start = Nombre de componente "{ $name }" no válido. Los nombres deben empezar por una letra.\n\n## Azúcar sintáctico de `<answer>`\n\nanswer-video-watched-missing-video = Un `<answer>` de tipo videoWatched debe tener un atributo video\n\nanswer-video-watched-video-not-reference = Un `<answer>` de tipo videoWatched debe tener un atributo video que sea una referencia\n\nanswer-name-not-single-text = El atributo name de `<answer>` debe tener un único hijo de texto\n\n## Referencias a otro documento\n\nexternal-doenetml-recursion-limit = No se pudo obtener el DoenetML externo por exceso de niveles de recursión. ¿Hay alguna referencia circular?\n\nexternal-doenetml-unavailable = No se pudo obtener el DoenetML de { $attribute }="{ $uri }"\n\nexternal-doenetml-type-mismatch = El DoenetML obtenido de { $attribute }="{ $uri }" no es válido: no coincide con el tipo de componente "{ $componentType }"\n\n## Sintaxis obsoleta\n\n# `[deprecation]` es una marca literal que abre los tres mensajes; se deja\n# igual. $component es `none` cuando el cambio de nombre vale para todos los\n# componentes que aceptan el atributo y nombrar uno sería engañoso.\n\ndeprecated-attribute-renamed =\n    { $component ->\n        [none] [deprecation] El atributo `{ $from }` está obsoleto; usa `{ $to }` en su lugar.\n       *[other] [deprecation] El atributo `{ $from }` de `<{ $component }>` está obsoleto; usa `{ $to }` en su lugar.\n    }\n\ndeprecated-attribute-renamed-conflict =\n    { $component ->\n        [none] [deprecation] El atributo `{ $from }` está obsoleto y se ignora porque también se especificó `{ $to }`.\n       *[other] [deprecation] El atributo `{ $from }` de `<{ $component }>` está obsoleto y se ignora porque también se especificó `{ $to }`.\n    }\n\ndeprecated-attribute-ignored = [deprecation] El atributo `{ $attribute }` de `<{ $component }>` está obsoleto y se ignora.\n\n\n## Cobertura de idiomas\n\n# $locale es la etiqueta de idioma del documento, tal como se declaró.\npluralize-english-only = `<pluralize>` solo puede pluralizar en inglés, así que su texto queda sin cambios en un documento escrito en { $locale }. Escribe el plural directamente o indícalo con el atributo `pluralForm`.\n\n\n## Comprobación del esquema\n\n# $tag, $parent y $attribute reproducen lo que escribió quien redacta el\n# documento y se dejan tal cual; los signos `<`, `>` y las comillas invertidas\n# que los rodean son puntuación de este catálogo, no parte del nombre.\n\nschema-element-unrecognized = El elemento `<{ $tag }>` no es un elemento de Doenet reconocido.\n\nschema-element-not-allowed-at-root = El elemento `<{ $tag }>` no se permite en la raíz del documento.\n\nschema-element-not-allowed-inside = El elemento `<{ $tag }>` no se permite dentro de `<{ $parent }>`.\n\nschema-attribute-unrecognized = El elemento `<{ $tag }>` no tiene ningún atributo llamado `{ $attribute }`.\n\n# $allowed son los valores admitidos, cada uno ya entre comillas dobles y\n# enumerados según el idioma de quien lee. $isList indica si el atributo acepta\n# varios a la vez.\nschema-attribute-value-not-allowed =\n    { $isList ->\n        [true] El atributo `{ $attribute }` del elemento `<{ $tag }>` debe ser una lista en la que cada elemento sea uno de: { $allowed }\n       *[other] El atributo `{ $attribute }` del elemento `<{ $tag }>` debe ser uno de: { $allowed }\n    }\n';
 const BUNDLED_TRANSLATIONS = {
   es: {
     chrome: esChrome,
@@ -38935,6 +39036,12 @@ const DIAGNOSTIC_CODES = {
   "doenet-w0108": "deprecated-attribute-renamed",
   "doenet-w0109": "deprecated-attribute-renamed-conflict",
   "doenet-w0110": "deprecated-attribute-ignored",
+  "doenet-w0111": "pluralize-english-only",
+  "doenet-w0112": "schema-element-unrecognized",
+  "doenet-w0113": "schema-element-not-allowed-at-root",
+  "doenet-w0114": "schema-element-not-allowed-inside",
+  "doenet-w0115": "schema-attribute-unrecognized",
+  "doenet-w0116": "schema-attribute-value-not-allowed",
   "doenet-e0001": "pretzel-circuit-first-problem-distractor",
   "doenet-e0002": "component-type-invalid",
   "doenet-e0003": "attribute-repeated",
@@ -38989,18 +39096,6 @@ function asListArg(value) {
   }
   return void 0;
 }
-const LIST_TYPES = ["conjunction", "disjunction", "unit"];
-function listFormatFor(locale, type) {
-  const options = {
-    style: "long",
-    type: LIST_TYPES.includes(type) ? type : "conjunction"
-  };
-  try {
-    return new Intl.ListFormat(locale, options);
-  } catch {
-    return new Intl.ListFormat(DEFAULT_LOCALE, options);
-  }
-}
 function lowerArgs(args, locale) {
   if (args === void 0 || args === null) {
     return void 0;
@@ -43275,7 +43370,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-AuWkkb03-fPAEjoj_-Bca-IwLK.js").then((n2) => n2.s)).default;
+      const sha256 = (await import("./sha256-AuWkkb03-De5-_UeK-BiX7_wOX.js").then((n2) => n2.s)).default;
       digest = (data2) => sha256(data2, {
         asBytes: true
       });
@@ -70556,6 +70651,55 @@ function requireLib() {
 }
 var libExports = requireLib();
 const stringify = /* @__PURE__ */ getDefaultExportFromCjs(libExports);
+function returnContentLocaleDependencies({ ownLocale = false } = {}) {
+  return {
+    // For `<document>` itself, whose own `lang` is the language of its own
+    // content. The ancestor lookup below deliberately excludes the
+    // component it runs on — that is what lets a nested `<document>`
+    // detect that it is nested — so without this a root
+    // `<document lang="es">` would resolve its own prose against the
+    // host's locale instead of the one it declares.
+    //
+    // Off by default: a `stateVariable` dependency on a variable the
+    // component doesn't have is an error, not an empty value, and only
+    // `<document>` has `locale`.
+    ...ownLocale ? {
+      contentLocaleSelf: {
+        dependencyType: "stateVariable",
+        variableName: "locale"
+      }
+    } : {},
+    contentLocaleDocument: {
+      dependencyType: "ancestor",
+      componentType: "document",
+      variableNames: ["locale"]
+    },
+    // The host's locale, for a component with no `<document>` above it —
+    // which happens in tests and in a fragment rendered on its own. Without
+    // it `contentLocale` would have no tag to hand `Intl`, and a number
+    // would be grouped in English inside a Spanish document merely because
+    // the ancestor lookup came up empty.
+    contentHostLocale: {
+      dependencyType: "locale"
+    },
+    getContentTranslator: {
+      dependencyType: "translator"
+    }
+  };
+}
+function contentLocale(dependencyValues) {
+  return dependencyValues.contentLocaleSelf || dependencyValues.contentLocaleDocument?.stateValues.locale || dependencyValues.contentHostLocale || // A host that supplies an empty tag, which is not a locale but is also
+  // not a reason for a state variable to throw.
+  DEFAULT_LOCALE;
+}
+function isEnglishContent(dependencyValues) {
+  return contentLocale(dependencyValues).split(/[-_]/)[0].toLowerCase() === "en";
+}
+function contentTranslator(dependencyValues) {
+  return dependencyValues.getContentTranslator(
+    contentLocale(dependencyValues)
+  );
+}
 function returnScoredContainerAncestorDependency(...variableNames) {
   return {
     dependencyType: "ancestor",
@@ -70607,15 +70751,13 @@ function returnStandardAnswerAttributes() {
       createComponentOfType: "boolean",
       createStateVariable: "colorCorrectnessPreliminary",
       defaultValue: true,
-      public: true,
       groupName: "answer-grading",
       // The runtime stores the raw attribute value under
       // `colorCorrectnessPreliminary` so a derived `colorCorrectness`
-      // state def can combine it with the ancestor's setting. Authors
-      // should see only the derived `colorCorrectness` property, so
-      // hide the plumbing-named state var from the schema while
-      // keeping the attribute itself author-facing. See #1089.
-      stateVarExcludeFromSchema: true,
+      // state def can combine it with the ancestor's setting. That raw
+      // variable is plumbing, so it is not public: the attribute stays
+      // author-facing, and `$a.colorCorrectnessPreliminary` is not a
+      // reference anyone can write. See #1089.
       description: "Whether to color-code the response based on its correctness."
     },
     disableAfterCorrect: {
@@ -70628,19 +70770,21 @@ function returnStandardAnswerAttributes() {
     },
     submitLabel: {
       createComponentOfType: "text",
-      createStateVariable: "submitLabel",
+      createStateVariable: "submitLabelPreLocalize",
+      // The default is English here only so that authors see the words
+      // in the schema; `returnSubmitLabelStateVariableDefinitions`
+      // ignores this value when the attribute is unspecified and takes
+      // the label from the document's own language instead. An authored
+      // value is never translated — see the note there.
       defaultValue: "Check Work",
-      public: true,
-      forRenderer: true,
       groupName: "answer-grading",
       description: "Label for the submit button when correctness is shown."
     },
     submitLabelNoCorrectness: {
       createComponentOfType: "text",
-      createStateVariable: "submitLabelNoCorrectness",
+      createStateVariable: "submitLabelNoCorrectnessPreLocalize",
+      // See the note on `submitLabel`.
       defaultValue: "Submit Response",
-      public: true,
-      forRenderer: true,
       groupName: "answer-grading",
       description: "Label for the submit button when correctness is not shown."
     },
@@ -70662,9 +70806,64 @@ function returnStandardAnswerAttributes() {
     }
   };
 }
+function returnSubmitLabelStateVariableDefinitions({
+  ownLocale = false,
+  button = "the submit button"
+} = {}) {
+  return {
+    submitLabel: submitLabelDefinition({
+      name: "submitLabel",
+      translatedDefault: (t22) => t22("answer-submit-label"),
+      description: `Label for ${button} when correctness is shown.`,
+      ownLocale
+    }),
+    submitLabelNoCorrectness: submitLabelDefinition({
+      name: "submitLabelNoCorrectness",
+      translatedDefault: (t22) => t22("answer-submit-label-no-correctness"),
+      description: `Label for ${button} when correctness is not shown.`,
+      ownLocale
+    })
+  };
+}
+function submitLabelDefinition({
+  name: name2,
+  translatedDefault,
+  description,
+  ownLocale
+}) {
+  const authored = `${name2}PreLocalize`;
+  return {
+    description,
+    public: true,
+    shadowingInstructions: {
+      createComponentOfType: "text"
+    },
+    forRenderer: true,
+    returnDependencies: () => ({
+      [authored]: {
+        dependencyType: "stateVariable",
+        variableName: authored
+      },
+      ...returnContentLocaleDependencies({ ownLocale })
+    }),
+    definition({ dependencyValues, usedDefault }) {
+      const label = usedDefault[authored] ? translatedDefault(contentTranslator(dependencyValues)) : dependencyValues[authored];
+      return { setValue: { [name2]: label } };
+    }
+  };
+}
 function returnStandardAnswerStateVariableDefinition() {
   const stateVariableDefinitions = {};
+  Object.assign(
+    stateVariableDefinitions,
+    returnSubmitLabelStateVariableDefinitions()
+  );
   stateVariableDefinitions.showCorrectness = {
+    description: "Whether correctness is shown for the submitted response, after combining the attribute with hand-grading, any enclosing section's setting, and the activity-wide flag.",
+    public: true,
+    shadowingInstructions: {
+      createComponentOfType: "boolean"
+    },
     forRenderer: true,
     returnDependencies: () => ({
       showCorrectnessPreliminary: {
@@ -70699,6 +70898,11 @@ function returnStandardAnswerStateVariableDefinition() {
     }
   };
   stateVariableDefinitions.colorCorrectness = {
+    description: "Whether the response is color-coded by correctness, after combining the attribute with any enclosing section's setting and with whether correctness is shown at all.",
+    public: true,
+    shadowingInstructions: {
+      createComponentOfType: "boolean"
+    },
     forRenderer: true,
     returnDependencies: () => ({
       colorCorrectnessPreliminary: {
@@ -79164,19 +79368,20 @@ function returnScoredSectionAttributes() {
     },
     submitLabel: {
       createComponentOfType: "text",
-      createStateVariable: "submitLabel",
+      createStateVariable: "submitLabelPreLocalize",
+      // See the note in `returnStandardAnswerAttributes`: this default
+      // is shown to authors, but an unspecified attribute resolves to
+      // the label in the document's own language rather than to this
+      // English.
       defaultValue: "Check Work",
-      public: true,
-      forRenderer: true,
       groupName: "scoring",
       description: "Label for the section-wide submit button when correctness is shown."
     },
     submitLabelNoCorrectness: {
       createComponentOfType: "text",
-      createStateVariable: "submitLabelNoCorrectness",
+      createStateVariable: "submitLabelNoCorrectnessPreLocalize",
+      // See the note on `submitLabel`.
       defaultValue: "Submit Response",
-      public: true,
-      forRenderer: true,
       groupName: "scoring",
       description: "Label for the section-wide submit button when correctness is not shown."
     },
@@ -79192,6 +79397,12 @@ function returnScoredSectionAttributes() {
 }
 function returnScoredSectionStateVariableDefinition() {
   const stateVariableDefinitions = {};
+  Object.assign(
+    stateVariableDefinitions,
+    returnSubmitLabelStateVariableDefinitions({
+      button: "the section-wide submit button"
+    })
+  );
   stateVariableDefinitions.scoredDescendants = {
     returnDependencies: () => ({
       scoredDescendants: {
@@ -79360,6 +79571,11 @@ function returnScoredSectionStateVariableDefinition() {
     }
   };
   stateVariableDefinitions.showCorrectness = {
+    description: "Whether correctness is shown for the answers this section contains, after combining the attribute with any enclosing section's setting and with the activity-wide flag.",
+    public: true,
+    shadowingInstructions: {
+      createComponentOfType: "boolean"
+    },
     forRenderer: true,
     returnDependencies: () => ({
       showCorrectnessPreliminary: {
@@ -79388,6 +79604,11 @@ function returnScoredSectionStateVariableDefinition() {
     }
   };
   stateVariableDefinitions.colorCorrectness = {
+    description: "Whether the answers this section contains are color-coded by correctness, after combining the attribute with any enclosing section's setting and with whether correctness is shown at all.",
+    public: true,
+    shadowingInstructions: {
+      createComponentOfType: "boolean"
+    },
     forRenderer: true,
     returnDependencies: () => ({
       colorCorrectnessPreliminary: {
@@ -82850,6 +83071,22 @@ function splitSymbolsIfMath({
     ];
   }
 }
+function booleanWord(value, t22) {
+  return value ? t22("boolean-true") : t22("boolean-false");
+}
+function booleanFromWord(text, t22) {
+  const word = normalize(text);
+  if (word === "true" || word === normalize(booleanWord(true, t22))) {
+    return true;
+  }
+  if (word === "false" || word === normalize(booleanWord(false, t22))) {
+    return false;
+  }
+  return void 0;
+}
+function normalize(text) {
+  return String(text).toLowerCase();
+}
 class BooleanComponent extends InlineComponent {
   static componentType = "boolean";
   static componentDocs = {
@@ -83212,7 +83449,7 @@ class BooleanComponent extends InlineComponent {
       }
     };
     stateVariableDefinitions.text = {
-      description: 'The boolean rendered as a text string ("true" or "false").',
+      description: `The boolean rendered as a text string ("true" or "false", in the document's language).`,
       public: true,
       shadowingInstructions: {
         createComponentOfType: "text"
@@ -83222,25 +83459,27 @@ class BooleanComponent extends InlineComponent {
         value: {
           dependencyType: "stateVariable",
           variableName: "value"
-        }
+        },
+        ...returnContentLocaleDependencies()
       }),
       definition: function({ dependencyValues }) {
         return {
           setValue: {
-            text: dependencyValues.value ? "true" : "false"
+            text: booleanWord(
+              dependencyValues.value,
+              contentTranslator(dependencyValues)
+            )
           }
         };
       },
-      inverseDefinition({ desiredStateVariableValues }) {
-        let desiredText = String(
-          desiredStateVariableValues.text
-        ).toLowerCase();
-        let desiredBoolean;
-        if (desiredText === "true") {
-          desiredBoolean = true;
-        } else if (desiredText === "false") {
-          desiredBoolean = false;
-        }
+      inverseDefinition({
+        desiredStateVariableValues,
+        dependencyValues
+      }) {
+        let desiredBoolean = booleanFromWord(
+          desiredStateVariableValues.text,
+          contentTranslator(dependencyValues)
+        );
         if (desiredBoolean !== void 0) {
           return {
             success: true,
@@ -120584,6 +120823,13 @@ class Document extends BaseComponent {
       returnScoredSectionStateVariableDefinition()
     );
     delete stateVariableDefinitions.aggregateScores;
+    Object.assign(
+      stateVariableDefinitions,
+      returnSubmitLabelStateVariableDefinitions({
+        ownLocale: true,
+        button: "the section-wide submit button"
+      })
+    );
     stateVariableDefinitions.titleChildName = {
       forRenderer: true,
       returnDependencies: () => ({
@@ -145301,7 +145547,7 @@ class BooleanInput extends Input {
       }
     };
     stateVariableDefinitions.text = {
-      description: 'The current value rendered as a text string ("true" or "false").',
+      description: `The current value rendered as a text string ("true" or "false", in the document's language).`,
       public: true,
       shadowingInstructions: {
         createComponentOfType: "text"
@@ -145310,12 +145556,16 @@ class BooleanInput extends Input {
         value: {
           dependencyType: "stateVariable",
           variableName: "value"
-        }
+        },
+        ...returnContentLocaleDependencies()
       }),
       definition: function({ dependencyValues }) {
         return {
           setValue: {
-            text: dependencyValues.value ? "true" : "false"
+            text: booleanWord(
+              dependencyValues.value,
+              contentTranslator(dependencyValues)
+            )
           }
         };
       }
@@ -154529,7 +154779,8 @@ class PiecewiseFunction extends Function$1 {
         avoidScientificNotation: {
           dependencyType: "stateVariable",
           variableName: "avoidScientificNotation"
-        }
+        },
+        ...returnContentLocaleDependencies()
       }),
       definition: function({ dependencyValues }) {
         let functionVariable = dependencyValues.variable;
@@ -154635,7 +154886,7 @@ class PiecewiseFunction extends Function$1 {
               formulaLatexByLine.push(formulaLatex);
               subsetDomainsByLine.push([]);
               nonNumericConditionsByLine.push([
-                "\\text{otherwise}"
+                conditionOtherwise(dependencyValues)
               ]);
               break;
             }
@@ -154677,18 +154928,19 @@ class PiecewiseFunction extends Function$1 {
         }
         let conditionLatexByLine = subsetDomainsByLine.map(
           (subsetDomains, i2) => {
-            if (nonNumericConditionsByLine[i2].length === 1 && nonNumericConditionsByLine[i2][0] === "\\text{otherwise}") {
-              return "\\text{otherwise}";
+            const otherwise = conditionOtherwise(dependencyValues);
+            if (nonNumericConditionsByLine[i2].length === 1 && nonNumericConditionsByLine[i2][0] === otherwise) {
+              return otherwise;
             } else {
-              let conditionLatex = "\\text{if }";
+              let conditionLatex = conditionIf(dependencyValues);
               if (nonNumericConditionsByLine[i2].length > 0) {
                 conditionLatex += " " + nonNumericConditionsByLine[i2].join(
-                  " \\text{ or } "
+                  ` ${conditionOr(dependencyValues)} `
                 );
               }
               if (subsetDomains.length > 0) {
                 if (nonNumericConditionsByLine[i2].length > 0) {
-                  conditionLatex += " \\text{ or } ";
+                  conditionLatex += ` ${conditionOr(dependencyValues)} `;
                 } else {
                   conditionLatex += " ";
                 }
@@ -154840,6 +155092,18 @@ class PiecewiseFunction extends Function$1 {
     return stateVariableDefinitions;
   }
 }
+function conditionOr(dependencyValues) {
+  const t22 = contentTranslator(dependencyValues);
+  return `\\text{ ${t22("piecewise-condition-or")} }`;
+}
+function conditionIf(dependencyValues) {
+  const t22 = contentTranslator(dependencyValues);
+  return `\\text{${t22("piecewise-condition-if")} }`;
+}
+function conditionOtherwise(dependencyValues) {
+  const t22 = contentTranslator(dependencyValues);
+  return `\\text{${t22("piecewise-condition-otherwise")}}`;
+}
 function latexFromSubsetDomain({
   subsetDomain,
   dependencyValues,
@@ -154858,7 +155122,7 @@ function latexFromSubsetDomain({
         value: Context.fromAst(subint),
         dependencyValues
       }).toLatex(toLatexParams)
-    ).join(" \\text{ or }");
+    ).join(` ${conditionOr(dependencyValues)}`);
   } else {
     childDomainLatex = roundForDisplay({
       value: childDomainMath,
@@ -170682,9 +170946,9 @@ class Unparser {
     return `${startSheeet}${unparsedStart}:${endSheet}${unparsedEnd}`;
   }
 }
-function formatNumber(number, decimalSeparator) {
+function formatNumber(number, decimalSeparator2) {
   const numericString = number.toString();
-  return numericString.replace(".", decimalSeparator);
+  return numericString.replace(".", decimalSeparator2);
 }
 class ParserWithCaching {
   constructor(config2, functionRegistry, resolveSheetReference) {
@@ -183128,8 +183392,8 @@ class NumberLiteralHelper {
   constructor(config2) {
     this.config = config2;
     const thousandSeparator = this.config.thousandSeparator === "." ? `\\${this.config.thousandSeparator}` : this.config.thousandSeparator;
-    const decimalSeparator = this.config.decimalSeparator === "." ? `\\${this.config.decimalSeparator}` : this.config.decimalSeparator;
-    this.numberPattern = new RegExp(`^([+-]?((${decimalSeparator}\\d+)|(\\d+(${thousandSeparator}\\d{3,})*(${decimalSeparator}\\d*)?)))([eE][+-]?\\d+)?$`);
+    const decimalSeparator2 = this.config.decimalSeparator === "." ? `\\${this.config.decimalSeparator}` : this.config.decimalSeparator;
+    this.numberPattern = new RegExp(`^([+-]?((${decimalSeparator2}\\d+)|(\\d+(${thousandSeparator}\\d{3,})*(${decimalSeparator2}\\d*)?)))([eE][+-]?\\d+)?$`);
     this.allThousandSeparatorsRegex = new RegExp(`${thousandSeparator}`, "g");
   }
   numericStringToMaybeNumber(input) {
@@ -187812,7 +188076,7 @@ class Config {
       context,
       currencySymbol,
       dateFormats,
-      decimalSeparator,
+      decimalSeparator: decimalSeparator2,
       evaluateNullToZero,
       functionArgSeparator,
       functionPlugins,
@@ -187854,7 +188118,7 @@ class Config {
     this.dateFormats = [...configValueFromParamCheck(dateFormats, Array.isArray, "array", "dateFormats")];
     this.timeFormats = [...configValueFromParamCheck(timeFormats, Array.isArray, "array", "timeFormats")];
     this.functionArgSeparator = configValueFromParam(functionArgSeparator, "string", "functionArgSeparator");
-    this.decimalSeparator = configValueFromParam(decimalSeparator, [".", ","], "decimalSeparator");
+    this.decimalSeparator = configValueFromParam(decimalSeparator2, [".", ","], "decimalSeparator");
     this.language = configValueFromParam(language, "string", "language");
     this.ignoreWhiteSpace = configValueFromParam(ignoreWhiteSpace, ["standard", "any"], "ignoreWhiteSpace");
     this.licenseKey = configValueFromParam(licenseKey, "string", "licenseKey");
@@ -210527,11 +210791,12 @@ class Hint extends BlockComponent {
     });
   }
 }
+const LEADING_DECIMAL = /^-?\d+(?:\.\d+)?/;
 class IntComma extends Text {
   static componentType = "intComma";
   static rendererType = "text";
   static componentDocs = {
-    summary: "Renders a numeric value with thousands separators (e.g. 1,000,000)"
+    summary: "Renders a numeric value with the thousands separators of the document's language (e.g. 1,000,000)"
   };
   static returnStateVariableDefinitions() {
     let stateVariableDefinitions = super.returnStateVariableDefinitions();
@@ -210541,7 +210806,7 @@ class IntComma extends Text {
       newName: "originalValue"
     });
     stateVariableDefinitions.value = {
-      description: "The numeric value with thousands separators.",
+      description: "The numeric value, grouped as the document's language groups digits.",
       public: true,
       shadowingInstructions: {
         createComponentOfType: this.componentType
@@ -210550,17 +210815,23 @@ class IntComma extends Text {
         originalValue: {
           dependencyType: "stateVariable",
           variableName: "originalValue"
-        }
+        },
+        ...returnContentLocaleDependencies()
       }),
       definition: function({ dependencyValues }) {
-        let value = dependencyValues.originalValue;
-        let startAtLeastFourNumRegex = /^(-?\d+)(\d{3})/;
-        let matchObj = value.match(startAtLeastFourNumRegex);
-        while (matchObj !== null) {
-          value = value.replace(startAtLeastFourNumRegex, `$1,$2`);
-          matchObj = value.match(startAtLeastFourNumRegex);
+        const value = dependencyValues.originalValue;
+        const number = LEADING_DECIMAL.exec(value)?.[0];
+        if (number === void 0) {
+          return { setValue: { value } };
         }
-        return { setValue: { value } };
+        return {
+          setValue: {
+            value: formatDecimalString(
+              contentLocale(dependencyValues),
+              number
+            ) + value.slice(number.length)
+          }
+        };
       }
     };
     stateVariableDefinitions.text = {
@@ -214004,7 +214275,7 @@ es.extend(je);
 class Pluralize extends Text {
   static componentType = "pluralize";
   static componentDocs = {
-    summary: "Renders a word in its singular or plural form based on a count"
+    summary: "Renders a word in its singular or plural form based on a count (English only)"
   };
   static rendererType = "text";
   static createAttributesObject() {
@@ -214050,9 +214321,13 @@ class Pluralize extends Text {
         basedOnNumber: {
           dependencyType: "stateVariable",
           variableName: "basedOnNumber"
-        }
+        },
+        ...returnContentLocaleDependencies()
       }),
       definition: function({ dependencyValues }) {
+        if (!isEnglishContent(dependencyValues)) {
+          return pluralizeWithoutTheModel(dependencyValues);
+        }
         let text = es(dependencyValues.valuePrePluralize);
         let allwords = text.values().toNumber().all().terms().json();
         if (allwords.length === 0) {
@@ -214173,6 +214448,25 @@ class Pluralize extends Text {
 function numberDesignatesPlural(num) {
   return num !== 1;
 }
+function pluralizeWithoutTheModel(dependencyValues) {
+  const { valuePrePluralize, pluralForm, basedOnNumber } = dependencyValues;
+  if (pluralForm !== null) {
+    const makePlural = basedOnNumber === null || numberDesignatesPlural(basedOnNumber);
+    return {
+      setValue: { value: makePlural ? pluralForm : valuePrePluralize }
+    };
+  }
+  return {
+    setValue: { value: valuePrePluralize },
+    sendDiagnostics: [
+      codedDiagnostic({
+        type: "warning",
+        code: "doenet-w0111",
+        args: { locale: contentLocale(dependencyValues) }
+      })
+    ]
+  };
+}
 class Feedback extends BlockComponent {
   constructor(args) {
     super(args);
@@ -233539,4 +233833,4 @@ export {
   getDefaultExportFromCjs$1 as g,
   updateSyntaxFromV06toV07 as u
 };
-//# sourceMappingURL=index-5ZTpiqA9.js.map
+//# sourceMappingURL=index-wqA0T-Hr.js.map