doc-translator

To translate French Markdown documentation to English while preserving frontmatter, use an i18n-aware translation process that maintains the exact Markdown structure, switches the lang value from fr to en, and keeps the slug identical.

i18n-aware adaptation for UI labels works by applying predefined i18n mappings during translation to replace French UI terms, buttons, and menus with their consistent, idiomatic English equivalents.

No, translating FR documentation files requires both the original FR source files and English i18n references to ensure accurate terminology mapping and produce consistent localized outputs.

The best way to automate FR to EN document translation in a localization pipeline is to run the translation phase after initial FR files are generated, applying i18n mappings to produce structured EN outputs.

Translating Markdown files preserves the original document slug exactly, changing only the frontmatter language tag from fr to en while keeping the structural format intact.

You need to run a French to English translation phase after your documentation writer has produced all original FR files, ensuring the complete source content is ready for i18n-aware adaptation.