@stacksjs/stx 0.2.41 → 0.2.43

package/dist/site-builder/i18n.d.ts

@@ -21,10 +21,21 @@ export declare function resolveI18n(site: SiteConfig, projectRoot?: string): Res
  */
 export declare function translate(i18n: ResolvedI18n, locale: string, key: string): string;
 /**
- * Replace `{t:key}` markers in HTML with the translated string for
- * the given locale. The key syntax sidesteps stx's `{{ ... }}`
- * templating (which evaluates as JS at build time and would render
- * `t(...)` calls as empty when no `t` binding exists in scope).
+ * Replace `{t:key}` and `{t!:key}` markers in HTML with the translated
+ * string for the given locale. The key syntax sidesteps stx's
+ * `{{ ... }}` templating (which evaluates as JS at build time and
+ * would render `t(...)` calls as empty when no `t` binding exists
+ * in scope).
+ *
+ * Two variants:
+ *   - `{t:key}`  — value is HTML-escaped before substitution. Default
+ *     for ordinary text. Safe for any translator-supplied string.
+ *   - `{t!:key}` — value is substituted *raw*, without escaping. Use
+ *     this when the translation needs inline markup (e.g. `<strong>`,
+ *     `<a>`, `<br>`) so different languages can place emphasis where
+ *     their grammar requires. Translation values for these keys live
+ *     in the project's own translation files, so the trust boundary
+ *     is the same as the page template itself.
  *
  * Keys may use letters, digits, `_`, `.`, `-`. Anything that doesn't
  * match the pattern is left alone — runs after stx has finished its