feat(i18n): add Korean (ko) interface locale #8290

Read This First

• Docs: https://docs.newapi.ai/
• Usage questions first: https://deepwiki.com/QuantumNous/new-api
• Do not report issues when pass-through is enabled; pass-through sends content as-is and does not go through new-api processing logic.
• State facts and evidence concisely. Do not paste unfiltered AI-generated text in the issue body or in later comments.
• Reports about Coding Plan services, reverse-engineered channels, third-party API wrappers, or compatibility issues caused by exposing a Codex endpoint through a reverse proxy as a general-purpose API are not accepted. Protocols or behavior specific to the Codex API should not be treated as standard OpenAI API behavior; confirm such issues with the channel or API provider first.
• This project does not provide official hosting and does not support third-party hosting sites, relays, or API services; contact their operator instead.
• Warning: issues with this template removed, section headings deleted, or content cleared may be closed directly. Repeated submissions of unfiltered AI-generated text, or repeated abusive submissions, may result in a block.

Your current newapi version

v1.0.0-rc.49 (image calciumion/new-api:latest, the console reports New API v1.0.0-rc.49 on startup)

Submission Checks

• Non-duplicate issue: I have searched existing Issues and confirmed there are no similar issues.
• Read this first: I have fully read the section above, reviewed the docs at https://docs.newapi.ai/ and the project README, and asked AI first, confirming this is not a usage, configuration, or integration question, and that the current version cannot meet my needs.
• Supported version: I have provided an exact version, commit, or image tag (not latest or unknown) and confirm this feature request is for an unmodified, supported version from this repository.
• Not a third-party service: I confirm that this request is not exclusive to a third-party hosting site, relay, API service, or fork that has not been verified against the unmodified repository. Third-party instance issues must be reported to their operator.
• Not pass-through: I confirm this is not a forwarding report after enabling pass-through; pass-through sends content as-is and does not go through new-api processing logic.
• Channel and protocol boundary: I confirm this is not a feature request for a Coding Plan service, reverse-engineered channel, third-party API wrapper, Codex reverse-proxy endpoint, or treating Codex API-specific behavior as standard OpenAI API behavior. If first observed through such an interface, I have based the request on a standard API protocol supported by this repository.
• Template intact: I have not removed any guidance or section headings from this template and will complete it as requested.
• Maintainer time: I understand that maintainers have limited time. Do not paste unfiltered AI-generated text in the issue body or in later comments; extract the points needed for review first. Submissions that do not follow this template, or that omit the necessary points and cannot be reviewed, may be ignored or closed. Repeated submissions of this kind may result in a block.

Feature Description

Korean is not offered as an interface language. The console ships seven
(zhCN, en, fr, ru, ja, vi, zhTW), and there is no ko.json under
web/src/i18n/locales/, so a Korean browser falls back to English.

Adding it needs three things:

1. web/src/i18n/locales/ko.json with the same key set as en.json.
2. ko in resources / supportedLngs (web/src/i18n/config.ts) and in
   INTERFACE_LANGUAGE_OPTIONS (web/src/i18n/languages.ts).
3. A tag mapping in convertDetectedLanguage: with load: 'currentOnly' a ko-KR browser is
   not expanded to ko, so Korean users would still get English without it.

Two Korean proposals are already open — #3363 (2026-03) and #6304 (2026-07) — and neither is
merged. #6304 has machine-review notes about translation quality: time units rendered as
1H/1M, provider names translated literally, disabled rendered as 장애인, Completion price as 준공가격, Passkey treated as password login. Those are the points I made sure to get
right in #8289; if you would rather push that one over the line instead, that works for me too.

Use Case

Self-hosted deployments run by Korean-speaking teams have to operate the console in English
today, and there is no supported way to add a locale without patching the resource map.

#8289 has the prepared change: a complete ko.json (7,403 keys, sync-i18n reports 0 missing
/ 0 extra / 0 untranslated), the two registry entries, and a unit test for the tag mapping. No
other locale is touched.