kata-translate

Translating technical Markdown without breaking structure requires preserving code blocks, file paths, and URLs while translating only prose. A rule-driven approach ensures localized output remains valid and functional.

Maintaining consistent terminology across target language translations requires applying layered language rules, including default, cross-cutting, and language-specific directives. This enforces canonical term preservation throughout the localized documentation files.

Path mapping for localized framework documentation detects framework-specific files and computes correct destination paths for each target language. It maps source paths to language-specific output locations to ensure translated files are correctly placed.

Yes, you can use validation to check completeness and correct file placement for localized docs. After translating prose while preserving Markdown and code, validation ensures the translated file is complete and located in the correct destination path.

Yes, i18n translation supports preserving canonical terms and URLs in technical documentation. By reading translation directives and layered language rules, the process translates only translatable prose while explicitly protecting URLs and canonical terminology.

The main limitation is that code blocks, file paths, URLs, and canonical terms cannot be translated and must be strictly preserved. Additionally, achieving correct output requires reading translation directives and applying layered language rules to avoid misplaced or incomplete files.