Skip to content

i18n: review machine-drafted Studio strings (fields, listings, collections) #112

Open

Description

@Madraka

The Studio strings added for collections (0.4), typed fields (0.5) and listings/structured data (0.6) were drafted for the 18 non-English languages with the translate skill. They are machine translations awaiting review: #91, #98, #100 and #107, namespaces collections, fields and listings, plus core keys for tool labels and error codes.

Turkish is reviewed (the owner checked the new strings). The other languages stay reviewed: false in apps/studio/src/i18n/locales.ts until a person who speaks them reviews the whole catalog.

For reviewers: the translators flagged coined terms, such as "listing fields", the comparison operators and the expiry wording ("unlist" / "hide"). Export with pnpm i18n:export --locale <xx> and import with pnpm i18n:import.

Done when: each language that gets a review has reviewed: true, and corrections are imported.

Activity

  1. Madraka commented on Nov 10, 2026

    @Madraka
    ContributorAuthor

    Machine-draft QA pass: summary (PR #194)

    An AI quality pass over the machine-drafted strings, before human review. It covers the same 494 keys in each of the 18 non-English languages:

    • the collections, fields and listings namespaces;
    • the core tool labels and error codes;
    • oauthConsent, connectedAgents and the setup-link sign-up text;
    • the status pages.

    Every language stays reviewed: false until a person who speaks it reviews it; this pass does not count as a review.

    Automatic checks covered placeholders, select values, CLDR plural categories and #, leftover English, and short labels more than 2.5× the English length. They found no ICU errors in any language.

    Semantic pass: every draft was back-translated and compared with the English. Only clear errors were fixed: 268 in total. After the fixes, the security wording holds in every language:

    • "not verified" stays a negation;
    • "Approve only if you…" stays a restriction;
    • "anyone … any name", "at most 90 days" and "never beyond your role" are all kept;
    • the setup-link text keeps that sign-up closes afterwards.
    Language Fixed For review Main finding
    tr 4 (owner's pack) "oturum aç" where Studio says "giriş yap"; one setup line read as if the app signs in
    de 6 10 Look-alike warning's last condition had no referent; "darüber hinaus" in the expiry count; Agenten → Agents
    es 1 7 "En cambio" (on the other hand) for "Changing…"; status pages use tú (open)
    fr 27 7 21 keys in "tu" in a "vous" catalog; two words for self-registered; "est le ou avant"
    it 1 13 Unlist action read as an order to the reader
    pt-BR 1 6 "Back by {time}" read as "back at"
    nl 3 8 Look-alike pronouns; verbinden vs koppelen; "Back by"
    pl 4 16 Loopback warning lost "you"
    ru 6 5 Self-registered label ungrammatical; two verbs for approve
    uk 5 7 Two words for connect and approve on the consent screen
    ja 1 5 "never beyond your role" had lost "never"
    ko 109 4 Formal 합니다체 in the new namespaces (Studio is 해요체); "never" lost
    zh-Hans 10 4 代理 (also "proxy") for agent; Studio says 智能体
    hi 32 8 Two words each for entry and collection; approve verb mixed
    id 15 5 "not yet verified" softened the identity labels; "Putuskan" reads as "Decide"; four keys in kamu
    ar 7 6 Entry/theme/computer terms mixed; one agreement error
    fa 29 10 Entry was ورودی and مطلب; informal تو in four keys
    he 7 9 Masculine-only verbs where the file is gender-neutral

    Every fix, with the old and new text and the reason, and every open review item is in docs/i18n-review/qa-2026-11.md. The Turkish keys changed since the owner's last review are in docs/i18n-review/tr.md.

    How to review your language

    1. Read the glossary of coined terms and your language's section of the QA report.
    2. Export with pnpm i18n:export, which writes .i18n/<locale>/<file>.json. English and each key's note are in .i18n/en/ and .i18n/descriptions.json.
    3. Edit only .i18n/<locale>/*.json. Keep every {argument}, and give each plural every category your language has.
    4. Import with pnpm i18n:import --locale <locale>, which checks the files and runs the catalog tests.
    5. Open a PR saying what you reviewed. If you change a glossary term, change it in every key and in the glossary.

    The full steps are in §7 of the guide. The links point to the PR branch until it merges.

  2. added 3 commits that reference this issue on Nov 10, 2026
  3. Madraka commented on Nov 11, 2026

    @Madraka
    ContributorAuthor

    Turkish: the owner asked the PM to check and approve the Turkish review pack. All 93 keys were reviewed (two independent reviewers and a judge per section, then read by the PM); 22 changed. Merged in #201, and docs/i18n-review/tr.md lists each change with its reason. Turkish stays reviewed: true; this issue stays open for the other 17 languages, which still await people who speak them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions