Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🌐 [i18n-KO] Translating docs to Korean #20179

Open
73 of 84 tasks
wonhyeongseo opened this issue Nov 12, 2022 · 19 comments
Open
73 of 84 tasks

🌐 [i18n-KO] Translating docs to Korean #20179

wonhyeongseo opened this issue Nov 12, 2022 · 19 comments
Labels
Documentation WIP Label your PR/Issue with WIP for some long outstanding Issues/PRs that are work in progress

Comments

@wonhyeongseo
Copy link
Contributor

wonhyeongseo commented Nov 12, 2022

Hi!

Let's bring the documentation to all the Korean-speaking community 🌏 (currently 9 out of 77 complete)

Would you want to translate? Please follow the 🤗 TRANSLATING guide. Here is a list of the files ready for translation. Let us know in this issue if you'd like to translate any, and we'll add your name to the list.

Some notes:

안녕하세요!

한국어를 사용하는 모두가 기술 문서를 읽을 수 있게 해보아요 🌏 (현재 77개 문서 중 9개 완료)

번역에 참여하고 싶으신가요? 🤗 번역 가이드를 먼저 읽어보시기 바랍니다. 끝 부분에 번역해야할 파일들이 나열되어 있습니다. 작업하고 계신 파일이 있다면 여기에 간단히 알려주세요. 중복되지 않도록 작업중으로 표시해둘게요.

참고 사항:

  • 기술 문서이지만 (친구에게 설명 듣듯이) 쉽게 읽히면 좋겠습니다. 존댓말 로 써주시면 감사하겠습니다.
  • 성별은 일부 언어(스페인어, 프랑스어 등)에만 적용되는 사항으로, 한국어의 경우 번역기를 사용하신 후 문장 기호와 조사 등이 알맞는지 확인해주시기 바랍니다.
  • 소스 폴더 아래 ko 폴더에 번역본을 넣어주세요.
  • 목차(ko/_toctree.yml)도 함께 업데이트해주세요. 영어 목차와 순서가 동일해야 합니다.
  • 모두 마치셨다면, 기록이 원활하도록 PR을 여실 때 현재 이슈(#20179)를 내용에 넣어주시기 바랍니다. 리뷰 요청은 @ArthurZucker님, @sgugger님, @eunseojo님께 요청해주세요.
  • 🙋 커뮤니티에 마음껏 홍보해주시기 바랍니다! 🤗 포럼에 올리셔도 좋아요.
  • 가짜연구소이니셔티브로 번역이 더욱 빠르게 진행될 예정입니다. 🎉 많은 응원 부탁드려요! 우리팀 화이팅 👍
    @0525hhgus, @kihoon71, @gabrielwithappy, @jungnerd, @sim-so, @HanNayeoniee, @wonhyeongseo

GET STARTED

TUTORIAL

TASK GUIDES

NATURAL LANGUAGE PROCESSING

AUDIO

COMPUTER VISION

MULTIMODAL

GENERATION

  • Customize the generation strategy

DEVELOPER GUIDES

PERFORMANCE AND SCALABILITY

  • Overview

EFFICIENT TRAINING TECHNIQUES

OPTIMIZING INFERENCE

CONTRIBUTE

CONCEPTUAL GUIDES

Other relevant PRs along the way

@wonhyeongseo wonhyeongseo changed the title Tranformers documentation translation to Korean [i18n/ko] Translating docs to Korean Nov 12, 2022
@wonhyeongseo wonhyeongseo changed the title [i18n/ko] Translating docs to Korean [i18n-KO] Translating docs to Korean Nov 12, 2022
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread.

Please note that issues that do not follow the contributing guidelines are likely to be ignored.

@wonhyeongseo
Copy link
Contributor Author

Hello @sgugger, may you please add the WIP tag to this issue? Thank you so much.

@sgugger sgugger added the WIP Label your PR/Issue with WIP for some long outstanding Issues/PRs that are work in progress label Dec 13, 2022
@wonhyeongseo wonhyeongseo changed the title [i18n-KO] Translating docs to Korean 🌐 [i18n-KO] Translating docs to Korean Dec 31, 2022
@jungnerd jungnerd mentioned this issue Apr 1, 2023
5 tasks
@wonhyeongseo
Copy link
Contributor Author

wonhyeongseo commented Apr 2, 2023

For contributors and PseudoLab team members, please see a PR template gist (raw) that could ease your first PR experience.
@0525hhgus, @kihoon71, @gabrielwithappy, @jungnerd, @sim-so, @HanNayeoniee, @wonhyeongseo

@gabrielwithappy
Copy link
Contributor

gabrielwithappy commented Apr 3, 2023

Dear @sgugger, would you add document label to this issue?
I think other issues for the translation have a document label.
Thank you in advance

@wonhyeongseo
I changed my PR with a new PR template. would you change
Load pretrained instances with an AutoClass to [WIP]🌐[i18n-KO] Translate autoclass_tutorial to Korean and Fix the typo of quicktour #22533

@gabrielwithappy
Copy link
Contributor

@sgugger wow! Thank you a million! :-)

@jungnerd
Copy link
Contributor

jungnerd commented Oct 8, 2024

Hi @stevhliu 👋🏻

Our team is currently conducting a translation sprint, resulting in a lot of PRs.

By the way, we recently discovered that the Quantization Methods (which is 경량화 메소드 in Korean) section in ko/_toctree.yml was accidentally duplicated in a previous PR, which unfortunately went unnoticed before being merged. As a result, this duplication now exists across all subsequent PRs, including those that are still open.

Given the large number of merged and open PRs, we are considering two possible approaches to address this:

  • When all current PRs are merged, then submitting a dedicated PR to fix the duplication in ko/_toctree.yml.
  • Explore alternative solutions that can resolve the issue more efficiently.

We apologize for not catching this during the review process 🥲
We're seeking advice on the best approach to resolve this issue while minimizing disruption to ongoing work.

Any suggestions or recommendations would be greatly appreciated, and we sincerely appreciate your ongoing support and careful reviews of our PRs ❤️

@stevhliu
Copy link
Member

stevhliu commented Oct 9, 2024

Great work on the translation sprint everyone! 🚀

I think it'll be easiest to submit a dedicated PR to remove the duplicated section once all the current PRs are merged :)

@maximizemaxwell
Copy link
Contributor

Hi there, I want to contribute to the translation of the "Training on Specialized Hardware" section and submit a PR once it’s completed. Is it OK?

@stevhliu
Copy link
Member

stevhliu commented Nov 4, 2024

Hi and thanks for your interest in translating @maximizemaxwell, feel free to translate that section! 🤗

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation WIP Label your PR/Issue with WIP for some long outstanding Issues/PRs that are work in progress
Projects
None yet
Development

No branches or pull requests

10 participants