🌐 [i18n-KO] Translated main_classes/processors.md to Korean
#39715
Conversation
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
…traction Changed '양식' to '모달리티' and '특징 추출기' to '특성 추출기' to use more accurate and consistent technical terminology in multimodal contexts.
Changed '골드 레이블' to '정답 레이블' to use a more natural Korean expression that better conveys the meaning of ground truth labels.
Simplified complex sentence structures by removing redundant phrases and making the text flow more naturally in Korean.
Simplified complex sentence structures by removing redundant phrases and making the text flow more naturally in Korean.
|
39519 와 중복 PR입니다. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Translated the
main_classes/processors.mdfile of the documentation to Korean.Thank you in advance for your review.
Part of #20179
Before reviewing
[[lowercased-header]])Who can review? (Initial)
May you please review this PR?
@jungnerd
@harheem
@4N3MONE
@yijun-lee
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review? (Final)