[GH-ISSUE #5659] [feature]: Inconsistent Product Name Translation in Korean Locale (ko.json) #2192

Closed
opened 2026-03-16 23:32:12 +03:00 by kerem · 1 comment
Owner

Originally created by @g-yunjh on GitHub (Dec 4, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5659

Originally assigned to: @g-yunjh on GitHub.

Is there an existing issue for this?

  • I have searched the existing issues

Summary

Description

The Korean translation file (packages/hoppscotch-common/locales/ko.json) translates "Hoppscotch" to "호프스카치" (phonetic Korean) throughout the file. This creates several issues:

  1. Inconsistency with other Asian locales: Japanese (ja.json) and Chinese (cn.json) both keep the product name as "Hoppscotch" in English, while Korean is the only Asian language that translates it phonetically.

  2. Awkward for native speakers: As a native Korean speaker, seeing "호프스카치" feels forced and unnatural. Product names, especially for technical tools, are typically kept in their original English form in Korean tech documentation.

  3. Internal inconsistency: The file uses two different phonetic translations:

    • "호프스카치" (hopseukachi)
    • "홉스카치" (hobseukachi)

    This inconsistency makes the translation look unprofessional.

Current Example

{
  "name": "호프스카치",
  // ... other instances throughout the file
}

Proposed Solution

Change all instances of "호프스카치" and "홉스카치" to "Hoppscotch" to:

  • Match the approach used in other Asian locales
  • Provide a more natural reading experience for Korean users
  • Maintain consistency throughout the file
  • Follow common Korean tech localization practices

Next Steps

I'm preparing a PR to address this issue by replacing all phonetic translations of the product name with "Hoppscotch".

Why should this be worked on?

  • User Experience: The phonetic translation ("호프스카치") feels unnatural to native Korean speakers and appears unprofessional
  • Consistency: Japanese and Chinese locales keep "Hoppscotch" in English - Korean should follow the same approach
  • Internal Issues: Two different phonetic spellings are used inconsistently throughout the file
  • Best Practice: Korean tech localization typically keeps product/brand names in English (following standards set by Google, Microsoft, etc.)
  • Low Effort: Simple find-and-replace fix with immediate UX improvement
Originally created by @g-yunjh on GitHub (Dec 4, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5659 Originally assigned to: @g-yunjh on GitHub. ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary ### **Description** The Korean translation file (`packages/hoppscotch-common/locales/ko.json`) translates "Hoppscotch" to "호프스카치" (phonetic Korean) throughout the file. This creates several issues: 1. **Inconsistency with other Asian locales**: Japanese (`ja.json`) and Chinese (`cn.json`) both keep the product name as "Hoppscotch" in English, while Korean is the only Asian language that translates it phonetically. 2. **Awkward for native speakers**: As a native Korean speaker, seeing "호프스카치" feels forced and unnatural. Product names, especially for technical tools, are typically kept in their original English form in Korean tech documentation. 3. **Internal inconsistency**: The file uses two different phonetic translations: - "호프스카치" (hopseukachi) - "홉스카치" (hobseukachi) This inconsistency makes the translation look unprofessional. ### **Current Example** ```json { "name": "호프스카치", // ... other instances throughout the file } ``` ### **Proposed Solution** Change all instances of "호프스카치" and "홉스카치" to "Hoppscotch" to: - Match the approach used in other Asian locales - Provide a more natural reading experience for Korean users - Maintain consistency throughout the file - Follow common Korean tech localization practices ### **Next Steps** I'm preparing a PR to address this issue by replacing all phonetic translations of the product name with "Hoppscotch". ### Why should this be worked on? - **User Experience**: The phonetic translation ("호프스카치") feels unnatural to native Korean speakers and appears unprofessional - **Consistency**: Japanese and Chinese locales keep "Hoppscotch" in English - Korean should follow the same approach - **Internal Issues**: Two different phonetic spellings are used inconsistently throughout the file - **Best Practice**: Korean tech localization typically keeps product/brand names in English (following standards set by Google, Microsoft, etc.) - **Low Effort**: Simple find-and-replace fix with immediate UX improvement
kerem 2026-03-16 23:32:12 +03:00
  • closed this issue
  • added the
    feature
    label
Author
Owner

@jamesgeorge007 commented on GitHub (Dec 22, 2025):

This is now addressed in the v2025.12.0 release.

<!-- gh-comment-id:3681592755 --> @jamesgeorge007 commented on GitHub (Dec 22, 2025): This is now addressed in the [v2025.12.0](https://github.com/hoppscotch/hoppscotch/releases/tag/2025.12.0) release.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#2192
No description provided.