Skip to content

feat(i18n): localize Artifacts feature strings to Korean - #13810

Closed
zz1996zz wants to merge 3 commits into
stablyai:mainfrom
zz1996zz:feat/localize-artifacts-ko
Closed

zz1996zz wants to merge 3 commits into
stablyai:mainfrom
zz1996zz:feat/localize-artifacts-ko

Conversation

@zz1996zz

@zz1996zz zz1996zz commented Aug 11, 2026 •

Copy link
Copy Markdown

Summary

The Artifacts sidebar entry, settings pane, share flow, and publish dialogs shipped with no Korean translations (ko.json had 0 of the 82 auto.components.artifacts.* keys, plus related settings/sidebar keys, all falling back to English).

Fills in the 120 missing keys across auto.components.artifacts, auto.components.settings.artifacts, auto.components.settings.orcaAccount, and the sidebar/settings-navigation entries in src/renderer/src/i18n/locales/ko.json.

Translates "artifact" as "아티팩트" (the standard loanword for build/CI artifacts among Korean developers), keeps Orca, HTML, Markdown untranslated per the existing catalog policy, and matches terminology already used elsewhere in ko.json (삭제, 새로고침, 다시 시도, 로그인, 링크 복사, 닫기, 미리보기, etc.).

No English source, source code, or other locale files were touched — this is a ko.json-only change, consistent with the sparse-target-catalog architecture described in config/i18n-translation-source.md.

Screenshots

No visual change — this PR only adds translated strings to an existing, already-shipped UI surface. No new components, layouts, or styling.

Testing

  • pnpm lint
  • pnpm typecheck
  • pnpm test
  • pnpm build
  • Added or updated high-quality tests that would catch regressions, or explained why tests were not needed

Notes on the above:

  • pnpm lint and pnpm typecheck pass cleanly.
  • pnpm build completes successfully end to end (desktop + native).
  • pnpm test: full suite is 49,951 tests; 5 failed on the first full run, all in files unrelated to this change (agent-exec-handler.test.ts, run-electron-vite-dev.test.ts, ai-vault-session-worktree-map.test.tsx, terminal-output-frame-chunks-equivalence.test.ts). Re-ran each failing file in isolation: 4 of the 5 failures were parallel-run resource/timing flakiness and pass individually; the remaining 2 (agent-exec-handler.test.ts) fail only because my shell session has Claude Code/git env vars injected (CLAUDECODE, GIT_CONFIG_COUNT=4, etc.) that the test's environment-passthrough assertion doesn't expect — a local environment artifact, not a regression from this change. None of the failing files touch i18n, locales, or ko.json.
  • No new tests added: this PR only adds translated string values to an existing JSON catalog; correctness is verified by the localization catalog/extraction/coverage checks below, not unit tests.
  • Additionally ran the project's dedicated localization checks, all passing:
    • node config/scripts/verify-localization-catalog.mjs — no extra/missing keys, no interpolation-placeholder mismatches, no generic-term regressions; ko.json coverage increased with the new keys.
    • pnpm run verify:localization-extraction — passes (pre-existing unrelated diffs unchanged by this PR).
    • pnpm run verify:localization-coverage — passes.
  • Manually verified every new key's {{placeholder}} interpolation matches its English source exactly, and that key ordering in ko.json matches en.json for the touched sections.

AI Review Report

Reviewed the diff against config/i18n-translation-source.md and the existing ko.json conventions before writing translations: confirmed this change only needed to touch the sparse target locale file (English source and other locales untouched), checked that {{placeholder}} interpolation tokens are preserved verbatim in every translated string, and cross-referenced existing ko.json entries to keep terminology consistent (e.g. 삭제/새로고침/다시 시도/로그인/링크 복사/닫기/미리보기) rather than inventing new phrasing per string.

This PR does not touch any platform-specific code paths (no shortcuts, no file path handling, no shell invocation, no Electron APIs), so cross-platform behavior for macOS, Linux, and Windows is unaffected — it is a pure data change to one JSON locale file consumed identically on every platform.

Security Audit

No input handling, command execution, path handling, auth, secrets, dependency, or IPC changes. This PR only adds static translated string literals to an existing, version-controlled JSON locale file that is bundled at build time — no new user-controlled data paths are introduced.

Notes

No platform-specific behavior or follow-up work. This is a translation-only change limited to src/renderer/src/i18n/locales/ko.json.

@zz1996zz
zz1996zz requested a review from brennanb2025 as a code owner August 11, 2026 12:31
@zz1996zz
zz1996zz force-pushed the feat/localize-artifacts-ko branch from 6664acc to 795c995 Compare August 11, 2026 12:33
@coderabbitai

coderabbitai Bot commented Aug 11, 2026 •

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: eb702821-2abe-4928-b6ef-0eaad985cd32

📥 Commits

Reviewing files that changed from the base of the PR and between fdb047b and 32d484a.

📒 Files selected for processing (1)
  • src/renderer/src/i18n/locales/ko.json
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/renderer/src/i18n/locales/ko.json

Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review.


📝 Walkthrough

Walkthrough

Added Korean localization for artifact settings, sidebar navigation, account settings, sharing, publishing, previews, pagination, authentication, expiration, file constraints, validation, and error states.

Merge Risk: ⚪ Minimal · up to 32d48

This localized string update is limited to the Korean catalog and does not change application behavior; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description explains the implementation and testing, but it omits the required Linked Issue and several template sections, and does not use the required N/A visual-proof format. Add a linked issue, restore the required ELI5, What Changed, Why, Review, checklist, and boundary sections, and use N/A with a brief reason for visual proof.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the main change: adding Korean localization for Artifacts feature strings.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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.

The Artifacts sidebar entry, settings pane, share flow, and publish
dialogs shipped with no Korean translations. Fill in the 120 missing
keys under auto.components.artifacts, auto.components.settings.artifacts,
auto.components.settings.orcaAccount, and related sidebar/navigation
entries in ko.json.
@zz1996zz
zz1996zz force-pushed the feat/localize-artifacts-ko branch from 795c995 to 7c6a66f Compare August 18, 2026 00:39
@coderabbitai

coderabbitai Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@zz1996zz

Copy link
Copy Markdown
Author

Rebased onto main (6ee265e5) — the conflict in ko.json is resolved and the PR is mergeable again.

The conflict was purely additive on both sides: main added automationsTitle/automationsDescription and the automations/GlobalWorktreeVisibilitySourcesSetting blocks while this branch added the Artifacts keys. Both sides are kept, existing key order is preserved, and no translated value was changed. Verified that ko.json still has zero keys absent from en.json and zero {{placeholder}} mismatches.

@brennanb2025 whenever you have a moment — happy to adjust any wording.

@nwparker nwparker removed the P2 label Aug 19, 2026
Resolve ko.json artifacts conflict: keep the shipped wording from the
artifacts page redesign (stablyai#15233), drop keys it removed, translate the ones
it added.

# Conflicts:
#	src/renderer/src/i18n/locales/ko.json
@coderabbitai

coderabbitai Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1


ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 5cc0f65a-0e22-477d-8af1-a862b6b88400

📥 Commits

Reviewing files that changed from the base of the PR and between 4fc8b65 and fdb047b.

📒 Files selected for processing (1)
  • src/renderer/src/i18n/locales/ko.json

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

Comment thread src/renderer/src/i18n/locales/ko.json Resolved
…tring

The English source reads "Load the next page to continue." The Korean
copy had the purpose and action clauses swapped, which inverted the
meaning.
@OrcaWin

OrcaWin commented Oct 28, 2026

Copy link
Copy Markdown
Collaborator

Thanks @zz1996zz — the Korean Artifacts strings are already translated on main, so there's nothing left to apply here. Closing as already fixed.

@OrcaWin OrcaWin closed this Oct 28, 2026
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.

5 participants