Skip to content

Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.

docs(skill): make clear meta.translations works for any locale, not just the shipped examples

uygnoey29c79b5324c1
diff --git a/archify.zip b/archify.zip
index 9385e23c..6385f975 100644
Binary files a/archify.zip and b/archify.zip differ
diff --git a/archify/SKILL.md b/archify/SKILL.md
index 21a4e08e..c10282cb 100644
--- a/archify/SKILL.md
+++ b/archify/SKILL.md
@@ -123,9 +123,9 @@ Read `references/viewer-runtime.md` only when the user explicitly asks for Share
## Localizing the Viewer UI with meta.translations
-`en`, `zh-CN`, and `es` ship as built-in Viewer-chrome catalogs (`renderers/shared/i18n.mjs`); every other locale is supplied as translation *data*, not a renderer code change. Set `meta.locale` to any well-formed language tag and, unless it is `en`, `zh-CN`, or `es`, also set `meta.translations` to an object mapping canonical message keys (see `catalogKeys()`, or any key in `examples/locales/ko.json`) to translated strings whose `{placeholder}` tokens match the English source exactly. `validate`/`render`/`deliver` report coverage to stderr (`archify: meta.translations for locale "…" covers N/519 renderer-owned messages…`); a key that is missing, unknown, or has mismatched placeholders falls back to its English string rather than breaking the render. `meta.locale` without a built-in catalog or `meta.translations` falls back entirely to English Viewer UI and `<html lang="en">`, with the same disclosure on stderr — never a half-translated page.
+**Any well-formed locale tag works, for any language — not just the ones listed below.** `en`, `zh-CN`, and `es` ship as built-in Viewer-chrome catalogs (`renderers/shared/i18n.mjs`), so those three need nothing further. Every other locale — including ones with no example on disk — is supplied as translation *data* you (the authoring agent) write into the document, not a renderer code change and not a fixed list anywhere in this repo. To localize a diagram in a language with no existing example, set `meta.locale` to its tag and write `meta.translations` yourself: an object mapping canonical message keys (see `catalogKeys()`, or any key in `examples/locales/ko.json`) to translated strings whose `{placeholder}` tokens match the English source exactly. `validate`/`render`/`deliver` report coverage to stderr (`archify: meta.translations for locale "…" covers N/519 renderer-owned messages…`); a key that is missing, unknown, or has mismatched placeholders falls back to its English string rather than breaking the render. `meta.locale` without a built-in catalog or `meta.translations` falls back entirely to English Viewer UI and `<html lang="en">`, with the same disclosure on stderr — never a half-translated page. The renderer itself never translates anything or calls a translation service; every string in `meta.translations` must already be present in the document when you call `validate`/`render`/`deliver`.
-`examples/locales/ko.json` is a complete, checked-in Korean catalog (519/519 keys) — the worked example for this contract. `examples/locales/fr.partial.json` is a small, deliberately partial French catalog proving the mechanism needs no renderer or schema change to support a new, previously-unsupported language: only translation data.
+`examples/locales/` carries reusable, checked-in catalogs so a diagram doesn't need retranslating from scratch every time: `examples/locales/ko.json`, `fr.json`, `pt.json`, `ja.json`, `de.json`, `it.json`, and `ru.json` are each complete (519/519 keys). `examples/locales/fr.partial.json` is a small, deliberately partial French catalog demonstrating the missing-key/coverage-report path specifically. None of these are a closed enum — they're starting points to copy or extend, and a language with no file here works exactly the same way once you write its `meta.translations`.
`assets/template.html` also bundles D2Coding (SIL OFL, `assets/D2Coding-OFL.txt`) after JetBrains Mono in the monospace stack, and one weight of Pretendard (SIL OFL, `assets/Pretendard-OFL.txt`) in the "editorial" preset's serif heading stack, so Hangul in authored content or a Korean-translated chrome renders without missing glyphs. This is independent of `meta.translations`: it helps any locale or authored text that uses Hangul, and is not required for the translation mechanism itself to work.