course
course copied to clipboard
huggingface
Translate to Thai
Hi there 👋
Let's translate the course to Thai so that the whole community can benefit from this resource 🌎!
Below are the chapters and files that need translating - let us know here if you'd like to translate any and we'll add your name to the list. Once you're finished, open a pull request and tag this issue by including #issue-number in the description, where issue-number is the number of this issue.
🙋 If you'd like others to help you with the translation, you can also post in our forums or tag @_lewtun on Twitter to gain some visibility.
Chapters
0 - Setup
- [x]
1.mdx@peeraponw
1 - Transformer models
- [x]
1.mdx@peeraponw - [x]
2.mdx@peeraponw - [x]
3.mdx - [x]
4.mdx - [x]
5.mdx - [x]
6.mdx - [x]
7.mdx - [x]
8.mdx - [x]
9.mdx - [x]
10.mdx
2 - Using 🤗 Transformers
3 - Fine-tuning a pretrained model
4 - Sharing models and tokenizers
- [x]
1.mdx@jomariya23156 - [x]
2.mdx@jomariya23156 - [x]
3.mdx@jomariya23156 - [x]
4.mdx@jomariya23156 - [x]
5.mdx@jomariya23156 - [x]
6.mdx@jomariya23156
5 - The 🤗 Datasets library
6 - The 🤗 Tokenizers library
- [x]
1.mdxmeanna - [x]
2.mdx - [x]
3.mdx - [x]
3b.mdx - [x]
4.mdx - [x]
5.mdx - [x]
6.mdx - [x]
7.mdx - [x]
8.mdx - [x]
9.mdx - [x]
10.mdx
7 - Main NLP tasks
8 - How to ask for help
Events
- [ ]
1.mdx
We'll refactor thai2transformers and get back to you within the next month or so.
wav2vec2 tutorial for Thai https://github.com/vistec-AI/wav2vec2-large-xlsr-53-th/blob/main/notebooks/wav2vec2_finetuning_tutorial.ipynb
Extractive QA https://github.com/vistec-AI/thai2transformers/blob/dev/notebooks/train_question_answering_lm_finetuning.ipynb
Hey @a-krirk and @pattanunNP, thank you very much for your offer to help with the translation! I've added your names to the list :)
@cstorm125 we're currently focusing on doing direct translations of the English course content to Thai. If you'd like to contribute new content on training models in Thai, I suggest opening an issue in transformers to see whether our official tutorials could benefit from a translation :)
Hello, we have two PRs now ready for Thai!
- https://github.com/huggingface/course/pull/70
- https://github.com/huggingface/course/pull/73
Unfortunately, I don't speak Thai so would someone here be willing to have a quick look at the translations?
Hey @jomariya23156 thank you for offering to help! I've added your name to the list :)
I've just deployed the first part of the Thai translation 🥳 ! You can view it here: https://huggingface.co/course/th/chapter1/1
Next week we'll fix the language dropdown so that you can access all the languages from the same place.
@ckingkan thank you for offering to help! I've added your name to the list
Just curious how often should we do a PR? I am afraid @lewtun would be overloaded if we make a PR per section, which means 69 PRs per language. Should it be like once per a couple of sections, or like one third of the chapter per PR?
Just curious how often should we do a PR? I am afraid @lewtun would be overloaded if we make a PR per section, which means 69 PRs per language. Should it be like once per a couple of sections, or like one third of the chapter per PR?
Thanks for raising this issue @peeraponw! Indeed a PR per chapter would be ideal, but I understand that not everyone has the time to do this. So my general suggestion would be:
- If you're planning to tackle a whole chapter => open a PR for that chapter
- If you're planning to tackle a few sections of a chapter => open a PR for those sections
For the reviews themselves, I'll need all your help to do a quick check that the translations are OK, so having PRs covering multiple sections will help there too :)
Speaking of PRs, this one from @a-krirk is ready for someone to have a look at: https://github.com/huggingface/course/pull/73
Edit: here's another great PR for review: https://github.com/huggingface/course/pull/83
Edit: here's another PR for review: https://github.com/huggingface/course/pull/85
One thing you might want to discuss here is how to handle English technical terms like "pretrained model": https://github.com/huggingface/course/pull/73/files#r841659145
I'll leave this decision to you, but here's a few suggestions:
- Leave the technical terms in English
- Translate the technical terms, but add the English equivalent in parentheses. This is similar to how Wikipedia handles translations e.g. here
- Translate the technical terms where it makes sense and add a new "glossary" chapter with the corresponding terms in Thai and English
I think the Italian and Persian translations are going to adopt choice 3, so that might be the best option right now :)
One thing you might want to discuss here is how to handle English technical terms like "pretrained model": https://github.com/huggingface/course/pull/73/files#r841659145
I'll leave this decision to you, but here's a few suggestions:
- Leave the technical terms in English
- Translate the technical terms, but add the English equivalent in parentheses. This is similar to how Wikipedia handles translations e.g. here
- Translate the technical terms where it makes sense and add a new "glossary" chapter with the corresponding terms in Thai and English
I think the Italian and Persian translations are going to adopt choice 3, so that might be the best option right now :)
As mentioned in #73, my translation and @a-krirk translation seems to align with the 2. choice.
As mentioned in #73, my translation and @a-krirk translation seems to align with the 2. choice.
OK great, let's stick with that. We can always add a glossary later on :)
I'd like to translate chapter 6.
Fantastic! I've added your name to the list :)
I'd like to translate chapter 6.
Fantastic! I've added your name to the list :)
Nice, thank you. I'm having an exam at the uni this week. I think I can start next week:)