Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:
Target branch: Please verify that the pull request targets the dev branch.
Description: See below
Changelog: Yes
Code review: I did a self-review based on other existing keys in the same file.
Prefix: yes, used i18n
Changelog Entry
Description
In the Korean translation file, I noticed that the word "끔찍함", used to represent the lower bound of a rating scale (opposite of "fantastic"), felt overly emotional and somewhat informal for the context in which it's being used.
To improve clarity and maintain a more neutral and professional tone, I replaced "끔찍함" with "형편없음", which still conveys a strong negative sentiment but in a more appropriate and formal manner.
This small adjustment helps ensure consistency in tone across the UI and aligns better with other descriptors used in the same file. No functional changes were made, only the label string was updated.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/open-webui/open-webui/pull/12981
**Author:** [@knight-upstage](https://github.com/knight-upstage)
**Created:** 4/17/2025
**Status:** ✅ Merged
**Merged:** 4/17/2025
**Merged by:** [@tjbck](https://github.com/tjbck)
**Base:** `dev` ← **Head:** `dev`
---
### 📝 Commits (1)
- [`cdf26d8`](https://github.com/open-webui/open-webui/commit/cdf26d8189b8e720f75eb1bd772bae8fc9ae83ce) i18n: Update ko-KR (Korean) translation.json
### 📊 Changes
**1 file changed** (+1 additions, -1 deletions)
<details>
<summary>View changed files</summary>
📝 `src/lib/i18n/locales/ko-KR/translation.json` (+1 -1)
</details>
### 📄 Description
# Pull Request Checklist
### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request.
**Before submitting, make sure you've checked the following:**
- [x] **Target branch:** Please verify that the pull request targets the `dev` branch.
- [x] **Description:** See below
- [x] **Changelog:** Yes
- [x] **Code review:** I did a self-review based on other existing keys in the same file.
- [x] **Prefix:** yes, used i18n
# Changelog Entry
### Description
In the Korean translation file, I noticed that the word "끔찍함", used to represent the lower bound of a rating scale (opposite of "fantastic"), felt overly emotional and somewhat informal for the context in which it's being used.
To improve clarity and maintain a more neutral and professional tone, I replaced "끔찍함" with "형편없음", which still conveys a strong negative sentiment but in a more appropriate and formal manner.
This small adjustment helps ensure consistency in tone across the UI and aligns better with other descriptors used in the same file. No functional changes were made, only the label string was updated.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/open-webui/open-webui/pull/12981
Author: @knight-upstage
Created: 4/17/2025
Status: ✅ Merged
Merged: 4/17/2025
Merged by: @tjbck
Base:
dev← Head:dev📝 Commits (1)
cdf26d8i18n: Update ko-KR (Korean) translation.json📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
src/lib/i18n/locales/ko-KR/translation.json(+1 -1)📄 Description
Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:
devbranch.Changelog Entry
Description
In the Korean translation file, I noticed that the word "끔찍함", used to represent the lower bound of a rating scale (opposite of "fantastic"), felt overly emotional and somewhat informal for the context in which it's being used.
To improve clarity and maintain a more neutral and professional tone, I replaced "끔찍함" with "형편없음", which still conveys a strong negative sentiment but in a more appropriate and formal manner.
This small adjustment helps ensure consistency in tone across the UI and aligns better with other descriptors used in the same file. No functional changes were made, only the label string was updated.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.