question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Translation to Persian

See original GitHub issue

Hi 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:

  1. Please fork the Hugging Face course to your profile.
  2. Clone your fork to your local machine.
  3. Use this issue page for general discussion on word choices and whatnot.
  4. Fetch frequently from upstream to your fork and keep your local working tree updated.
  5. It is perfectly fine to link to your fork on this page for discussions.
  6. 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)
  7. 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.
  8. 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.
  9. 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

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:open
  • Created a year ago
  • Reactions:1
  • Comments:70 (70 by maintainers)

github_iconTop GitHub Comments

4reactions
jowharshamshiricommented, Apr 18, 2022

Hi everyone! Great to see Persian community here hugs. I would also like to contribute by taking over chapter4, if you will. Let’s get it done 😉

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.

3reactions
jowharshamshiricommented, Apr 23, 2022

Hi @hamedonline jan,

Please review the first draft of Chapter2/Page3.

These are questions that occurred to me in the new page.

  1. Take this sentence. Should اشتراک and گذاشته be separated by a half-space per our last review? Seems weird. . …را به اشتراک گذاشته…

  2. 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?

  3. 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?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Translate English to Persian online
Choose your English to Persian translation service ... Urgent professional translation ⧉ from an expert. Only $0.07/word! Source language.
Read more >
Farsi Translator : English to Persian Dictionary
Online Farsi translation tool instantly translates text. This Farsi translator supports Persian, English, Spanish, German, Swedish and French.
Read more >
English to Persian translation - ImTranslator
Free Online English to Persian Online Translation Service. The English to Persian translator can translate text, words and phrases into over 100 languages....
Read more >
Persian-English Online Translation and Dictionary - Lingvanex.
English to Persian translation by Lingvanex translation software will help you to get a fulminant translation of words, phrases, and texts from English...
Read more >
Persian - English Translation
Persian - English Translation, Dictionary, Text To Speech, detect language, Back translation, decoder, keyboard, spelling, Compare translation, ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found