docs(l10n): add ko-kr, ja-jp, zh-cn, es-es, pt-br translations of the full course - #121
docs(l10n): add ko-kr, ja-jp, zh-cn, es-es, pt-br translations of the full course#121justinyoo wants to merge 12 commits into
Conversation
Adds full Japanese localization for the GitHub Copilot CLI for Beginners course under localization/ja-jp/. Files translated (13 total): - localization/ja-jp/README.md — course index - localization/ja-jp/00-quick-start/README.md - localization/ja-jp/01-setup-and-first-steps/README.md - localization/ja-jp/02-context-conversations/README.md - localization/ja-jp/03-development-workflows/README.md - localization/ja-jp/04-agents-custom-instructions/README.md - localization/ja-jp/05-skills/README.md - localization/ja-jp/06-mcp-servers/README.md - localization/ja-jp/06-mcp-servers/mcp-custom-server.md - localization/ja-jp/07-putting-it-together/README.md - localization/ja-jp/appendices/README.md - localization/ja-jp/appendices/additional-context.md - localization/ja-jp/appendices/ci-cd-integration.md Translation conventions: - Polite form (です・ます調) throughout - Brand names, code blocks, file paths, and identifiers preserved as-is - Relative paths adjusted for localization/ja-jp/ depth (../../.. prefix) - Sibling chapter links kept as localized references Co-authored-by: Copilot <[email protected]>
Re-map [text](#anchor) and cross-file [text](path#anchor) targets so they point to the localized heading slugs rather than the original English slugs. Preserves leading-hyphen status from the original anchor and mirrors github-slugger semantics for translated heading text. Co-authored-by: Copilot <[email protected]>
Headings that begin with emoji + space produce a slug with a leading hyphen on GitHub (e.g. ## 🎯 Learning Objectives -> #-learning-objectives). The original anchors in the source markdown are inconsistent about this (some include the leading hyphen, some don't), so the localized files now use the canonical, github-slugger-faithful slug for the localized heading text regardless of how the source anchor was written. Co-authored-by: Copilot <[email protected]>
…icalize GFM does not honor Pandoc-style explicit heading IDs; the ja-jp translator agent had appended them to 9 headings, where they rendered as literal text and polluted the auto-generated slug. Strip the annotations and re-canonicalize incoming anchors that referenced the old polluted slug. Co-authored-by: Copilot <[email protected]>
…ocale READMEs Mirror the new section added to the root README. Each locale's link list highlights the current language with ./README.md and points to the others via ../<locale>/README.md (English uses ../../README.md). Co-authored-by: Copilot <[email protected]>
Mirror the new TOC entry added to the root README. Each locale uses a short translation of 'Your Language' and points to the locale's own 'Use Your Preferred Language' heading slug. Co-authored-by: Copilot <[email protected]>
|
Hi @justinyoo. Let me know if you're still exploring this option and how it's working out. I have the co-op-translator (with a "polishing phase") working now so wanted to compare if you feel this option is viable. Let me know - thanks! |
|
Hi @DanWahlin I've been testing it with a custom skill. It looks OK for Korean for now. Let me add the Spanish one for you to take a look. Once the localisation result looks fine, we can add a GitHub Actions workflow. |
|
I added a localisation skill with two rules - one for Spanish and the other for Korean. Based on the skill, I reviewed all the docs. You can run it like:
|
Summary
Adds full localization of the course documentation into 5 languages under
localization/<locale>/, mirroring the original directory structure. Each translated chapter, README, and appendix is a standalone document; images continue to point at the originals in the repo-rootimages/folder. A new 🌐 Use Your Preferred Language section and matching TOC entry land in the rootREADME.mdso readers can switch languages from the landing page.Locales
ko-kr— 한국어ja-jp— 日本語zh-cn— 中文(简体)es-es— Españolpt-br— Português (Brasil)Each locale ships 13 documents (root README + chapters 00–07 + appendices), for 65 translated files in total.
What's localized
00-quick-startthrough07-putting-it-togetherappendices/README.md,appendices/additional-context.md,appendices/ci-cd-integration.mdWhat's intentionally NOT localized
AGENTS.md,CODE_OF_CONDUCT.md,CONTRIBUTING.md,GLOSSARY.md,SECURITY.md,SUPPORT.mdsamples/**(code samples and supporting files).github/**(templates, workflows)Quality work performed
After the initial machine-assisted translation pass, the following corrections were applied across every locale to ensure rendered output is faithful and links resolve:
../../../<chapter>/images/..., repo-root shared images via../../../images/...from chapters and../../images/...from each locale's root README.GLOSSARY.md,LICENSE, etc. updated to../../../GLOSSARY.mdstyle from chapter files.**[text](url)**rewritten to[**text**](url)so GitHub renders the bold inside the link (≈115 fixes).[text](#anchor)and cross-file[text](path#anchor)link in localized files now points at the localized heading slug, computed with a faithful github-slugger implementation (lowercase, drop emoji/punctuation, whitespace → hyphens, preserve the leading hyphen produced by a leading emoji + space).{#id}cleanup — the ja-jp draft used Pandoc-style explicit heading IDs that GitHub does not honor; these were stripped and the dependent anchors re-canonicalized.🌐 Use Your Preferred Languagesection is mirrored in every locale, and the top-of-page TOC strip includes a localized🌐 [Your Language]entry pointing to that locale's section.Verification
MD_LINK+HTML_SRC+HTML_HREFregex resolution) reports 0 missing files and 0 broken relative paths across all 5 locales.Notes for reviewers
localization/<locale>/...file at the same heading position.ko-kr/02-context-conversationstoko-kr/appendices/additional-context.md#…) are remapped to the target locale's heading slug, not the English slug.