Persian translations

[saeedesmaili]

Description

I want to start translating the docs to Persian language and will track the progress here.

[mosi-kha]

sounds good!

[Kludex]

I'm going to ping the translations' coordination issue here: #1497 .
As we organize the translations there.

[tiangolo]

Awesome! I just added this issue to the pinned translations issue.

[meysam81]

@saeedesmaili
Need any help buddy? I'm game if you want a partner ✌️

[lnxpy]

@saeedesmaili I'm also ready to contribute.

[onionj]

I'm also ready to contribute. @saeedesmaili

[aminalaee]

@Kludex Do you think you can merge this #2395 through so people can start the translations?

And for anyone else, I think when #2395 is merged, we can just pick one or some markdown files from English docs and start the translations and put them in the Persian docs folder, and create PRs for them.
I'm happy to contribute in translations and reviews.

[Kludex]

I don't have merge rights on FastAPI. We'd need to wait for Sebastián to merge it.

What I recommend (so you don't are blocked) is to create branches on top of #2395, and when that is merged, rebase your branch.

[aminalaee]

Thanks for the reply. Honestly I thought about that too, but since the base branch is already a year old, if that's not approved and needs changes then we'll need some modifications in all new branches.

[Kludex]

Usually the first commit on a language translation doesn't have any translated pages. This PR has index.md translated, so that's maybe why it was not merged.

Even so, if that PR changes, each PR is minimal, only rebase will be needed without conflicts. If you feel like that PR is not going to be merged, for some reason (maybe changes are needed and author away), knowing that you're active on the community, maybe you should create the PR yourself (without the index.md being translated, only in English, like the other languages).