CLI v0 formats
Match an installed legacy parser to its locale layout and verify the reconstructed native file.
Choose the bucket by the data you want to extract and the files you expect back. V0 uses the bucket's type to select a parser; the extension does not override it. A JSON catalog and a multi-locale Xcode catalog therefore need different configuration even when both contain messages.
Choose the output model first #
Most buckets write separate locale files using [locale] in the path. CSV, Xcode string catalogs, JSON dictionaries, and Vue i18n blocks can hold several locales in one file. For shared output, inspect both the target section and the source section after translation.
| Bucket | Content | Documented output model |
|---|---|---|
json, json5, jsonc | Structured JSON variants | Separate locale files |
json-dictionary | JSON values containing locale-keyed objects | Shared file |
yaml | YAML catalog | Separate locale files |
yaml-root-key | YAML wrapped in the output locale's root key | Separate locale files |
markdown, mdx, markdoc | Markdown-family documents | Separate locale files |
html, mjml | HTML and email markup | Separate locale files |
android | Android XML resources | Separate locale files |
xcode-strings, xcode-stringsdict | Apple strings and plural resources | Separate locale files |
xcode-xcstrings | Xcode string catalog | Shared file |
flutter | ARB catalog | Separate locale files |
po | Gettext PO | Separate locale files |
properties | Java properties | Separate locale files |
csv | Multi-locale CSV | Shared file |
csv-per-locale | One CSV per locale | Separate locale files |
xml, xliff | XML and XLIFF | Separate locale files |
srt, vtt | Subtitles | Separate locale files |
php | PHP localization arrays | Separate locale files |
typescript | TypeScript localization content | Separate locale files |
vue-json | Locale-keyed Vue i18n JSON blocks | Shared file |
txt | Plain text | Separate locale files |
This is the legacy bucket family, not a compatibility list for other tools. Earlier v0 releases can predate individual entries. TypeScript, PHP, and Vue parsers handle their supported localization structures; their presence does not authorize arbitrary executable-source rewriting.
The 0.138.10 dispatcher also contains ail, ejs, twig, dato, and xcode-xcstrings-v2. Retain the parser already used by an installed project until its input and output have been inspected. A schema enum alone is not sufficient: the legacy schema also names compiler, but this dispatch path has no corresponding loader.
yaml-root-key reconstructs only the selected locale root. Do not point source and target at one shared YAML file: a write can replace its other roots. Use a locale-specific path such as locales/[locale].yml. This differs from a JSON dictionary or Vue block that explicitly merges a new locale into the original structure.
Configure a representative file #
For JSON, the same pattern identifies a source file and separate targets:
{
"buckets": {
"json": { "include": ["src/locales/[locale].json"] }
}
}For a shared Xcode catalog beside Android locale-specific resources:
{
"buckets": {
"xcode-xcstrings": { "include": ["ios/Localizable.xcstrings"] },
"android": {
"include": ["android/app/src/main/res/values-[locale]/strings.xml"]
}
}
}Adapt Android locale spelling and resource directories to the application. After the first run, validate both native formats with their build tools and confirm the application loads the selected target. Configuration acceptance alone does not establish that path.
Discover files without selecting generated output #
Paths resolve relative to i18n.json; * matches within a level. Recursive ** arrived in 0.135.0. It excludes node_modules, .git, dist, build, .next, and .turbo by default. Exclude any additional generated content explicitly:
{
"buckets": {
"markdown": {
"include": ["docs/[locale]/*.md"],
"exclude": ["docs/[locale]/drafts/*.md"]
}
}
}For several packages, choose shared or per-package configuration according to languages and localization engine ownership. Narrow paths keep generated output from becoming unexpected source input.
Check format-specific protections #
For key/value catalogs, apply key controls according to who owns each value. JSONC and Xcode catalog comments can carry translator notes. Free-form documents and subtitles do not necessarily use those features in the same way.
Inspect what the parser reconstructed: catalog keys and values, document markup and links, subtitle timing cues, or native resource identifiers. Accept the output only after the consuming parser or build can use it. When migrating, consult the current Formats manual and the invoking tool's supported list rather than assuming this legacy matrix carries over.