Skip to content

Conversation

@luckyvickyricky
Copy link
Contributor

What does this PR do?

Translated the main_classes/backbones.md file of the documentation to Korean.
Thank you in advance for your review.

Part of #20179

Before reviewing

  • Check for missing / redundant translations (번역 누락/중복 검사)
  • Grammar Check (맞춤법 검사)
  • Review or Add new terms to glossary (용어 확인 및 추가)
  • Check Inline TOC (e.g. [[lowercased-header]])
  • Check live-preview for gotchas (live-preview로 정상작동 확인)

Who can review? (Initial)

May you please review this PR?
@jungnerd, @chelsseeey, @skwh54, @amo33, @maximizemaxwell, @D15M4S
@harheem
@4N3MONE
@yijun-lee

Before submitting

  • This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
  • Did you read the contributor guideline,
    Pull Request section?
  • Was this discussed/approved via a Github issue or the forum? Please add a link
    to it if that's the case.
  • Did you make sure to update the documentation with your changes? Here are the
    documentation guidelines, and
    here are tips on formatting docstrings.
  • Did you write any new necessary tests?

Who can review? (Final)

Changed "특징 추출" to "특성 추출" and "출력 특징" to "출력 특성" to follow the established translation glossary for "feature" terminology.
- Fix markdown formatting issues
- Standardize backbone terminology to "백본" for consistency
- Resolve translation inconsistencies across different sources
@luckyvickyricky
Copy link
Contributor Author

This PR re-translates the previously deprecated Korean backbone documentation (#39714) and incorporates community feedback to unify the "backbone" terminology. After discussion about inconsistent translations(TTA terminology using "기간", glossary using "기반", and tech blogs using "백본"), we've used to "백본" for better clarity and consistency. The markdown formatting issues from the previous PR comments have also been addressed for better readability.

@4N3MONE
Copy link
Contributor

4N3MONE commented Oct 22, 2025

LGTM! 👍

Copy link
Contributor

@ahnjj ahnjj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM !!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants