ترجمه فارسی آماده بازبینی است | Farsi Translation

[MrHinsh]

🔍 Farsi Translation Ready for Review

Preview link:
https://agreeable-island-0c966e810-preview.centralus.6.azurestaticapps.net/fa/

Language: Farsi (fa)
Status: ⏳ In Review

💡 We need your help with:

• Reviewing the translation
• Testing the multilingual functionality of the site

If you speak Farsi or are familiar with technical translations, your contribution would be highly valuable.

---

👥 Contributors

• Translator(s):

Co-authored-by: Pedram Keshavarzi <[email protected]>
Co-authored-by: Alinaderivarandi <[email protected]>
Co-authored-by: Pooya Sabramooz <[email protected]>

• Reviewer(s):

1. @JaamySkm
2. @farzadtara
3. @pantehash
4. @AliSaxaei
5. @javadbat

• Other contributors:

[MrHinsh]

Issues Ive found:

• Creators has soem hard coded links that are not honoring the translation 🐞 Fix: Language Switch Produces 404 on Non-Homepage Routes #63
• creator photos are not working in farsi 🐞 Bug: Creator Photos Not Displayed on Farsi Pages #66
• Changing language on a translated page causes a 404 as its continuously appending language codes. e.g. /tlh/fa/creators/ralph-jocham/ 🐞 Fix: Language Switch Produces 404 on Non-Homepage Routes #63

[Alinaderivarandi]

For your Info: @pedicurus

Any update regarding these issues?

[pedicurus]

@Alinaderivarandi
These have been resolved.

[ViralGoodAgile]

Inspired by another non-Scrum guide website that has the highest quality translations, to the extent that the translations are trusted, the authors of the Scrum Guide Expansion Pack created a Translation Code of Conduct for the Scrum Guide Expansion Pack(SGEP).

The authors of the SGEP were caught a little off guard by the number of translation requests and the level of enthusiasm in a short period.

Translators of the Scrum Guide Expansion Pack and its associated materials do our community an invaluable service and are greatly appreciated. The Code of Conduct for Scrum Guide Expansion Pack Translations outlines expectations and standards to ensure that translation work is of the highest quality and serves the best interests of the communities served by the Scrum Guide Expansion Pack.

Translators must agree to the Translation Code of Conduct before translating, re-translating, or continuing to translate any written materials associated with the Scrum Guide Expansion Pack. All translators in any translation must comply with the Translation Code of Conduct for the Scrum Guide Expansion Pack.

Suggestions to improve the Translation Code of Conduct can be submitted using discussions.

Translation refers to any translated document from the official website(s) publishing the Scrum Guide Expansion Pack, currently the Scrum Guide Expansion Pack website.

A translator is a person who facilitates, creates, amends, or reviews the translation(s) of documents on the official website(s) for accessing the Scrum Guide Expansion Pack.

If any translator is uncomfortable with the Translation Code of Conduct, they must stop their involvement in SGEP translation work and allow other translators to proceed without them. Any perceived breaches of the Translation Code of Conduct may be reported to me privately via email to [email protected], and I will arrange calls to discuss, review the evidence shared with me, and review all sides of such reports. There is no appeals process.

[pedicurus]

@Alinaderivarandi review the pack please whenever @MrHinsh merge the changes. The Persian Expansion Pack has been fully translated. It needs your review.

[pedicurus]

Dear @MrHinsh

We also want to translate the home and translation pages from scratch. Because they were translated by a machine, they were not fluent and common for Persians. In addition, they were not compatible with what we have translated in the Expansion Pack.

Could you tell us how to modify them? In which files are they stored?

Thanks

[MrHinsh]

Search for .fa..md... They contain the core data.

There is also lookup table in the i18n folder... Fa.yml

[pedicurus]

Got it, Thanks. It must be in ...fa.yml.

[pedicurus]

If you are going to discuss an equivalent of a specific term, see the below topic and put your feedback. We have translated the whole Expansion Pack according to the following agreement: #165

[javadbat]

Dear @MrHinsh and @pedicurus,

I’ve reviewed the Persian guide—it reads fluently and is easy to follow.
However, I noticed some inconsistencies between the guide and the homepage.
@pedicurus mentioned that he is working on resolving them.

Best regards,
Javad

[pedicurus]

Thanks @javadbat for your reviewing.

[pedicurus]

Dear @MrHinsh

Where is {{ .Site.Title }}? It must be "مقاله‌ی مکمل راهنمای اسکرام" not "بسته گسترش‌یافته راهنمای اسکرام". I can't find its source.

[JaamySkm]

Hi @MrHinsh and @pedicurus,
I’ve finished reviewing the Persian Expansion Pack. It’s very well written and easy to understand.
Well done!

Best wishes,
Jamasb

[pedicurus]

Thanks @JaamySkm

[AliSaxaei]

Dear @MrHinsh and @pedicurus,
I’ve reviewed the Persian Expansion Pack.
In terms of clarity and comprehensibility for someone who is already familiar with Scrum and its underlying practices, I find the translation to be clear, useful, and practical. With careful reading, one can gain a deeper understanding of the concepts, which ultimately comes through practical experience and intuitive knowledge in this domain.
One point I would like to suggest is to consider including the original English term with each specialized or technical term that has been translated into Persian. This would help ensure that the original terminology does not get lost within the translated text, and it would also allow readers and users of this guide to become familiar with the corresponding English terms as well.

[pedicurus]

Thanks @AliSaxaei , we'll apply your improvement.

FYI @Alinaderivarandi

[farzadtara]

Hi @MrHinsh and @pedicurus
I’ve reviewed the Persian Expansion Pack. The translation is clear and conveys the original intent well. Minor consistency improvements in key term usage could make it even stronger. Great job

[pedicurus]

Thanks @farzadtara for reviewing, we are going to mention the original English terms within (_) after each translation. I hope it ensures the consistency.

[pantehash]

Hi @MrHinsh and @pedicurus,
I’ve reviewed it—it’s clear and easy to understand. Including the original English term alongside each technical word would make it even better.

[Alinaderivarandi]

Dear @MrHinsh and @ViralGoodAgile ,

Five Scrum nerds reviewed the translation, and we took their feedback into consideration. I think the next step is to make it available to all Farsi speakers. After that, we will try to keep the community active and work on continuous improvement.

Special thanks to our reviewers:
@JaamySkm
@farzadtara
@pantehash
@AliSaxaei
@javadbat

P.S: Special thanks to the Farsi language community, which worked on the translation and review. I am aware of the current situation in Iran and its limitations, but you did a great job. For me, it was a great collaboration. I am happy to have met you all and look forward to continuing our collaboration. Cheers!

[pedicurus]

Thanks, @Alinaderivarandi, for being with me as the co-author of the Persian Expansion Pack.

@MrHinsh , Please also consider @marjanfazli as another reviewer, and @sabramooz as the other contributer which has helped us initiate the project.

[marjanfazli]

Hi @MrHinsh and @pedicurus,
I’ve reviewed it. It’s clear and well-understood. If there was an original English word after each technical term, it would be awesome.

[pedicurus]

Thanks, @marjanfazli, for reviewing the translation.

[MrHinsh]

@ViralGoodAgile, @rjocham all i need is a GO from you to flip the switch on farsi.

There are 5 reviewers listed, and it's technically done.

[ViralGoodAgile]

GO. Thank you very much for your service to the communities, @MrHinsh and the Farsi translations group.

[rjocham]

Hey Farsi translators, thanks for your hard work. Your translation went live, if there any issues please let us know.
If you are ok, feel free to go wild on social media.

[pedicurus]

You're very welcome—it was our pleasure!
I've already shared a post on my LinkedIn account and on the Agile Gap podcast page to spread the word.

We’re excited to see it live, and we’ll definitely let you know if anything comes up. Thanks again for the opportunity!