Native review of monitoring-plan and webhook copy in deferred site locales #948

Activity

1. cemililik

   added

   documentationImprovements or additions to documentationImprovements or additions to documentation

   on Oct 15, 2026
2. cemililik

   added this to ForgeLM Project Planon Oct 15, 2026
3. github-project-automation

   moved this to Todo in ForgeLM Project Planon Oct 15, 2026
4. cemililik

   added a commit that references this issue on Oct 15, 2026

   fix: validate monitoring declarations and preserve endpoint identity

   ...

   e020d81
5. cemililik commented on Oct 16, 2026

   

   cemililik

   on Oct 16, 2026

   Last edited by cemililik

   CollaboratorAuthor

   More actions

   Progress from #954, plus the review packet for the parts that need native speakers. #954 references this issue and does not close it.

   Done in #954 (checked against EUR-Lex and the source strings)

   • German and Spanish: the Regulation's Art. 72 terms, "Beobachtung nach dem Inverkehrbringen" and "vigilancia poscomercialización".
   • French and Spanish: the hints say "metadata" again, so every locale separates ForgeLM's optional record, the provider's Art. 72 system and the Annex IV point 9 material.
   • German, French and Spanish: annex-citation, article and grammatical-gender slips in the touched strings ("das YAML", "le YAML", "el YAML"); one German term for the external stack.
   • German: the monitoring hint says "deklarieren" instead of "dokumentieren", the verb Art. 72(1) uses for the provider's own duty.
   • French and Turkish: straight apostrophes in the monitoring copy.
   • Chinese: full-width punctuation and 端点 in the webhook toggle copy.
   • English and Turkish: the hint now says Annex IV point 9 asks for "a detailed description of [the system], including the monitoring plan". The English source said "the detailed plan".
   • Turkish: the guides say "AB" and the site cites "(AB) 2024/1689 sayılı Tüzük". The site, the docs and the docs/standards/localization.md glossary follow the Turkish decisions below.
   • The new validation and interval keys keep their English fallback (acceptance criterion 2), and a test pins this.

   Still open: native review

   This covers acceptance criterion 1, the rest of criterion 4, and linking the reviewed wording from #902. Each item is a decision for a native reviewer; the current wording is quoted.

   German

   • Annex citation style. wizard.monitoring.enabled.hint writes "Annex IV Nummer 9", using the Regulation's own word "Nummer". Six compliance strings write "Annex IV §1". No string uses "Anhang IV".
   • "Detailed plan". wizard.monitoring.enabled.hint still says "umfasst den detaillierten Plan". Align it with the English source change above.
   • Misleading verb. In wizard.monitoring.enabled.detail, "plant keine Kontrollen" (for "schedules no checks") reads as "plans no controls".
   • Monitoring vs Beobachtung. "Monitoring" names ForgeLM's side and "Beobachtung nach dem Inverkehrbringen" the legal duty. Confirm that this split is intended.
   • Word choices:
     • "Drift-Warnungen" or "Drift-Alerts";
     • "Erklärung" in …enabled.detail, or the "deklarieren"/"Deklarierter" the labels use;
     • the exporter option "Custom Webhook".

   French

   • Annex and article citations. "l'Annex IV, point 9": EUR-Lex writes "l'annexe IV, point 9", and 24 strings use "Annex IV". Also "L'Art. 72" vs "L'article 72".
   • Typography. 16 keys, mostly wizard.error.*, use ’, while the monitoring copy now uses '. There is no narrow no-break space before ";" and ":".
   • Exporter option. "Webhook custom", while other strings use "personnalisé".
   • One word for two things. "surveillance" names both ForgeLM's declared plan and the legal term.
   • "Detailed plan". "comprend le plan détaillé": align it with the English source change above.

   Spanish

   • Term for ForgeLM's side. The wizard's monitoring strings use "monitoreo" and the Art. 9 and Art. 11 cards "monitorización". The legal term is "vigilancia poscomercialización".
   • Annex and article citations. "el Annex IV, punto 9" vs "el anexo IV, punto 9"; 25 strings use "Annex IV". Also "El Art. 72" vs "El artículo 72".
   • Exporter option. "Webhook custom" vs "personalizado".
   • "Detailed plan". "incluye el plan detallado": align it with the English source change above.

   Chinese

   • Site-wide punctuation. 235 of 754 values put ASCII , ; : ( ) next to Chinese text, and 26 use full-width forms. Pick one convention; GB/T 15834 uses full-width forms. The monitoring and webhook copy now uses full-width.
   • Monitoring term. 监控 (9 strings) vs 监测; 上市后监测 is the usual regulatory term for post-market monitoring.
   • Annex citation and wording.
     • "Annex IV 第 9 点" or "附件四第 9 项";
     • "形成文档" in …enabled.hint;
     • "包括详细计划": align it with the English source change above.
   • Endpoint. "endpoint" remains in home.cap.export.body and quickstart.step5.body, while the wizard now uses 端点.
   • Regulation citation. compliance.mapping.lead cites "Regulation (EU) 2024/1689" in English.

   Turkish (active locale): decided by the owner and applied in #954

   • Post-market monitoring. "piyasaya arz sonrası izleme", after the Turkish legal term for placing on the market (was "pazar sonrası izleme").
   • Annex points. "Annex IV §9", like the existing "Annex IV §1" strings; "madde" stays for Articles such as "Madde 72".
   • Metrics exporter. "exporter", kept in English like endpoint and webhook (was "aktarım sistemi").
   • Alert, notification, warning. A monitoring alert is "alarm", a webhook's chat message "bildirim" and a log warning "uyarı"; all three used to be "uyarı". This item was added during review.
   • Apostrophes. The straight apostrophe throughout; the six wizard.error.* strings that used ’ are fixed.

   English source

   • Apostrophes. 5 wizard.error.* keys use ’, while the rest of the wizard uses '.
   • Annex IV claim. compliance.art11.body says the nine Annex IV sections are "auto-populated from the run". This is tracked in [Wave 3] Medium — Docs: site/compliance.html #597.

   Also noticed: in DE/FR/ES/ZH, the English fallback strings render under <html lang="de|fr|es|zh"> with no lang="en", so a screen reader reads them with the wrong voice. CR-A18-086 in #685 covers the same problem on the guide, and the wizard needs the same fix.
6. cemililik

   added a commit that references this issue on Oct 16, 2026

   docs(tr): apply the owner's Turkish terminology decisions

   ...

   47fe7ba
7. cemililik commented on Oct 16, 2026

   

   cemililik

   on Oct 16, 2026

   CollaboratorAuthor

   More actions

   An update to the native-review packet above, after another verification round on #954.

   Changed in #954 — please confirm the wording

   • wizard.monitoring.enabled.hint now says that Annex IV §9 asks for a detailed description of the post-market monitoring system, its plan included, instead of "includes the detailed plan". German, French and Spanish take the wording of Annex IV point 9 in the official language versions of Regulation (EU) 2024/1689:
     • DE "verlangt eine detaillierte Beschreibung dieses Systems, einschließlich des Plans für die Beobachtung nach dem Inverkehrbringen"
     • FR "en exige une description détaillée, y compris le plan de surveillance après commercialisation"
     • ES "exige una descripción detallada de dicho sistema, incluido el plan de vigilancia poscomercialización"
     • ZH has no official text. The new line, Annex IV §9 要求对该系统进行详细描述，包括上市后监控计划。, needs a native check.
   • The hint cites "Annex IV §9" in every locale, as the other strings do with "§1"; German had "Annex IV Nummer 9" beside "Annex IV §1".
   • FR wizard.webhook.hint: the English "alerts" became "Envoyez des alertes Slack/Teams/Discord lors des événements d'entraînement."
   • ZH webhook card: full-width punctuation in wizard.webhook.title, wizard.webhook.url.hint and wizard.webhook.url.detail.

   A correction to the packet: the "Endpoint" item asked about "endpoint" in home.cap.export.body and quickstart.step5.body. Both name a product, Hugging Face Inference Endpoints ("HF-Endpoints", "HuggingFace Endpoints"), and should stay as they are; that item needs no change.

   Still open for the native review (unchanged)

   • DE: the monitoring detail says "plant keine Kontrollen" ("schedules no checks"; "Prüfungen" may read better) and mixes "Erklärung" with "deklarieren" / "Deklarierter".
   • ES: "monitoreo" in the monitoring copy, "monitorización" in compliance.art9.body.
   • FR / ES: the article and capitalisation used with "Annex IV", and the French terms for exporter and webhook, which differ from the EN/DE/TR choices.
   • ZH: 监控 is used throughout; whether 监测 fits the regulatory sense better is a native choice (the tests accept either).
   • French and English still use the curly apostrophe outside the monitoring copy; only Turkish switched to the straight one, by decision.
8. cemililik

   added 3 commits that reference this issue on Oct 16, 2026

   docs: cite Annex IV as §N everywhere and finish the Turkish terms

   ...

   7ac2d74

   fix(site): keep German, French and Spanish pages inside a phone's width

   ...

   6860cb4

   docs(tr): replace "Ek IV" and "piyasaya sunulmuş", and pin the monito…

   ...

   936f2b5
9. cemililik commented on Oct 16, 2026

   

   cemililik

   on Oct 16, 2026

   CollaboratorAuthor

   More actions

   Wording points for the native review of the deferred locales, found in the last verification round on #954. #954 leaves these strings unchanged:

   • Chinese: wizard.webhook.hint "在训练事件发送 Slack/Teams/Discord 警报。" may read as missing a verb ("在训练事件发生时发送 …"?). The Operations step tutorial mixes " / " and "+" with full-width punctuation.
   • Spanish: the wizard says "monitoreo" (4 strings) and the compliance page "monitorización" (2); pick one.
   • German: "Warnungen" names both a drift alert (Drift-Warnungen) and a log warning (Warnungen im Prozesslog); the Turkish copy separates alarm from uyarı for the same reason. wizard.webhook.url.hint "Env-Variable die sie trägt" lacks the comma before the relative clause.
   • French: wizard.monitoring.metrics_export.custom reads "Webhook custom", English word order; "Webhook personnalisé" would follow French.
   • French: one string says "d'Annex IV" (compliance.art11.body), others "de l'Annex IV" and "l'Annex IV"; Spanish uses its article consistently.
10. cemililik

    added 3 commits that reference this issue on Oct 17, 2026

    docs(site): use the Regulation's terms in deferred-locale monitoring …

    ...

    baf98de

    docs(site): address locale review of the monitoring copy

    ...

    a5c24c3

    docs(site): address the second locale review of the monitoring copy

    ...

    fa7078a