Title: Korean (ko) docs: native-speaker review notes for glossary.json and instructions.md · Issue #3732 · modelcontextprotocol/python-sdk · GitHub
Open Graph Title: Korean (ko) docs: native-speaker review notes for glossary.json and instructions.md · Issue #3732 · modelcontextprotocol/python-sdk
X Title: Korean (ko) docs: native-speaker review notes for glossary.json and instructions.md · Issue #3732 · modelcontextprotocol/python-sdk
Description: Every term in i18n/ko/glossary.json is marked "provisional pending native review", and #3280 mentions that only Portuguese had a reviewer lined up. I'm a native Korean speaker and compared the generated Korean pages with the English sour...
Open Graph Description: Every term in i18n/ko/glossary.json is marked "provisional pending native review", and #3280 mentions that only Portuguese had a reviewer lined up. I'm a native Korean speaker and compared the gene...
X Description: Every term in i18n/ko/glossary.json is marked "provisional pending native review", and #3280 mentions that only Portuguese had a reviewer lined up. I'm a native Korean speaker and com...
Opengraph URL: https://github.com/modelcontextprotocol/python-sdk/issues/3732
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Korean (ko) docs: native-speaker review notes for glossary.json and instructions.md","articleBody":"Every term in `i18n/ko/glossary.json` is marked \"provisional pending native review\", and #3280 mentions that only Portuguese had a reviewer lined up. I'm a native Korean speaker and compared the generated Korean pages with the English source. Below are only the problems that come from the inputs (`glossary.json` / `instructions.md`), not one-off sentences. Paths are under `i18n/ko/pages/`, and line numbers refer to those Korean files on `main` at 2af9e30.\n\nAI disclosure: I used Claude Code to compare 45 of the 52 Korean pages with the English source and collect examples. I read and confirmed every example below myself, and the proposed renderings are my choices. `advanced/` was not reviewed.\n\n### 1. `capability` → 기능 collides with \"feature\"\n\nThe glossary note already anticipated this collision; the pages confirm it.\n\n- `handlers/dependencies.md:148` \"선언되지 않은 기능은 …\" (*capability*) and `:150` \"독립적인 샘플링 및 루트 **기능**은\" (*features*): two lines apart, and the English contrast is lost.\n- `client/callbacks.md:73` `## A callback is a capability` → `## 콜백이 곧 기능`, which reads as \"a callback is a feature\".\n- `whats-new.md:192`: the English italicizes *capabilities* to separate them from features, but the next paragraph uses 기능 for features too.\n\nProposal: render *capability* (what a side declares it supports) as **지원 기능**, and keep 기능 for *feature*. Example: `## 콜백 등록이 곧 지원 기능 선언`.\n\n### 2. `era` has no entry, and \"2025년대\" is wrong\n\n- `handlers/sampling-and-roots.md:41` \"On 2025-era connections\" → \"2025년대 연결에서\". -년대 means a decade (as in 2020년대), so \"2025년대\" / \"2026년대\" is not a valid expression. It occurs 4 times (also `servers/media.md:123`, `client/session-groups.md:72`).\n- Elsewhere the same word is 시대 (`protocol-versions.md`), 세대 (`handlers/multi-round-trip.md`) or 시절 (`deprecated.md`).\n\nAn era is a group of protocol revisions, not a period of time, so any time word misleads in Korean. Proposal: no noun for era; name the versions instead.\n\n- 2025-era → `2025-11-25` 이하 버전\n- 2026-era → `2026-07-28`\n- pre-2026 → `2026-07-28` 이전 버전\n- a generic \"protocol era\" → 프로토콜 버전\n- never -년대, -년, 시대, 시절 or 세대\n\n### 3. Revision strings read as calendar dates\n\n- \"deprecated at `2026-07-28`\" became \"`2026-07-28`에서 지원 중단 예정\" (`handlers/sampling-and-roots.md:49`, `handlers/dependencies.md:150`). This reads as \"support ends on July 28, 2026\", while the English means \"deprecated as of the 2026-07-28 revision\".\n- The term is also shortened to 지원 중단 (\"호출하면 지원 중단 경고가 발생합니다\", `handlers/sampling-and-roots.md:43`), which reads as \"already unsupported\".\n\nProposal:\n\n- In `instructions.md` §4, when a revision string is the point in time, write 사양부터: \"`2026-07-28` 사양부터 지원 중단 예정입니다\".\n- In the `deprecated` note, say that \"deprecation warning\" is 지원 중단 예정 경고 and that the term is never shortened.\n\n### 4. `elicitation` → 엘리시테이션 is opaque\n\nThe glossary calls this the least settled term. The transliteration carries no meaning for Korean readers, and the candidate 유도 reads as \"nudging the user\".\n\nProposal: **사용자 입력 요청**, written 사용자 입력 요청(elicitation) at first mention.\n\n- form elicitation → 폼 입력 요청\n- URL-mode elicitation → URL 모드 입력 요청\n- push elicitation → 푸시 입력 요청\n- code such as `ctx.elicit()` and `elicitation/create` stays as is\n\n### 5. Terms with no entry, rendered differently across pages\n\nCounts are approximate (grep over `i18n/ko/pages`).\n\n| English | Renderings found | Proposal |\n|---|---|---|\n| argument | 인자 (94) / 인수 (48) | 인자 |\n| annotation | 어노테이션 (38) / 애너테이션 (5) | 어노테이션 |\n| docstring | 독스트링 / \"docstring\" left in Latin (`servers/prompts.md`) | 독스트링 |\n| parameter | 매개변수 / 파라미터 (`handlers/elicitation.md`) | 매개변수 |\n| spec | 사양 (45) / 명세 (8) | 사양 |\n| server-initiated request | 서버 시작 요청 / 서버가 시작하는 요청 / 서버 주도 | 서버가 시작하는 요청 (\"서버 시작 요청\" reads as \"a request to start the server\") |\n| provider (OAuth, identity) | 프로바이더 (20) / 공급자 (16) / 아이덴티티 공급자 | keep \"provider\" in Latin script |\n| completion (an LLM's output) | 완성, 완성 결과, 컴플리션 | keep \"completion\" in Latin script |\n| Completions (the primitive) | 자동 완성 / 완성 (`servers/index.md:21`) | 자동 완성 |\n\nThe argument, parameter, annotation and docstring proposals follow the Python documentation's own Korean glossary (https://docs.python.org/ko/3/glossary.html).\n\n\"wire\" (와이어 ×35, 전송 구간, 통신) needs a rule by context rather than one word:\n\n- on / across the wire → 실제로 주고받는 메시지에서\n- wire name, key or format → 프로토콜상 이름 / 키 / 형식\n- the wire as the channel (stdout under stdio) → 통신 채널\n- the verb \"wire\" → 연결하다 (already right)\n- never 와이어\n\n### 6. Gaps in `instructions.md`\n\n- **Requirement strength.** There is no mapping, and \"should not\" came out at must-not strength (\"-해서는 안 됩니다\", \"-면 안 되는지\", \"-지 않아야 합니다\") in `deprecated.md:155`, `client/identity-assertion.md:119` and `handlers/sampling-and-roots.md:13`. Proposal: must → -해야 합니다, should → -하는 것이 좋습니다, should not → -하지 않는 것이 좋습니다, may → -할 수 있습니다.\n- **Headings.** §1 bans -나요? / -습니까? headings, but other sentence endings appear: \"루트: 어디에 두어야 할까\" (`handlers/sampling-and-roots.md:28`), \"## 무엇을 발생시킬 것인가\" (`servers/handling-errors.md:78`), \"## 원할 때까지는 비용이 들지 않습니다\" (`run/opentelemetry.md:38`). Proposal: say that a heading never ends in a verb ending.\n- **-ㅂ시다.** It appears 3 times in `servers/handling-errors.md` (e.g. \"바꿔 봅시다.\"). §1 could list it next to -십시오.\n\nIf this is useful and you assign me, I can open a PR with the `glossary.json` / `instructions.md` changes. I also have a list of one-off mistranslations (e.g. \"crash\" → 충돌 in `client/index.md:142`) that I can file separately.\n","author":{"url":"https://github.com/Jeonghyeock","@type":"Person","name":"Jeonghyeock"},"datePublished":"2026-10-21T02:30:42Z","url":"https://github.com/modelcontextprotocol/python-sdk/issues/3732"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:a1aff652-1132-682a-45be-d8a03258ebe0 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | D23A:16EED3:3C8C44:4E8FDC:6B00D3F5 |
| html-safe-nonce | d34517a65689bfaa8932a55591f50f421e5788092365be055c24ec1140b31b4f |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJEMjNBOjE2RUVEMzozQzhDNDQ6NEU4RkRDOjZCMDBEM0Y1IiwidmlzaXRvcl9pZCI6IjYyNTIyODY0NDk4MTE1MTAyNjEiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | a060571ae55cd964481f38cb640c3bfb7dfcca0d4f6ef4682e4583a60ef2cf8c |
| hovercard-subject-tag | issue:5953193236 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/modelcontextprotocol/python-sdk/3732/issue_layout |
| twitter:image | https://opengraph.githubassets.com/5f8e682034ee9f33f33527e50380bc0b7e25248f837da5808fc3bdd0f70db440/modelcontextprotocol/python-sdk/issues/3732 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/5f8e682034ee9f33f33527e50380bc0b7e25248f837da5808fc3bdd0f70db440/modelcontextprotocol/python-sdk/issues/3732 |
| og:image:alt | Every term in i18n/ko/glossary.json is marked "provisional pending native review", and #3280 mentions that only Portuguese had a reviewer lined up. I'm a native Korean speaker and compared the gene... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | Jeonghyeock |
| hostname | github.com |
| expected-hostname | github.com |
| None | a481f62a1e04c9b9bdcb5628230682c66d59006f5b13b080f79cba84a176905b |
| turbo-cache-control | no-preview |
| go-import | github.com/modelcontextprotocol/python-sdk git https://github.com/modelcontextprotocol/python-sdk.git |
| octolytics-dimension-user_id | 182288589 |
| octolytics-dimension-user_login | modelcontextprotocol |
| octolytics-dimension-repository_id | 862584018 |
| octolytics-dimension-repository_nwo | modelcontextprotocol/python-sdk |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 862584018 |
| octolytics-dimension-repository_network_root_nwo | modelcontextprotocol/python-sdk |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 84c8c5cc25e2fb7f2308428458538436baecc6d2 |
| ui-target | canary-2 |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width