Translation to Persian
See original GitHub issueHi there 👋
Let’s translate the course to Persian so that the whole community can benefit from this resource 🌎!
Before you get started please take a minute to read the latest version of our evolving translation guidelines (T). It is important that we maintain a common tone in our collective work, while contributing with our separate creative voices.
We have a glossary page (G) where we store our latest choice of Persian equivalents for words. This page may be subject to change with every PR and its review discussion. If there are changes, we will mention here that the glossary file has been updated. We need to retroactively apply the changes to our sections.
Check here for general instructions on contributing.
Here’s the workflow for contributions:
- Please fork the Hugging Face course to your profile.
- Clone your fork to your local machine.
- Use this issue page for general discussion on word choices and whatnot.
- Fetch frequently from upstream to your fork and keep your local working tree updated.
- It is perfectly fine to link to your fork on this page for discussions.
- When you have the first draft of a page(s) done commit back to your fork and open a PR for that page(s) on the Hugging Face course repo. (Huggingface course/main branch <- Your fork/main or whatever branch you have)
- Ask someone to help you review the page(s) there. Commit the changes back to your fork and they will automatically be appended to the PR.
- If you have updates to the glossary try to include the stakeholders in the discussion(check commit history) and when done mention the changes on this page so we can all apply the changes retroactively to our sections.
- When done with the review, ask @lewtun to merge.
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
1 - Transformer models
2 - Using 🤗 Transformers
-
1.mdx
@jowharshamshiri -
2.mdx
@jowharshamshiri -
3.mdx
@jowharshamshiri -
4.mdx
WIP @jowharshamshiri -
5.mdx
-
6.mdx
-
7.mdx
-
8.mdx
3 - Fine-tuning a pretrained model
4 - Sharing models and tokenizers
5 - The 🤗 Datasets library
6 - The 🤗 Tokenizers library
7 - Main NLP tasks
8 - How to ask for help
Events
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:70 (70 by maintainers)
Hi @hamedonline jan. Super happy to have you join us. Thanks for donating your time. Please checkout the glossary, it is a work in progress and your input is very much appreciated.
@lewtun I added Hamed’s name to chapter 4. @kambizG Please confirm if you’d like to work on chapter 3.
Hi @hamedonline jan,
Please review the first draft of Chapter2/Page3.
These are questions that occurred to me in the new page.
Take this sentence. Should اشتراک and گذاشته be separated by a half-space per our last review? Seems weird. . …را به اشتراک گذاشته…
Both me and @kambizG jan, previously did not distinguish btw equivalents for “cache” and “save”. I have a section on how caching of models happens immediately followed by a section on saving the models, in the new page. How do you guys think we should proceed?
I previously asked about the accepted equivalent for “Encoder” and “Decoder” while reviewing @schoobani jan’s work. I have the verb “encode” here, but it’s only used to mean we assign numbers to things, for which “رمزنگاری” doesn’t really work. How do you guys think we should proceed? “کد گذاری” or “کد شدن” maybe?