Gå til hovedinnhold

kapi exec translate-after

kapi translate-after [files...]

Translate After

Commandexec translate-after
Try it

Runs in your browser against a small sample file. Edit the command before running, or press Run to execute it as shown.

kapi exec translate-after
Flags
FlagTypeDefaultDescription
--concurrency , -jint0max parallel files (0 = auto)
--encoding , -estringcharset the input is read in; a byte-order mark in the file wins (default: the project's defaults.encoding, then UTF-8)
--engine stringformat engine for detected files: native or a plugin name (default: native, then plugins)
--fail-on-unknown boolfalseexit with error if any file cannot be processed (default: skip with warning)
--format , -fstringoverride input format detection
--json boolfalseoutput results as JSON
--level stringwrittenWhat a block's source must reach before its translations are produced: written (its checks pass) or established (a person reviewed it); none holds nothing (none, written, established)
--map , -mstringArraymap glob pattern to format (e.g. '*.docx=okf_openxml:test')
--no-warn boolfalsesuppress warnings for skipped files
--pack boolfalsewhen transforming a .kpz, also eject the result to the .kpz (auto-pack)
--parallel-blocks int0fan out block processing across N goroutines (0 = off)
--progress boolfalseshow progress bar
--project , -pstringpath to a kapi.yaml project recipe or its directory (auto-discovered from cwd if omitted)
--source-lang stringsource language (e.g. en, en-US; defaults to the project's source_language, else en)
--strict boolfalsealias for --fail-on-unknown
--trace stringwrite flow trace JSON to file (for flow visualization)

← Back to the Command Reference