-
-
Notifications
You must be signed in to change notification settings - Fork 76.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I want to translate in hebrew #1000
Comments
Btw I speak hebrew natively |
Posso ajudar |
Relatório semanal |
I am sorry, but I don't understand the language. Do you speak english? |
He said* *Using google translate as i dont speak Portuguese Except for that, Tamir I also thought to try and help translating this cool project into hebrew, maybe we can team up? |
@odedindi Sure, any help will be good. What is your level of hebrew? |
Good day, Feel free to add to the existing partial one, and I can merge in changes as you create PRs. There's no need to translate all at once. Thanks again! |
@jwasham I don't fully understand, as a native speaker it looks fine. Are you referring to the proper way to do it via GitHub markup? |
@Tamir198 great!, im gonna do now the section underneath this one until the Table of Contents |
a'ight.. i've opened a pr about the short paragraph that comes before the table of contents. also if any one else except me and @Tamir198 wanna join in please write here or open another issue and let us know what you are working on so we don't do double the work for nothing. |
i wanna join |
@A-nisa963 you are welcome to join, I don't have so much time right now, I will try to return and translate this later on. |
Hey, I would like to continue adding Hebrew to the already (partial) existing translation.
The thing is, I won't have the time to translate it all at once.
And I have a question regarding the subject :
For your convenience, would you rather have something like weekly pr with what I could do for that week, or When I finish translating a section in the README I will open a pr?
The text was updated successfully, but these errors were encountered: