feat(i18n): add missing keys to Korean translation#4788
Open
moduvoice wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
This adds Korean (
ko) translation support — to help Korean-speaking users use thisopen-source project more comfortably in their own language.
(한국 사람들의 오픈소스 이용에 도움이 되게 하기 위해서 한글화 작업을 하였습니다.)
Changes
apps/dokploy/public/locales/ko/settings.json, which was missing 13 keys (39/52) compared toen:settings.common.enterTerminalsettings.server.webServer.traefik.managePorts,.managePortsDescription,.targetPort,.publishedPort,.addPort,.portsUpdated,.portsUpdateError,.publishModesettings.terminal.connectionSettings,.ipAddress,.port,.usernameapps/dokploy/public/locales/ko/common.jsonhas no gap versusen(both are empty{}).Testing
envskoacross bothcommon.jsonandsettings.json; confirmedkonow matchesenkey-for-key (52/52 insettings.json, 0/0 incommon.json) with no missing and no extra keys.{{var}}) in both files — none exist, so no placeholder-preservation issues apply here.npx @biomejs/biome checkon the changed file — no formatting/lint issues.