kapi exec term-check

$ kapi term-check [files...]

Terminology Check

Commandexec term-check

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 term-check app.xliff --source-lang en --target-lang fr

Flags

Flag	Type	Default	Description
--case-sensitive	bool	false	Whether term matching is case-sensitive
--concurrency, -j	int	0	max parallel files (0 = auto)
--encoding, -e	string		charset the input is read in; a byte-order mark in the file wins (default: the project's defaults.encoding, then UTF-8)
--engine	string		format engine for detected files: native or a plugin name (default: native, then plugins)
--fail-on-unknown	bool	false	exit with error if any file cannot be processed (default: skip with warning)
--format, -f	string		override input format detection
--json	bool	false	output results as JSON
--map, -m	stringArray		map glob pattern to format (e.g. '*.docx=okf_openxml:test')
--no-warn	bool	false	suppress warnings for skipped files
--pack	bool	false	when transforming a .kpz, also eject the result to the .kpz (auto-pack)
--parallel-blocks	int	0	fan out block processing across N goroutines (0 = off)
--progress	bool	false	show progress bar
--project, -p	string		path to a kapi.yaml project recipe or its directory (auto-discovered from cwd if omitted)
--source-lang	string		source language (e.g. en, en-US; defaults to the project's source_language, else en)
--strict	bool	false	alias for --fail-on-unknown
--target	string		the translation of the one source file named, in --target-lang, to check it against (a file that holds both, such as XLIFF, needs none)
--target-lang	string		target language (e.g. fr, de-DE); one per run
--term-rules	string		YAML or JSON file of term rules to check against instead of the project's terms store: a `term_rules:` list of {term, replacement}, the shape the MCP tool takes
--termstore	string		named terms or path to a terms store (defaults to the project terms store)
--trace	string		write flow trace JSON to file (for flow visualization)

More examples

$ kapi exec term-check messages.json --source-lang en --target-lang fr

← Back to the Command Reference