Skip to content

[Feature]: Add comprehensive Korean localization support #1029

Open

Description

@nanpuhaha

Problem

Currently, LoopForge only officially supports Chinese (zh) and English (en). Korean-speaking developers face language barriers when using the platform, management dashboards, and the chat workbench.

Proposed behavior

Provide complete, out-of-the-box Korean (ko) localization support:

  1. Add a comprehensive domain-specific Korean translation dictionary (web/i18n-ko.js) covering both management pages and the chat workbench (13,000+ entries).
  2. Extend the runtime translation engine (web/i18n.js, web/boot.js) to handle the ko locale, date/number formatting, and unit patterns.
  3. Inject i18n scripts into the native chat workbench bundle (chatbot/index.html) so the chat workspace renders in Korean seamlessly.
  4. Support 3-way language cycling (zh -> en -> ko) in the top navigation bar and login interface.
  5. Register web/i18n-ko.js in embedded static assets (web/embed.go).

Scope

Platform — UI / integrations

Alternatives considered

Relying on browser built-in machine translation, but domain-specific terms (SOP, Runner, Sandbox, Artifacts, etc.) are frequently mistranslated and inconsistent.

Checks

  • This proposal does not require organization-specific infrastructure or credentials.
  • I searched existing issues and discussions for similar proposals.

Activity

  1. cocofhu00 commented on Nov 18, 2026

    @cocofhu00
    Contributor

    Thanks for the proposal! As I understand it, LoopForge officially supports only Chinese and English today, and you would like full Korean (ko) localization: a domain dictionary for the management pages and chat workbench, runtime locale handling, the native chat bundle, a zh → en → ko language switch, and registering that dictionary in the embedded static assets.

    We've seen this and will look at it in the existing issue queue.

  2. added 3 commits that reference this issue on Nov 18, 2026
    bacfce0
    c52cbf8
    6af9dae
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions