github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 23:21:44 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #24557] issue:Bug: Korean (ko-KR) translation missing from v0.9.3+ builds #74934

New Issue
Open
opened 2026-05-13 07:48:16 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-05-13 07:48:16 -05:00
Owner
Copy Link

Originally created by @choseongho11 on GitHub (May 10, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24557

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.9.5

Ollama Version (if applicable)

No response

Operating System

ubuntu 24

Browser (if applicable)

No response

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

Subject: Bug: Korean (ko-KR) translation missing from v0.9.3+ builds

Bug Report

Description
Since v0.9.3, Korean (ko-KR) translation is completely missing from the build. The UI falls back to English even when Korean is selected in settings.

Steps to Reproduce

  1. Deploy Open WebUI v0.9.3 or later
  2. Set language to Korean (한국어) in Settings > General
  3. Save and refresh
  4. UI remains in English

Root Cause Investigation
We investigated the build files and found:

  • v0.9.2: Korean translation chunk exists (CMZxJWOC.js contains Korean strings)
  • v0.9.3+: Korean translation chunk is missing from the build

Verification command:

docker exec cnc_openwebui find /app/build -name "*.js" | xargs grep -l "ko-KR" 2>/dev/null
  • v0.9.2 result: Returns files containing Korean translations
  • v0.9.3+ result: No output (translation files missing)

Environment

  • Open WebUI v0.9.3, v0.9.4, v0.9.5 (all affected)
  • Docker deployment
  • PostgreSQL + pgvector backend

Expected Behavior
Korean translation should be available as in v0.9.2.

Current Workaround
Rolled back to v0.9.2 where Korean translation works correctly.

Please check if the Korean translation bundle was accidentally excluded from the build pipeline in v0.9.3+.

Thank you!

Actual Behavior

Subject: Bug: Korean (ko-KR) translation missing from v0.9.3+ builds

Bug Report

Description
Since v0.9.3, Korean (ko-KR) translation is completely missing from the build. The UI falls back to English even when Korean is selected in settings.

Steps to Reproduce

  1. Deploy Open WebUI v0.9.3 or later
  2. Set language to Korean (한국어) in Settings > General
  3. Save and refresh
  4. UI remains in English

Root Cause Investigation
We investigated the build files and found:

  • v0.9.2: Korean translation chunk exists (CMZxJWOC.js contains Korean strings)
  • v0.9.3+: Korean translation chunk is missing from the build

Verification command:

docker exec cnc_openwebui find /app/build -name "*.js" | xargs grep -l "ko-KR" 2>/dev/null
  • v0.9.2 result: Returns files containing Korean translations
  • v0.9.3+ result: No output (translation files missing)

Environment

  • Open WebUI v0.9.3, v0.9.4, v0.9.5 (all affected)
  • Docker deployment
  • PostgreSQL + pgvector backend

Expected Behavior
Korean translation should be available as in v0.9.2.

Current Workaround
Rolled back to v0.9.2 where Korean translation works correctly.

Please check if the Korean translation bundle was accidentally excluded from the build pipeline in v0.9.3+.

Thank you!

Steps to Reproduce

Subject: Bug: Korean (ko-KR) translation missing from v0.9.3+ builds

Bug Report

Description
Since v0.9.3, Korean (ko-KR) translation is completely missing from the build. The UI falls back to English even when Korean is selected in settings.

Steps to Reproduce

  1. Deploy Open WebUI v0.9.3 or later
  2. Set language to Korean (한국어) in Settings > General
  3. Save and refresh
  4. UI remains in English

Root Cause Investigation
We investigated the build files and found:

  • v0.9.2: Korean translation chunk exists (CMZxJWOC.js contains Korean strings)
  • v0.9.3+: Korean translation chunk is missing from the build

Verification command:

docker exec cnc_openwebui find /app/build -name "*.js" | xargs grep -l "ko-KR" 2>/dev/null
  • v0.9.2 result: Returns files containing Korean translations
  • v0.9.3+ result: No output (translation files missing)

Environment

  • Open WebUI v0.9.3, v0.9.4, v0.9.5 (all affected)
  • Docker deployment
  • PostgreSQL + pgvector backend

Expected Behavior
Korean translation should be available as in v0.9.2.

Current Workaround
Rolled back to v0.9.2 where Korean translation works correctly.

Please check if the Korean translation bundle was accidentally excluded from the build pipeline in v0.9.3+.

Thank you!

Logs & Screenshots

Subject: Bug: Korean (ko-KR) translation missing from v0.9.3+ builds

Bug Report

Description
Since v0.9.3, Korean (ko-KR) translation is completely missing from the build. The UI falls back to English even when Korean is selected in settings.

Steps to Reproduce

  1. Deploy Open WebUI v0.9.3 or later
  2. Set language to Korean (한국어) in Settings > General
  3. Save and refresh
  4. UI remains in English

Root Cause Investigation
We investigated the build files and found:

  • v0.9.2: Korean translation chunk exists (CMZxJWOC.js contains Korean strings)
  • v0.9.3+: Korean translation chunk is missing from the build

Verification command:

docker exec cnc_openwebui find /app/build -name "*.js" | xargs grep -l "ko-KR" 2>/dev/null
  • v0.9.2 result: Returns files containing Korean translations
  • v0.9.3+ result: No output (translation files missing)

Environment

  • Open WebUI v0.9.3, v0.9.4, v0.9.5 (all affected)
  • Docker deployment
  • PostgreSQL + pgvector backend

Expected Behavior
Korean translation should be available as in v0.9.2.

Current Workaround
Rolled back to v0.9.2 where Korean translation works correctly.

Please check if the Korean translation bundle was accidentally excluded from the build pipeline in v0.9.3+.

Thank you!

Additional Information

No response

Originally created by @choseongho11 on GitHub (May 10, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/24557 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.9.5 ### Ollama Version (if applicable) _No response_ ### Operating System ubuntu 24 ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior Subject: Bug: Korean (ko-KR) translation missing from v0.9.3+ builds **Bug Report** **Description** Since v0.9.3, Korean (ko-KR) translation is completely missing from the build. The UI falls back to English even when Korean is selected in settings. **Steps to Reproduce** 1. Deploy Open WebUI v0.9.3 or later 2. Set language to Korean (한국어) in Settings > General 3. Save and refresh 4. UI remains in English **Root Cause Investigation** We investigated the build files and found: - v0.9.2: Korean translation chunk exists (`CMZxJWOC.js` contains Korean strings) - v0.9.3+: Korean translation chunk is missing from the build Verification command: ```bash docker exec cnc_openwebui find /app/build -name "*.js" | xargs grep -l "ko-KR" 2>/dev/null ``` - v0.9.2 result: Returns files containing Korean translations - v0.9.3+ result: No output (translation files missing) **Environment** - Open WebUI v0.9.3, v0.9.4, v0.9.5 (all affected) - Docker deployment - PostgreSQL + pgvector backend **Expected Behavior** Korean translation should be available as in v0.9.2. **Current Workaround** Rolled back to v0.9.2 where Korean translation works correctly. Please check if the Korean translation bundle was accidentally excluded from the build pipeline in v0.9.3+. Thank you! ### Actual Behavior Subject: Bug: Korean (ko-KR) translation missing from v0.9.3+ builds **Bug Report** **Description** Since v0.9.3, Korean (ko-KR) translation is completely missing from the build. The UI falls back to English even when Korean is selected in settings. **Steps to Reproduce** 1. Deploy Open WebUI v0.9.3 or later 2. Set language to Korean (한국어) in Settings > General 3. Save and refresh 4. UI remains in English **Root Cause Investigation** We investigated the build files and found: - v0.9.2: Korean translation chunk exists (`CMZxJWOC.js` contains Korean strings) - v0.9.3+: Korean translation chunk is missing from the build Verification command: ```bash docker exec cnc_openwebui find /app/build -name "*.js" | xargs grep -l "ko-KR" 2>/dev/null ``` - v0.9.2 result: Returns files containing Korean translations - v0.9.3+ result: No output (translation files missing) **Environment** - Open WebUI v0.9.3, v0.9.4, v0.9.5 (all affected) - Docker deployment - PostgreSQL + pgvector backend **Expected Behavior** Korean translation should be available as in v0.9.2. **Current Workaround** Rolled back to v0.9.2 where Korean translation works correctly. Please check if the Korean translation bundle was accidentally excluded from the build pipeline in v0.9.3+. Thank you! ### Steps to Reproduce Subject: Bug: Korean (ko-KR) translation missing from v0.9.3+ builds **Bug Report** **Description** Since v0.9.3, Korean (ko-KR) translation is completely missing from the build. The UI falls back to English even when Korean is selected in settings. **Steps to Reproduce** 1. Deploy Open WebUI v0.9.3 or later 2. Set language to Korean (한국어) in Settings > General 3. Save and refresh 4. UI remains in English **Root Cause Investigation** We investigated the build files and found: - v0.9.2: Korean translation chunk exists (`CMZxJWOC.js` contains Korean strings) - v0.9.3+: Korean translation chunk is missing from the build Verification command: ```bash docker exec cnc_openwebui find /app/build -name "*.js" | xargs grep -l "ko-KR" 2>/dev/null ``` - v0.9.2 result: Returns files containing Korean translations - v0.9.3+ result: No output (translation files missing) **Environment** - Open WebUI v0.9.3, v0.9.4, v0.9.5 (all affected) - Docker deployment - PostgreSQL + pgvector backend **Expected Behavior** Korean translation should be available as in v0.9.2. **Current Workaround** Rolled back to v0.9.2 where Korean translation works correctly. Please check if the Korean translation bundle was accidentally excluded from the build pipeline in v0.9.3+. Thank you! ### Logs & Screenshots Subject: Bug: Korean (ko-KR) translation missing from v0.9.3+ builds **Bug Report** **Description** Since v0.9.3, Korean (ko-KR) translation is completely missing from the build. The UI falls back to English even when Korean is selected in settings. **Steps to Reproduce** 1. Deploy Open WebUI v0.9.3 or later 2. Set language to Korean (한국어) in Settings > General 3. Save and refresh 4. UI remains in English **Root Cause Investigation** We investigated the build files and found: - v0.9.2: Korean translation chunk exists (`CMZxJWOC.js` contains Korean strings) - v0.9.3+: Korean translation chunk is missing from the build Verification command: ```bash docker exec cnc_openwebui find /app/build -name "*.js" | xargs grep -l "ko-KR" 2>/dev/null ``` - v0.9.2 result: Returns files containing Korean translations - v0.9.3+ result: No output (translation files missing) **Environment** - Open WebUI v0.9.3, v0.9.4, v0.9.5 (all affected) - Docker deployment - PostgreSQL + pgvector backend **Expected Behavior** Korean translation should be available as in v0.9.2. **Current Workaround** Rolled back to v0.9.2 where Korean translation works correctly. Please check if the Korean translation bundle was accidentally excluded from the build pipeline in v0.9.3+. Thank you! ### Additional Information _No response_
GiteaMirror added the bug label 2026-05-13 07:48:16 -05:00
GiteaMirror commented 2026-05-13 07:48:18 -05:00
Author
Owner
Copy Link

@owui-terminator[bot] commented on GitHub (May 10, 2026):

⚠️ Missing Issue Title Prefix

@choseongho11, your issue title is missing a categorising prefix (e.g. bug:, feat:, docs:).

Please update the title to lead with one of:

  • bug: bug report or error
  • feat: feature request or enhancement
  • docs: documentation issue
  • question: usage question
  • help: support request

Example: bug: Login fails when the password contains special characters

<!-- gh-comment-id:4416670535 --> @owui-terminator[bot] commented on GitHub (May 10, 2026): # ⚠️ Missing Issue Title Prefix @choseongho11, your issue title is missing a categorising prefix (e.g. `bug:`, `feat:`, `docs:`). Please update the title to lead with one of: - **bug**: bug report or error - **feat**: feature request or enhancement - **docs**: documentation issue - **question**: usage question - **help**: support request Example: `bug: Login fails when the password contains special characters`
GiteaMirror commented 2026-05-13 07:48:18 -05:00
Author
Owner
Copy Link

@owui-terminator[bot] commented on GitHub (May 10, 2026):

⚠️ Invalid Issue Title

@choseongho11, your issue title is too short, too few words, or a generic placeholder — it doesn't tell maintainers what's actually being reported or requested.

Please update the title to be at least 10 characters and 2 words, and to describe the actual issue. Bare placeholders like bug, feat:, or issue make triage difficult and slow down everyone.

Example: bug: Login fails when password contains special characters

<!-- gh-comment-id:4416670558 --> @owui-terminator[bot] commented on GitHub (May 10, 2026): # ⚠️ Invalid Issue Title @choseongho11, your issue title is too short, too few words, or a generic placeholder — it doesn't tell maintainers what's actually being reported or requested. Please update the title to be **at least 10 characters and 2 words**, and to describe the actual issue. Bare placeholders like `bug`, `feat:`, or `issue` make triage difficult and slow down everyone. Example: `bug: Login fails when password contains special characters`
GiteaMirror commented 2026-05-13 07:48:19 -05:00
Author
Owner
Copy Link

@owui-terminator[bot] commented on GitHub (May 10, 2026):

🔍 Related Issues Found

I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions:

  1. 🟣 #1214 bug: i18n chinese not working
    This is the same class of problem: the UI stays in English even after selecting a non-English language. It is an older Chinese i18n issue, so it is relevant as a precedent for locale-specific translation failures.
    by jxyk2007

  2. 🟣 #22866 issue: Hardcoded lang="en" in HTML header triggers unwanted browser translation popups and breaks localization
    This issue is about localization breaking in the frontend due to language handling in the app. While the root cause is different, it is directly related to the broader i18n/localization path that affects Korean translation display.
    by dotmobo · bug

💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead.

This comment was generated automatically. React with 👍 if helpful, 👎 if not.

<!-- gh-comment-id:4416673422 --> @owui-terminator[bot] commented on GitHub (May 10, 2026): <!-- terminator-bot:related-issues-reply --> 🔍 **Related Issues Found** I found some existing issues that might be related. Please check if any of these are duplicates or contain helpful solutions: 1. 🟣 [#1214](https://github.com/open-webui/open-webui/issues/1214) **bug: i18n chinese not working** *This is the same class of problem: the UI stays in English even after selecting a non-English language. It is an older Chinese i18n issue, so it is relevant as a precedent for locale-specific translation failures.* *by jxyk2007* 2. 🟣 [#22866](https://github.com/open-webui/open-webui/issues/22866) **issue: Hardcoded `lang="en"` in HTML header triggers unwanted browser translation popups and breaks localization** *This issue is about localization breaking in the frontend due to language handling in the app. While the root cause is different, it is directly related to the broader i18n/localization path that affects Korean translation display.* *by dotmobo · `bug`* --- 💡 If your issue is a duplicate, please close it and add any additional details to the existing issue instead. *This comment was generated automatically.* React with 👍 if helpful, 👎 if not.
GiteaMirror commented 2026-05-13 07:48:19 -05:00
Author
Owner
Copy Link

@Cyp9715 commented on GitHub (May 11, 2026):

The same issue happens on Windows 11 too. (OpenWebUI Desktop)

<!-- gh-comment-id:4416805034 --> @Cyp9715 commented on GitHub (May 11, 2026): The same issue happens on Windows 11 too. (OpenWebUI Desktop)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#74934
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?