Chinese i Simplified,Koreana Hoʻololi
ZH KO
Nā hualoaʻa
API i loaʻa
E hoʻohuli ana...
E hōʻike ana ka unuhi i kēia wahi...
Hoʻopaʻa inoa e hoʻohuli i nā faila
E hana i kahi moʻokāki manuahi e hoʻololi i nā palapala, nā hua'ōlelo, a me nā mea hou aku.
E hoʻopaʻa inoa HoʻokomoPehea e hoʻololi ai i Chinese i Korean
1
E hoʻokomo i kāu hua'ōlelo
E kākau a i ʻole kāpae i kāu hua'ōlelo Chinese i loko o ka pākuʻi hoʻokomo ma luna. Hiki iā ʻoe ke komo i ka nui o 10,000 mau hua'ōlelo, a i ʻole e hoʻouka i kahi faila doc.
2
Kaomi e Hoʻohuli
E kaomi i ka pihi Hoʻololi a i ʻole e kali wale - hoʻomaka ka hoʻololi ʻana i ka mīkini ma hope o kou pau ʻana i ka kākau ʻana. Hoʻokō ʻo AI i kāu huaʻōlelo i nā milliseconds.
3
Hoʻololi i kāu hua'ōlelo
E hōʻike koke ana kāu hoʻololi Korean. E kaomi i ka pihi kope e kope iā ia i kāu papa hoʻoili, a i ʻole e hoʻohui ma o kā mākou API.
Nā hua'ōlelo maʻamau Chinese
Kaomi i kekahi hua'ōlelo e hoʻohuli iā ia i ka manawa like.
Hoʻololi i ka hua'ōlelo
E kiʻi i nā hoʻololi mai Chinese i Korean i nā milliseconds.
Ke kākoʻo o ka palapala
Hoʻouka i ka Word, PDF, SRT subtitles a me nā mea hou aʻe no ka hoʻololi pū ʻana.
Hoʻohana API
Hoʻohui i kēia ʻelua hoʻololi i kāu mau noi me kā mākou REST API.
Chinese i Korean API
E hoʻohui i kēia ʻelua hoʻololi i kāu noi me kahi kelepona API maʻalahi.
Hōʻike i nā palapala API E kiʻi i ke kī APIcurl -X POST https://api.translateapi.ai/api/v1/translate/ \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text": "Hello", "source_language": "zh", "target_language": "ko"}'E pili ana i ka hoʻololi Chinese i Korean
TranslateAPI hāʻawi i ka wikiwiki a pololei hoʻi Chinese i Korean ka hoʻololi ʻana i ka AI kiʻekiʻe.
- Hoʻololi i ka hua'ōlelo - Hoʻololi i kekahi huaʻōlelo i ka 10,000 mau huaʻōlelo i ka manawa like
- Hoʻololi i ka palapala - Hoʻouka i nā faila Word, PDF, a me nā hua'ōlelo no ka hoʻololi
- Hoʻohui API - E hoʻohui i ka hoʻololi Chinese i Korean i kāu mau noi
- Hoʻololi - Hoʻololi i nā hua'ōlelo he nui i loko o kahi noi wale nō
Hoʻohana i nā hihia:
- Hoʻololi i nā palapala Chinese i Korean no ka hana
- Hoʻololi i nā pūnaewele a me nā noi mai Chinese i Korean
- Hoʻololi i nā mea kākau o Chinese i Korean
- E kamaʻilio me nā kaikamahine Korean
Pākuʻi
- Kahua
- Chinese, Simplified (
zh) - Hoʻohālike
- Koreana (
ko)
Nā nīnau i nīnau pinepine ʻia
CJK ↔ CJK translation (Chinese ↔ Japanese ↔ Korean) is one of the strongest areas in modern neural machine translation because the three languages share a large vocabulary of Sino-loanwords. Expect 92-95% professional-grade accuracy for Chinese to Korean, with the largest residual errors in idiomatic or culturally-specific phrasing.
Yes — Japanese kango (Sino-Japanese), Korean Hanja-origin words, and Chinese hanzi often share a written form. The model exploits this by aligning Sino-loanwords across the pair, which is why CJK ↔ CJK quality often beats CJK ↔ English on technical content.
Output script follows the standard convention for the target: simplified Chinese for zh (use zh-TW for traditional), modern Japanese mixed-script for ja, pure Hangul for ko (Hanja is added only when context requires it). Override via the explicit target code if you need a different convention.
Ateji (kanji used phonetically rather than for meaning) are translated to the closest semantic equivalent in Korean, not transliterated. Hanja in Korean source text are read by their Korean pronunciation before translation.
All three CJK languages have rich honorific systems but they don't align one-to-one. Korean has the deepest distinction (반말, 해요체, 합니다체); Japanese splits into desu/masu plain, sonkeigo (elevated), and kenjōgo (humble); Mandarin Chinese encodes politeness mostly through word choice rather than verb morphology. The model picks a sensible default per target; for matched levels, hint in the source.
East Asian personal names use Last-First order and stay in that order through CJK ↔ CJK translation. Hanzi / kanji names are converted to the target language's reading (e.g. Chinese 王偉 → Japanese 王偉 with the on-yomi reading "Ō I"; Korean reading via the Sino-Korean equivalent). Western names stay in their romanized form.
Place names use the local-standard spelling: Tokyo as 東京 in Japanese, 도쿄 in Korean, 东京 in simplified Chinese. The model knows the alignment table so cross-script place names stay recognizable.
All three CJK languages have a classical register (wenyan for Chinese, bungo for Japanese, hanmun for Korean) used in poetry, legal text, and historical context. The model translates classical source text by first rendering modern paraphrase, then applying the target's classical conventions where appropriate.
No spaces in Chinese or Japanese source text means the model must segment internally. Modern subword tokenizers (BPE / SentencePiece) handle this without an explicit segmentation pass. Korean uses spaces but with looser conventions than English; the model normalizes spacing on the output side.
✓ ✗ 〇 × 三 ★ ⭐ — common East-Asian symbol marks (especially 〇 / × for yes/no on forms) are preserved across Chinese and Korean. Standard Unicode emojis pass through unchanged.
Yes — Chinese, Japanese, and Korean conventionally use full-width punctuation (。 ， 、 「」 『』 （）). The output for any CJK target uses full-width forms, switching to half-width inside Latin / Western quoted strings.
For CJK ↔ CJK, paragraph-level chunks (500-1500 characters) get the best discourse-level quality because the model preserves cross-sentence references and topic-comment structure within a chunk. The hard limit is 10,000 characters per web request, 50,000 per API call.