check-consistency

To check terminology consistency in Markdown documents, scan specified paths or the entire documentation directory to validate terms against an approved glossary, flagging missing entries, inconsistent translations, and untranslated terms.

Document terminology validation scans Markdown files against a predefined glossary to detect inconsistent translations by identifying instances where a single term is used with multiple different translations across the document set.

Yes, you can validate game rulebook translations by loading a YAML glossary to verify that game-specific terms like character classes and stats are translated consistently throughout the entire Markdown document set.

You can generate JSON reports for terminology validation by running the Python scanning scripts with JSON output options, enabling CI gating to block document deployments when untranslated terms or glossary inconsistencies are detected.

The best way to identify untranslated terms missing from a glossary is to scan Markdown documents against approved glossary entries, which automatically flags terms that appear in documents but are missing from the glossary.

Python scripts for glossary validation require a properly structured predefined glossary to function effectively, meaning translation errors or missing glossary entries will be flagged but not automatically corrected.