baoyu-translate

Translating long markdown articles with consistent terminology requires a chunked workflow that processes content per-chunk while merging built-in glossaries and custom EXTEND.md entries to maintain term consistency throughout the document.

Quick translation mode performs a direct translation, normal mode analyzes the text before translating, and refined mode adds a review and polish step after translating to produce higher quality localized content.

Yes, you can preserve frontmatter metadata when translating markdown documents because the translation process is frontmatter-aware, ensuring that your YAML metadata remains intact while the body content is localized.

You can set up a custom glossary for multilingual document localization by creating an EXTEND.md file with your specific terminology entries, which the translator merges with built-in glossaries during the translation process to ensure consistent vocabulary.

Yes, markdown-based translation works with the markdown-it dependency to parse and process markdown formatting, allowing the tool to accurately translate text while preserving structural elements like headers, links, and code blocks.

You should use refined translation instead of quick translation when you need high-quality localized content, as refined mode includes analysis, translation, review, and polish steps, whereas quick mode is best for fast direct translations.