Skip to content

🌐 Updated Korean (ko) translations#29094

Merged
9larsons merged 2 commits into
TryGhost:mainfrom
daeho-ro:feature/korean
Jul 7, 2026
Merged

🌐 Updated Korean (ko) translations#29094
9larsons merged 2 commits into
TryGhost:mainfrom
daeho-ro:feature/korean

Conversation

@daeho-ro

@daeho-ro daeho-ro commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

ref #23361

  • Filled remaining untranslated strings and fixed a few existing ones
  • Used 홍길동 for the "Jamie Larson" placeholder

Got some code for us? Awesome 🎊!

Please take a minute to explain the change you're making:

  • Why are you making it?
  • What does it do?
  • Why is this something Ghost users or developers need?

Please check your PR against these items:

  • I've read and followed the Contributor Guide
  • I've explained my change
  • I've written an automated test to prove my change works

We appreciate your contribution! 🙏

@cursor

cursor Bot commented Jul 4, 2026

Copy link
Copy Markdown

Bugbot is not enabled for this team, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@github-actions github-actions 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.

🌐 Automated translation review

Verdict:Looks good — no concerns flagged

Reviewed 189 translations across 3 files.

This is an excellent and thorough update to the Korean translations. The language is natural, consistent, and appropriately friendly throughout all three files. The use of 홍길동 as the placeholder name for "Jamie Larson" is a perfect choice — it's the quintessential Korean placeholder name, well-known and gender-neutral in usage. The email placeholder gildong@​example.com is a clever and consistent companion to that choice. Placeholders, inline tags, and ending punctuation all look correct. The informal-but-polite register (using ~요 endings) is used consistently and suits Ghost's brand voice well. 감사합니다!


Advisory review by i18n-review-bot. Non-blocking — a maintainer still owns the merge decision, and the bot cannot approve PRs on its own. Translator expertise wins where there is doubt.

@coderabbitai

coderabbitai Bot commented Jul 4, 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: faa14533-df4a-4092-92c9-d59fbafdb871

📥 Commits

Reviewing files that changed from the base of the PR and between 30df6a3 and af5c313.

📒 Files selected for processing (3)
  • ghost/i18n/locales/ko/comments.json
  • ghost/i18n/locales/ko/ghost.json
  • ghost/i18n/locales/ko/portal.json
✅ Files skipped from review due to trivial changes (2)
  • ghost/i18n/locales/ko/comments.json
  • ghost/i18n/locales/ko/ghost.json
🚧 Files skipped from review as they are similar to previous changes (1)
  • ghost/i18n/locales/ko/portal.json

Walkthrough

This pull request updates Korean locale strings in comments.json, ghost.json, and portal.json. It fills previously empty translations, adjusts some existing wording, and expands coverage for comment UI text, subscription and membership messaging, authentication and verification copy, notification templates, and portal error/access labels. The JSON key structure and exported entities are unchanged.

Possibly related PRs

  • TryGhost/Ghost#21959: Both PRs modify comment-related localization strings in ghost/i18n/locales/*/comments.json.

Suggested reviewers: cathysarisky

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: updated Korean translations.
Description check ✅ Passed The description is clearly related and matches the translation updates described in the diff.
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.
✨ 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.

@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.

🧹 Nitpick comments (1)
ghost/i18n/locales/ko/ghost.json (1)

52-52: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

Inconsistent particle form for dynamic {email} placeholder.

Line 52 uses a fixed "으로" ("{email}으로 전송되었어요.") while line 73 in the same file uses the parenthetical form "(으)로" ("{email}(으)로 전송되었어요.") for the same dynamic placeholder. Since the correct Korean particle depends on whether the substituted email string ends in a consonant or vowel sound, the fixed form can read as grammatically off for some dynamic values. Consider aligning with the "(으)로" pattern used elsewhere for consistency.

✏️ Suggested fix
-    "Sent to {email}": "{email}으로 전송되었어요.",
+    "Sent to {email}": "{email}(으)로 전송되었어요.",
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@ghost/i18n/locales/ko/ghost.json` at line 52, The Korean translation for the
Sent to {email} message uses a fixed particle form that is inconsistent with the
other localized string for the same placeholder. Update the entry in
ghost/i18n/locales/ko/ghost.json for the Sent to {email} translation to use the
same dynamic Korean particle pattern as the existing later translation, so the
grammar adapts correctly based on the {email} value; check the related
localization entry for the matching {email}(으)로 phrasing and align this string
accordingly.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@ghost/i18n/locales/ko/ghost.json`:
- Line 52: The Korean translation for the Sent to {email} message uses a fixed
particle form that is inconsistent with the other localized string for the same
placeholder. Update the entry in ghost/i18n/locales/ko/ghost.json for the Sent
to {email} translation to use the same dynamic Korean particle pattern as the
existing later translation, so the grammar adapts correctly based on the {email}
value; check the related localization entry for the matching {email}(으)로
phrasing and align this string accordingly.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 545db52c-a9a1-4cd5-bb45-7fa50cc5d8e5

📥 Commits

Reviewing files that changed from the base of the PR and between 3e36d12 and 280431a.

📒 Files selected for processing (3)
  • ghost/i18n/locales/ko/comments.json
  • ghost/i18n/locales/ko/ghost.json
  • ghost/i18n/locales/ko/portal.json

@cursor

cursor Bot commented Jul 4, 2026

Copy link
Copy Markdown

Bugbot is not enabled for this team, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@github-actions github-actions 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.

🌐 Automated translation review

Verdict:Looks good — no concerns flagged

Reviewed 190 translations across 3 files.

This is an excellent and thorough update to the Korean locale files. The translations are natural, consistent, and well-suited to Ghost's friendly, informal tone. The use of 홍길동 as the placeholder name for "Jamie Larson" is a great choice — it's the classic Korean placeholder name, analogous to "John Doe" in English. Placeholder variables, inline tags, and punctuation are all handled correctly throughout. 감사합니다!


Advisory review by i18n-review-bot. Non-blocking — a maintainer still owns the merge decision, and the bot cannot approve PRs on its own. Translator expertise wins where there is doubt.

ref TryGhost#23361

- Filled remaining untranslated strings and fixed a few existing ones
- Used 홍길동 for the "Jamie Larson" placeholder
@cursor

cursor Bot commented Jul 7, 2026

Copy link
Copy Markdown

Bugbot is not enabled for this team, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@github-actions github-actions 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.

🌐 Automated translation review

Verdict:Looks good — no concerns flagged

Reviewed 190 translations across 3 files.

This is a thorough and high-quality Korean translation. The strings are natural, consistent in tone (friendly informal 해요체 throughout), placeholders are all intact, inline tags are preserved, and the choice of 홍길동 as the placeholder name for "Jamie Larson" is excellent — it's the classic Korean everyman name. The example email placeholder gildong@​example.com is a nice touch too. No issues were found. 감사합니다!


Advisory review by i18n-review-bot. Non-blocking — a maintainer still owns the merge decision, and the bot cannot approve PRs on its own. Translator expertise wins where there is doubt.

@cursor

cursor Bot commented Jul 7, 2026

Copy link
Copy Markdown

Bugbot is not enabled for this team, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@github-actions github-actions 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.

🌐 Automated translation review

Verdict:Looks good — no concerns flagged

Reviewed 190 translations across 3 files.

This is a thorough and high-quality Korean translation update. The strings are accurate, natural-sounding, and consistent in tone throughout all three files. The use of 홍길동 as the placeholder name for "Jamie Larson" is an excellent choice — it's the quintessential Korean placeholder name, ungendered in usage, and widely recognised. The localised email placeholder (gildong@​example.com) is a nice touch too. Formality is consistent across the files, and all placeholders and inline tags appear to be intact. 감사합니다!


Advisory review by i18n-review-bot. Non-blocking — a maintainer still owns the merge decision, and the bot cannot approve PRs on its own. Translator expertise wins where there is doubt.

@nx-cloud

nx-cloud Bot commented Jul 7, 2026

Copy link
Copy Markdown

🤖 Nx Cloud AI Fix

Ensure the fix-ci command is configured to always run in your CI pipeline to get automatic fixes in future runs. For more information, please see https://nx.dev/ci/features/self-healing-ci


View your CI Pipeline Execution ↗ for commit 6d0d9bb

Command Status Duration Result
nx run @tryghost/admin-x-settings:test:acceptance ✅ Succeeded 10m 25s View ↗
nx run ghost:test:ci:integration ✅ Succeeded 2m 45s View ↗
nx run ghost:test:integration ✅ Succeeded 2m 51s View ↗
nx run-many --target=build --projects=tag:publi... ✅ Succeeded 1s View ↗
nx run ghost:test:legacy ✅ Succeeded 2m 54s View ↗
nx run ghost:test:e2e ✅ Succeeded 2m 28s View ↗
nx run-many -t test:unit -p @tryghost/admin-x-s... ✅ Succeeded 2m 47s View ↗
nx run-many -t lint -p @tryghost/i18n,@tryghost... ✅ Succeeded 1m 14s View ↗
Additional runs (5) ✅ Succeeded ... View ↗

💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗


☁️ Nx Cloud last updated this comment at 2026-07-07 21:03:36 UTC

@9larsons 9larsons enabled auto-merge (squash) July 7, 2026 20:52
@9larsons 9larsons merged commit 4a9d2a9 into TryGhost:main Jul 7, 2026
43 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants