Translation of the contribution guidelines to arabic #6017
Conversation
… first paragraph I made the Ar folder and the readme file and tried to make it look like the other translation attempts I translated the first paragraph until now A lot of the terminology has no formal translation in Arabic so I tried to find equivalents in Wikipedia and when no equivalent showed I tried to search in Hsoub as they teach programming in Arabic and made some terminology popular and when I found no equivalent in both of these sites I tried to come up with a translation like "pull request" I translated it to "طلب سحب" and in the first mention of the word I wrote PR next to it as an hint for the Arabic user and did the same for the words "issue" and "repository".
…contribution-guidelines-to-Arabic
I translated the second paragraph for the word familiar in at the end of the paragraph I used two words for translation which are: "تألف" ,"تفهم" I used these words instead of the equivalent word for familiar which is "تعتاد" as the words I used gives the meaning intended more than the word "تعتاد". The words "accessibility" and "inclusion" were translated to the words "إمكانية الوصول والإتاحة" and "حقوق المعاقين" The word "accessibility" has wo equivalents which are "إمكانية الوصول والإتاحة" but every word of these is has a distinct meaning but both used will give the meaning intended. For the word " inclusion" there is no direct equivalent for it in Arabic, so I tried to search it in Wikipedia and found out that it also means "disability rights" so I translated it to Arabic to "حقوق المعاقين". The word disabled has two equivalents in Arabic which are "المعاقين", "المعوقين" but "المعاقين " is the most used and uniformed word for this word so I used it.
This reverts commit 0f40058.
I translated the second paragraph for the word familiar in at the end of the paragraph I used two words for translation which are: "تألف" ,"تفهم" I used these words instead of the equivalent word for familiar which is "تعتاد" as the words I used gives the meaning intended more than the word "تعتاد". The words "accessibility" and "inclusion" were translated to the words "إمكانية الوصول والإتاحة" and "حقوق المعاقين" The word "accessibility" has wo equivalents which are "إمكانية الوصول والإتاحة" but every word of these is has a distinct meaning but both used will give the meaning intended. For the word " inclusion" there is no direct equivalent for it in Arabic, so I tried to search it in Wikipedia and found out that it also means "disability rights" so I translated it to Arabic to "حقوق المعاقين". The word disabled has two equivalents in Arabic which are "المعاقين", "المعوقين" but "المعاقين " is the most used and uniformed word for this word so I used it.
Finished the translation, but this is not the final form, I'm still searching for appropriate terms for some words in the terminology, also some additional revision on the text will be done to make it perfect and make sure that there are no typos or wrong grammar. There are a bug that occurred while writing this which is that the lists written in Arabic, have the list content in LTR while the list numbers/bullets are in RTL, I couldn't find a solution for this bug, but I'm still searching for a solution.
This should make no difference to how the readme looks on GitHub, but it changed the lists behavior in VSCode to show in RTL as intended.
…uidelines-to-Arabic
I used some words instead of others to fit the context better like: "العديد" instead of "الكثير" I eliminated the use of unnecessary "مصدر مؤول" which makes the text more comfortable to read. I fixed typos like "شفرة" and "الوقتن" I tried to rephrase some of the text to make it more meaningful I found an Arabic version of the ReactJS docs so I used the terminology they used for the GitHub terms like: pull request and issue, I used the terms "طلب مشكلة" and "طلب سحب"
…https://github.com/MostafaEwis/p5.js into translation-of-the-contribution-guidelines-to-Arabic
…uidelines-to-Arabic
|
🎉 Thanks for opening this pull request! Please check out our contributing guidelines if you haven't already. And be sure to add yourself to the list of contributors on the readme page! |
|
Thank you @MostafaEwis for working on it. I am inviting some p5.js contributors who worked p5.js Arabic translation before to review this pull request. Please feel free to leave your comments here. Thanks! |
|
Ok cool |
|
This looks great to me, thank you so much @MostafaEwis for your work on this! I'm sure it will help many more people to be able to participate in this community 🙂 I do have some suggestions, which I pushed up to a new fork on my own account for ease of viewing. If you agree with them, I'd also be happy to push my commit directly to your branch if you add me as a contributor there, or follow whatever other workflow makes sense. Here's the file as it looks after my edits: https://github.com/nabilhassein/p5.js/blob/translation-of-the-contribution-guidelines-to-Arabic/contributor_docs/ar/README.md The main idea behind my changes is to make the language more gender-neutral by avoiding addressing the reader with second-person masculine verb conjugations. As much as possible, I rephrased to use the "verbal noun" (مصدر) as consistent with the United Nations guidelines for gender-inclusive language, particularly section 3.9 "استعمال تراكيب غير مباشرة تليها مصادر عوضا عن تصريف الأفعال": https://www.un.org/ar/gender-inclusive-language/guidelines.shtml There were some cases where it seemed too awkward to do so; there, I used the second-person plural pronoun as a compromise, although that still doesn't fully avoid gender appearing given the way Arabic grammar works. Similarly, I think there are other places where my work could be further improved on -- for example, I struggled to come up with fully gender-neutral names in accordance with section 3.1 of the same UN document above ("استخدام أسماء محايدة جنسانيا") for nouns like "contributors" (مساهمين), "stewards" (المتعهدين), and "maintainers" (المشرفين). However, I think these are relatively minor issues compared to using masculine forms of address. Thanks again for your work, hope to see this out in the world soon! |
|
@nabilhassein Hi Nabil, thanks for your review and effort on improving the translation, I will be adding you as a contributor by tomorrow and we shall further discuss how to improve this and make it more gender neutral as it's really tricky to do so in Arabic |
…uidelines-to-Arabic
|
Thanks @MostafaEwis and @nabilhassein. Please leave a comment here when the updated translation is reviewed and ready to be merged. |
…uidelines-to-Arabic
- I kept the words which ends with "ضمير الوصل" "ك" and used no vocal characters as it depends on the reader to read it as the gender they think they are. - I kept the "ت" in the the end of verbs as it can be treated as "تاء الفاعل" or "تاء التأنيث" depending on the reader. - I used the "/ات" where I found no other way to omit the use of "جمع المذكر السالم" or no neutral way to mention the words "متعهد", "مساهم ", " مشرف". - The trickiest part was the "صيغة الفعل الأمر" which differs a lot depending on the gender you are calling so I had to omit most of them and used non imperative form which made the meaning differ but didn't really change it, except for line 13 where I found no way to use other forms than the imperative so I used it and added both of the forms for both genders. this overall made the meaning of some text differ but didn't really change it. I think it was better and more neutral to include the whole feminine word for words such as "مساهم" and the form "جمع المذكر السالم" but that was really going to make the text much much longer.
…uidelines-to-Arabic
|
Hi all and particularly @Qianqianye, just confirming on this thread that I reviewed this updated commit: MostafaEwis@0beddcf#commitcomment-103160578 @MostafaEwis has incorporated and/or further improved on all of my above suggestions -- I think the latest edited version looks great and is ready to be merged! |
|
@all-contributors please add @MostafaEwis for translation |
|
I've put up a pull request to add @MostafaEwis! 🎉 |
|
@all-contributors please add @nabilhassein for translation |
|
I've put up a pull request to add @nabilhassein! 🎉 |
|
Thank you @MostafaEwis and @nabilhassein for working on it. The Arabic translation is live on the contributor doc web page now. 🎉 |
|
Thank you @Qianqianye! I'm not sure if I can take on the responsibility of being a steward in the immediate future, but hopefully when my time becomes a bit more free around June, if not sooner 🙂 One note after looking at the live page at https://p5js.org/contributor-docs/#/ar/: unlike on github which seems to automatically detect the right to left direction of Arabic and display punctuation in the correct location in the rendered markdown I reviewed, I noticed that the punctuation is not in the correct visual location at the above link. I think it should be a quick fix of adding |
|
Hi @nabilhassein and @Qianqianye, I think that I would like to work further on the Arabic translation for the Contributor docs, and I will try to commit a fix for the text direction by the end of the day if @nabilhassein agrees. |
|
Hey @MostafaEwis, you can read more about the workflow in contributor_guidelines and i18n_contribution. Please feel free to tag me and @limzykenneth if you have any questions about p5.js translation. |
|
Hi @Qianqianye, GSOC has opened for proposals. Can I do the Arabic translation as a GSOC contributor? I mean, is this a valid idea as I didn't see adding new translations in the p5.js project list. |
|
Hi @Qianqianye again, should I focus now on the contributor docs, the FES or other parts. What has higher priority now? |
|
@MostafaEwis As far as I know, GSoC is more focused on technical projects and projects that just translate the contributor docs or FES may be difficult to make into a GSoC project. GSoD would be more suitable for a translation focused project. |
|
@MostafaEwis To add on what @limzykenneth said, another reason that we are not including p5.js translation project on the GSoc project list this year is that we'd like to review our translation process and potentially plan an updated workflow. If you are interested in working on p5.js projects for GSoC this year, I will highly recommend you to check out the projects labeled as 'High Priority'. |
Resolves #6001
Changes:
I created the Arabic translation of the contributer docs README.md
PR Checklist
npm run lintpasses