- 
                Notifications
    
You must be signed in to change notification settings  - Fork 0
 
Closed
Description
Task:
You will translate and standardize Markdown files located under the repository folder "website.en/MarkDown". The goal is to produce consistent, natural American English across all Markdown content while preserving file structure, code blocks, frontmatter, images, links, filenames, and any technical formatting.
重要:
- 「website.en フォルダーの下の MarkDown フォルダーの下のすべての MarkDown ファイル」が、「website フォルダーの下の MarkDown フォルダーの下にある日本語版」のそれぞれの対応する MarkDown ファイルの英訳になるようにしてください。
 - Do not change filenames or file paths. Only modify file contents under "website.en/MarkDown".
 
Scope:
- Only modify files under "website.en/MarkDown" (do not change any other folders or files).
 - Translate every Markdown file completely into American English.
 - Where a file already contains English, ensure phrasing is natural, consistent, and follows American English conventions.
 - Replace any remaining Japanese text in those files. Keep all non-text assets (images, svg links) unchanged.
 - Keep file names, paths, and relative links unchanged.
 - Maintain Markdown syntax, code-block fences, YAML frontmatter (if present), and any mermaid or diagram blocks intact; translate only human-readable text.
 - Preserve author/credit lines and citations; translate their descriptive parts only if they are originally in Japanese.
 
Constraints and formatting:
- Use American English spelling and conventions (e.g., "color", "organization", "analyze").
 - Do NOT invent new sections or restructuring; keep headings and sections in the same order.
 - Do NOT translate inline code, code blocks, or language-specific identifiers. Translate code comments.
 - When a line contains both Japanese and English (mixed), fully convert to natural American English.
 - For list items, tables, and captions, preserve Markdown structure and replace only the textual content.
 - For images and links: translation should not change the URL or file name; only update alt-text, captions, and descriptive text.
 
Glossary requirements:
Proofreading and checks:
- Ensure files are encoded in UTF-8 without BOM.
 - Ensure no remaining Japanese characters exist in the translated files.
 - Keep consistency for terminology across files by consulting the provided glossary.
 
Output style:
- Use clear, technical documentation style, matching the original book voice.
 - Keep line wrapping compatible with Markdown.
 
Copilot