[ko] Inconsistent notation for "X-to-Y" terms (text-to-image, etc.)

[OneVth]

Summary

In the Korean (ko) docs, "X-to-Y" terms (text-to-image, image-to-image, image-to-video, text-to-model, …) are written in many inconsistent forms. Before fixing it I'd like to check the preferred direction, since it's a wording choice rather than a clear bug.

The inconsistency

For the single concept text-to-image, the ko docs currently mix at least:

count	form
131	텍스트-to-이미지
21	텍스트-to-image
12	텍스트 to 이미지
4	텍스트-to-Image
3	텍스트-to이미지

Across all X-to-Y concepts there are ~330 hybrid occurrences in ~44 files. The same pattern shows up in other concepts too — e.g. image-to-image appears as both 이미지 to 이미지 (20) and 이미지-to-이미지 (16); image-to-3D as 이미지-to-3D (13, Korean spliced with "3D"); also 텍스트-to-비디오, 이미지-to-비디오, 텍스트-to-모델, etc. Most splice an English "to" between Korean words, which reads awkwardly in Korean.

This is mostly ko-specific: in ja/zh the same concepts almost never appear as this hybrid — they keep the English form (text-to-image, Text to Image) or localize fully (e.g. ja テキストから画像生成). The hybrid is essentially a ko-only artifact of the auto-translation.

Direction

Two reasonable options for ko:

1. Keep English (text-to-image, Text to Image) — matches what ja/zh mostly do, and T2I is already in preserve_terms.
2. Localize fully to natural Korean (e.g. 텍스트 기반 이미지 생성).

I think (1) fits best given the ja/zh precedent and the existing T2I rule, and I have a ko-only branch ready that restores the English-source form. Mainly I wanted to confirm this is a change you'd want, and that "keep English" is consistent with how the project wants locale docs to treat these terms — happy to go with (2) instead if you'd prefer.

(Not proposing a glossary change: to check whether a future re-translation would just bring the hybrid back, I took the fixed files (hybrids already restored to the English form) and re-translated them with --force (pnpm translate -- --force <file>) using both deepseek-v4-pro and qwen-mt-plus. Neither reintroduces the hybrid, so fixing the content is enough on its own — no preserve_terms/glossary change needed.)

[coderabbitai]

🔗 Related PRs

#1143 - fix: correct "Aima" typo to "Anima" in anima tutorial [merged]

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[lin-bot23]

Hi OneVth, thanks for the thorough research on this! Lin here.

Just wondering — what would be the most natural/common way to write these X-to-Y terms in the Korean AI/tech community? e.g. does the community tend to fully localize (텍스트 기반 이미지 생성) or keep the English form (text-to-image)?

If you could share what's more commonly used, we'll update the glossary accordingly.

Thanks again for the contribution! 🙏

[OneVth]

Thanks Lin! For Korean specifically, here's the general tendency I see:

• In everyday community usage, people mostly use the English abbreviations — t2i, i2v, etc.
• Tech blogs and write-ups often keep the English term (text-to-image).
• Beginner-oriented posts tend to fully translate into Korean (e.g. 텍스트 기반 이미지 생성).

So apart from the 한글-to-한글 hybrid (which nobody really writes — it's purely an auto-translation artifact), there's no single fixed form; it's more of a tendency than a rule.

I first suggested keeping English, but when I checked ja/zh they mostly localize it — zh uses native terms (文生图, 图生图…) and ja writes it out (テキストから画像へ, often with (Text to Image) in parens). With that, and the Korean tendency to fully translate in beginner-facing writing, I'm now thinking full Korean localization might actually suit this better — though that's just my take.

[comfyui-wiki]

@OneVth, let's use the full translation. Have you made any changes? If not, I will update it by myself. Thank you again, really appreciate it.

[OneVth]

@comfyui-wiki, I haven't done the actual changes yet. The branch I had only converts things to the English form (from when I was leaning that way), so it doesn't really help here. Please go ahead.

If you run into any cases where you're unsure which Korean phrasing reads most naturally, feel free to ping me. Happy to help with that, and thanks again! 😄

[comfyui-wiki]

Got it! Thank you!

[OneVth]

Resolved by #1174. Thanks!

[comfyui-wiki]

Forgot to apply the new translation to the current Korean docs; will fix it tomorrow. Thank you, @OneVth