Files
solidcraft/assets/locales/pending/README.md
T
bherbruckandClaude Opus 5.5 1ceab2ed4c One file per change for new UI strings and attribution rows (#6448)
New UI strings go in assets/locales/pending/<slug>.json and new ATTRIBUTION.md rows in
attribution/pending/<slug>.md. The app build, xtask lists/i18n/assets read them as part of the
catalogs, and the Generated files workflow folds and deletes them on main with
cargo xtask fold-pending.

Refs #6439

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 03:01:41 +00:00

1.2 KiB

Pending UI strings

A pull request that adds UI strings adds one new file here instead of editing assets/locales/<locale>.json. Two pull requests then never touch the same file, so they never conflict.

  • Name it after the change, lowercase with dashes: sketch-trim-hints.json.

  • Contents: a map from locale code to {"message id": "text"}. Give English; add other locales you can translate (a locale you leave out falls back to English, as before):

    {
      "en": { "sketch.trim.hint": "Click a segment to trim it" },
      "de": { "sketch.trim.hint": "Segment zum Kürzen anklicken" }
    }
    
  • The id must not already be in that locale's catalog, nor in another pending file; the build and cargo xtask lists fail otherwise. To change an existing message, edit the catalog itself.

  • Don't sort or fold anything. The app, cargo xtask i18n and the tests read these files as part of the catalogs, so your strings work in your own pull request.

  • After a merge, the Generated files workflow runs cargo xtask fold-pending on main: it adds the messages to the catalogs (sorted, one per line) and deletes the files. Never run it in a pull request.