Skip to content

i18n(ko): automated Crowdin translation import (part 01 of 13)#17391

Closed
minimalsm wants to merge 2 commits into
devfrom
i18n/import/2026-01-25T17-44-07-ko-part-01
Closed

i18n(ko): automated Crowdin translation import (part 01 of 13)#17391
minimalsm wants to merge 2 commits into
devfrom
i18n/import/2026-01-25T17-44-07-ko-part-01

Conversation

@minimalsm
Copy link
Copy Markdown
Contributor

Summary

Context

Split from the original large import PR for easier review and independent merging.

@github-actions github-actions Bot added content 🖋️ This involves copy additions or edits tooling 🔧 Changes related to tooling of the project translation 🌍 This is related to our Translation Program labels Feb 14, 2026
@netlify
Copy link
Copy Markdown

netlify Bot commented Feb 14, 2026

Deploy Preview for ethereumorg ready!

Name Link
🔨 Latest commit 74503be
🔍 Latest deploy log https://app.netlify.com/projects/ethereumorg/deploys/6992fd74da82b90008b18424
😎 Deploy Preview https://deploy-preview-17391.ethereum.it
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
7 paths audited
Performance: 58 (🟢 up 3 from production)
Accessibility: 94 (no change from production)
Best Practices: 100 (no change from production)
SEO: 100 (no change from production)
PWA: 59 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@minimalsm
Copy link
Copy Markdown
Contributor Author

Translation Quality Review

Language: Korean (ko)
Files Reviewed: 25 files
Overall Quality Score: 98/100

Quality by Category

Category Score Notes
Brand Names 100/100 ✅ All brand names correctly kept in English (Arbitrum, Aave, Polygon, Discord, GitHub, Figma, YouTube, etc.)
Code Blocks 100/100 ✅ No code translated inside fences
Markdown Syntax 95/100 ✅ Well-formed markdown throughout
Frontmatter 100/100 ✅ All frontmatter properly structured
Terminology 100/100 ✅ Technical terms properly handled
Grammar & Flow 95/100 ✅ Natural Korean phrasing, appropriate formality

Issues Found & Fixed

Fixed (2 issues):

  1. Duplicate word error in public/content/translations/ko/about/index.md:11

    • Before: ethereum.orgethereum.org의 누구도
    • After: ethereum.org의 누구도
  2. Missing space in public/content/translations/ko/about/index.md:114

    • Before: 참여하고 싶으신가요?[Figma에서
    • After: 참여하고 싶으신가요? [Figma에서 (space added after question mark)

Summary

This is a high-quality Korean translation batch. All 25 files demonstrate:

  • ✅ Consistent terminology usage
  • ✅ Proper preservation of English brand names
  • ✅ Clean markdown structure
  • ✅ Natural Korean flow and appropriate formality level
  • ✅ Accurate technical concept translations

The two minor issues found have been corrected and pushed to the branch. The translations are ready for merge.

Commit: fix(i18n): correct duplicate word and spacing in Korean translations

@github-actions
Copy link
Copy Markdown
Contributor

This issue is stale because it has been open 30 days with no activity.

@github-actions github-actions Bot added the Status: Stale This issue is stale because it has been open 30 days with no activity. label Mar 19, 2026
@wackerow wackerow added the duplicate 🐥🐥 This issue or pull request already exists label Mar 24, 2026
@wackerow
Copy link
Copy Markdown
Member

@wackerow wackerow closed this Mar 24, 2026
@github-actions github-actions Bot added the abandoned This has been abandoned or will not be implemented label Mar 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

abandoned This has been abandoned or will not be implemented content 🖋️ This involves copy additions or edits duplicate 🐥🐥 This issue or pull request already exists Status: Stale This issue is stale because it has been open 30 days with no activity. tooling 🔧 Changes related to tooling of the project translation 🌍 This is related to our Translation Program

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants