docs(ko): unify custom node terminology to 커스텀 노드#1123
Merged
Conversation
Member
|
Thank you @OneVth, I'm working on a PR to refine the auto-translate process |
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
2 participants
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.
Summary
Unifies the Korean translation of "custom node" to 커스텀 노드 across the ko docs. It was previously inconsistent — mostly 맞춤형 노드 with some 커스텀 노드.
커스텀 노드 is the term the Korean ComfyUI community actually uses (it mirrors the "Custom Nodes" label in ComfyUI Manager, and is what Korean users search for), whereas 맞춤형 노드 is a literal translation rarely used in practice.
Changes
맞춤형 노드 / 맞춤 노드 → 커스텀 노드 (340 occurrences across 54 files). Text-only change.
Test plan
mint devrenders affected pages correctlymint broken-links— no new broken links