Skip to content

feat(i18n): complete Korean website translations (100%)#2932

Open
say8425 wants to merge 2 commits intomanaflow-ai:mainfrom
say8425:feat/i18n-korean-web-translations
Open

feat(i18n): complete Korean website translations (100%)#2932
say8425 wants to merge 2 commits intomanaflow-ai:mainfrom
say8425:feat/i18n-korean-web-translations

Conversation

@say8425
Copy link
Copy Markdown
Contributor

@say8425 say8425 commented Apr 16, 2026

Summary

Add 222 missing Korean translations to web/messages/ko.json, bringing coverage from 600/822 keys (73%) to 822/822 (100%).

Translation scope

Section Keys Added
Blog posts (4 articles) 28
Docs: oh-my-claudecode, ohMyCodex, ohMyOpenCode, claudeCodeTeams ~80
Docs: SSH guide, configuration, keyboard shortcuts ~70
Remaining docs sections ~42
Wall of Love metadata 2
Total 222

Changes

  • web/messages/ko.json: 222 new translation entries (+290 lines)
  • No code changes, no other files affected

Quality checks

  • Valid JSON verified
  • Key count matches en.json exactly (822/822)
  • All placeholders preserved ({year}, {configPath}, {appName}, etc.)
  • All HTML-like tags preserved (, , , etc.)
  • Formal tone consistent with existing translations
  • Proper nouns kept untranslated (cmux, Ghostty, Claude Code, GitHub, etc.)
  • Terminology consistent: 워크스페이스, 창, 서피스, 사이드바

Test plan

  • Verify web/messages/ko.json is valid JSON and loads with next-intl
  • Visit cmux.com/ko and check translated pages render correctly
  • Check blog posts, docs (SSH, configuration, keyboard shortcuts) show Korean
  • Verify placeholders render with dynamic values

Review Trigger

@coderabbitai review
@cubic-dev-ai review

Summary by cubic

Complete Korean website translations by adding 222 strings to web/messages/ko.json (822/822, 100% coverage), covering four blog posts; docs for SSH, Claude Code Teams, and oh-my-*; keyboard‑shortcut chords + configuration; docs nav and community/blog/Wall of Love metadata. Follow‑up fixes clarify key‑chord terminology to “2단계 단축키(chord)” and localize the “Agent Integrations” nav to “에이전트 통합”; no other files changed.

Written for commit 5da05d4edc25aaa29ecba2e7a33c1633f5351ee6. Summary will update on new commits.

Summary by CodeRabbit

  • New Features

    • Added multiple new blog posts, reorganized blog sections, and surfaced SSH in the main navigation.
  • Documentation

    • Added comprehensive SSH docs and several new public docs (Claude/OhMy variants).
    • Expanded keyboard shortcuts with chord syntax and examples.
    • Improved configuration docs with settings file guidance and precedence.
    • Added/standardized meta titles across docs pages.
  • Chore

    • Updated site metadata (metaTitle/metaDescription) and reordered navigation.

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 16, 2026

@say8425 is attempting to deploy a commit to the Manaflow Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 16, 2026

📝 Walkthrough

Walkthrough

Updated Korean localization (web/messages/ko.json) with reorganized and expanded metadata across community, blog, and docs; added new blog posts and a new SSH docs section; consolidated duplicate meta fields and updated navigation order and wallOfLove metadata. (48 words)

Changes

Cohort / File(s) Summary
Community & Wall of Love
web/messages/ko.json
Moved metaTitle/metaDescription into the community object, consolidated duplicated metadata, and added wallOfLove.metaTitle/metaDescription.
Blog Restructuring & New Posts
web/messages/ko.json
Expanded blog with new top-level metadata blocks and new blog.posts entries (cmuxClaudeTeams, cmuxOmo, gpl, cmuxSsh); reorganized introducingCmux get-started fields and removed older root-level blog meta duplicates.
Documentation Metadata & Content
web/messages/ko.json
Added metaTitle to multiple docs sections, enriched docs.configuration with settingsFile* fields and restored exampleConfig, expanded keyboardShortcuts with chord syntax docs and cat.app labels, and consolidated meta keys across docs subsections.
SSH Documentation (New)
web/messages/ko.json
Introduced comprehensive docs.ssh object (title, meta, usage, flags, agent/relay/reconnect behavior, scp/drag-and-drop, notifications, and related subsections).
Navigation & Misc
web/messages/ko.json
Added nav.navItems.ssh, reordered navigation items (moved changelog), and adjusted assorted doc strings (e.g., docs.notifications.featureHeader, minor punctuation tweaks).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Poem

🐰 In JSON burrows I nibble and play,
Keys hop and nest in tidy array,
SSH tunnels and blog posts bloom,
Meta fields find their proper room,
A little hop — localization hooray! 🥕✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately and concisely describes the main change: completing Korean website translations to 100% coverage in a single sentence.
Description check ✅ Passed The description includes a clear summary of changes, quality checks, and testing plan. It provides detailed translation scope breakdown and notes that JSON validity was verified.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Apr 16, 2026

Greptile Summary

This PR adds 222 missing Korean (ko.json) translation entries, bringing coverage from 73% (600/822 keys) to 100% (822/822 keys). New translations cover blog posts (cmux Claude Teams, omo, GPL, SSH, Cmd+Shift+U), doc sections (SSH, claude-teams, oh-my-opencode/codex/claudecode, configuration, keyboard shortcuts), and Wall of Love metadata. Automated verification confirms: valid JSON, exact key-count parity with en.json, zero placeholder {var} mismatches, and zero HTML-tag mismatches.

Confidence Score: 5/5

Safe to merge — pure translation file, no logic changes, all structural invariants verified programmatically.

All 822 keys present and matching en.json structure, JSON is valid, zero placeholder or tag mismatches, proper nouns correctly left untranslated. No code changes outside the translation file.

No files require special attention.

Important Files Changed

Filename Overview
web/messages/ko.json +290 lines adding 222 translation entries; JSON is valid, 822/822 keys match en.json, all placeholders and HTML-like tags preserved, proper nouns kept untranslated as expected

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["web/messages/en.json\n(822 keys — source of truth)"] --> B{Key diff check}
    C["web/messages/ko.json\n(before PR: 600/822 keys)"] --> B
    B --> D["Missing: 222 keys\n(blog posts, SSH docs, agent integration docs,\nkeyboard shortcut chords, wall-of-love metadata)"]
    D --> E["PR #2932\nAdd 222 Korean translations"]
    E --> F["web/messages/ko.json\n(after PR: 822/822 keys ✓)"]
    F --> G{Validation}
    G --> H["Placeholder check\n{year}, {configPath}, etc. ✓"]
    G --> I["HTML-tag check\n<link>, <code>, <nightly> ✓"]
    G --> J["JSON validity ✓"]
    G --> K["Structure parity ✓"]
Loading

Reviews (1): Last reviewed commit: "feat(i18n): complete Korean website tran..." | Re-trigger Greptile

Add 222 missing Korean translations to web/messages/ko.json,
bringing coverage from 600/822 keys (73%) to 822/822 (100%).

Missing sections translated:
- Blog: 4 posts (cmux Claude Teams, cmux OMO, GPL, cmux SSH)
- Docs: oh-my-claudecode, ohMyCodex, ohMyOpenCode, claudeCodeTeams
- Docs: SSH guide, configuration, keyboard shortcuts (chords)
- Wall of Love metadata

All placeholders ({year}, {configPath}, etc.) and HTML-like tags
(<link>, <configPath>, etc.) preserved. Formal tone consistent
with existing translations.
@say8425 say8425 force-pushed the feat/i18n-korean-web-translations branch from 8b2077f to d230fde Compare April 16, 2026 02:21
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@web/messages/ko.json`:
- Around line 869-875: The "agentIntegrations" entry in the Korean messages file
is still in English; update the value for the "agentIntegrations" key in
web/messages/ko.json to the appropriate Korean translation (matching surrounding
localized entries), e.g., replace "Agent Integrations" with the Korean string
for agent integrations so the /ko sidebar is fully localized.
- Around line 347-350: The term "코드 단축키" is confusing; update the
"settingsFileChords" message to use a clearer Korean term such as "다단계 단축키" (or
"연속 단축키/다단계 키 조합") and reword the sentence accordingly to describe a prefix +
follow-up key (e.g., "[\"ctrl+b\", \"c\"]는 Ctrl+B를 누른 다음 C를 누르는 것을 의미합니다"); also
search and replace any other occurrences of the exact phrase "코드 단축키" elsewhere
in this file (including the similar wording around lines 422-427) so all
keys/messages use the new clearer term.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 08ca11c6-9c50-467a-925d-14908c1be45f

📥 Commits

Reviewing files that changed from the base of the PR and between 8b2077f and d230fde.

📒 Files selected for processing (1)
  • web/messages/ko.json

Comment thread web/messages/ko.json Outdated
Comment thread web/messages/ko.json
- "코드 단축키" → "2단계 단축키(chord)" — clearer term for key chords
- "Agent Integrations" → "에이전트 통합" — translate mixed-language label
Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

♻️ Duplicate comments (1)
web/messages/ko.json (1)

422-424: ⚠️ Potential issue | 🟡 Minor

Use one consistent Korean term for “chord” in shortcuts docs.

"단축키 코드" / "두 단계 단축키 코드" is still ambiguous. Please align this header/intro with the clearer wording already used in this file (2단계 단축키(chord)), so terminology is consistent across docs.

💡 Suggested wording
-      "chordsTitle": "단축키 코드",
-      "chordsIntro": "cmux는 <settingsFile>~/.config/cmux/settings.json</settingsFile>에서 두 단계 단축키 코드를 지원합니다. 전체 설정 파일 스키마는 <configurationLink>설정 문서</configurationLink>를 참조하세요.",
+      "chordsTitle": "2단계 단축키",
+      "chordsIntro": "cmux는 <settingsFile>~/.config/cmux/settings.json</settingsFile>에서 2단계 단축키(chord)를 지원합니다. 전체 설정 파일 스키마는 <configurationLink>설정 문서</configurationLink>를 참조하세요.",
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@web/messages/ko.json` around lines 422 - 424, Update the Korean terminology
for chords to match the file's preferred phrasing: replace the values of keys
"chordsTitle", "chordsIntro", and "chordsCallout" to use "2단계 단축키(chord)" (and
"2단계 단축키" where used in sentences) so the header/intro/callout consistently
refer to 2단계 단축키(chord) across the document.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@web/messages/ko.json`:
- Around line 422-424: Update the Korean terminology for chords to match the
file's preferred phrasing: replace the values of keys "chordsTitle",
"chordsIntro", and "chordsCallout" to use "2단계 단축키(chord)" (and "2단계 단축키" where
used in sentences) so the header/intro/callout consistently refer to 2단계
단축키(chord) across the document.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5e49e352-bcab-4569-8705-15a4945228cd

📥 Commits

Reviewing files that changed from the base of the PR and between d230fde and 5da05d4.

📒 Files selected for processing (1)
  • web/messages/ko.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant