Problem
The English, Japanese, and Korean READMEs currently reuse the same screenshot assets as the Chinese README. Several images contain Chinese UI copy or diagram labels, so non-Chinese readers see a Chinese product in the docs.
Scope
Start with the methodology / architecture infographic, which is fully labeled in Chinese.
Proposed naming
Keep files in assets/ with a language suffix. Do not use locale folders.
assets/llm_wiki_arch_en.jpg → README.mdassets/llm_wiki_arch_cn.jpg → README_CN.mdassets/llm_wiki_arch_ja.jpg → README_JA.mdassets/llm_wiki_arch_ko.jpg → README_KO.md
Language codes: en, cn, ja, ko. Leave logo.jpg unchanged (no UI text).
Follow-up
Other README screenshots still need localized versions if we want full i18n:
overview.jpg5-obsidian_compatibility.jpg3-knowledge_graph.jpgkg_community.jpgkg_insights.jpg1-deepresearch.jpg4-chrome_extension_webclipper.jpg
Same naming: {stem}_{locale}.jpg.
Problem
The English, Japanese, and Korean READMEs currently reuse the same screenshot assets as the Chinese README. Several images contain Chinese UI copy or diagram labels, so non-Chinese readers see a Chinese product in the docs.
Scope
Start with the methodology / architecture infographic, which is fully labeled in Chinese.
Proposed naming
Keep files in
assets/with a language suffix. Do not use locale folders.assets/llm_wiki_arch_en.jpg→README.mdassets/llm_wiki_arch_cn.jpg→README_CN.mdassets/llm_wiki_arch_ja.jpg→README_JA.mdassets/llm_wiki_arch_ko.jpg→README_KO.mdLanguage codes:
en,cn,ja,ko. Leavelogo.jpgunchanged (no UI text).Follow-up
Other README screenshots still need localized versions if we want full i18n:
overview.jpg5-obsidian_compatibility.jpg3-knowledge_graph.jpgkg_community.jpgkg_insights.jpg1-deepresearch.jpg4-chrome_extension_webclipper.jpgSame naming:
{stem}_{locale}.jpg.