-
Notifications
You must be signed in to change notification settings - Fork 38
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 would like to help to translate to Spanish (from English) #36
Comments
That sounds great! I will create a new branch in two days and you can work on it! |
Hi, you can work on this branch now: https://github.com/gossip-ink/gossip/tree/lang/spanish I think there are three parts you can translate:
If you have any further questions, feel free to let me know. |
Please, I didn't know how to create or upload a new "README.es-ES.md file".
Could you help me?
Thank you
El dom, 13 feb 2022 a las 7:31, MiniPear ***@***.***>)
escribió:
… Assigned #36 <#36> to
@RafaelLinux <https://github.com/RafaelLinux>.
—
Reply to this email directly, view it on GitHub
<#36 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADDRY744IEJZRBKFNMKUWXDU25F4VANCNFSM5OACDBXQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
OK, there are several steps:
|
It seems to be even more difficult that you wrote:
Clonando en 'gossip'...
The authenticity of host 'github.com (140.82.121.3)' can't be established.
ECDSA key fingerprint is
SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'github.com,140.82.121.3' (ECDSA) to the list of
known hosts.
***@***.***: Permission denied (publickey).
fatal: No se pudo leer del repositorio remoto.
Last message says "fatal: Remote repository can't be read"
El mar, 15 feb 2022 a las 15:55, MiniPear ***@***.***>)
escribió:
… OK, there are several steps:
- Clone this repo: Open terminal, change to desired folder and run git
clone ***@***.***:gossip-ink/gossip.git
- Fetch the branch lang/spanish:cd gossip && git fetch origin
lang/spanish
- Rename the exist file README.ESP.md to README.es-ES.md
- Translate the content to README.es-ES.md
- Commit the change: git add . && git commit -m "docs: translate
README.md from English to Spanish"
- Push the current branch to upstream: git push origin lang/spanish
- Create a pull request in https://github.com/gossip-ink/gossip/pulls
—
Reply to this email directly, view it on GitHub
<#36 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADDRY77WXAKDERW4LP4FRUTU3JSNZANCNFSM5OACDBXQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I added all ES tags to locales.js and pulled it. However, I don't see my changes anyway even in "pulled changes"!!!! What did happen to my changes to "locales.js"??? Thank you |
Do you clone this repo successfully? What do you mean you don't see your changes? |
There are two distinct parts: On the other hand, I followed the steps you took the trouble to write to me: So these are two different questions. |
I'm sorry to forget to tell you that you must fork it! I can see this branch for the translation: https://github.com/RafaelLinux/gossip/tree/patch-1, you can now open a pull request! |
This project is awesome and I would like to teach to use it to Spanish speakers people. How could I help about it?
Thank you
The text was updated successfully, but these errors were encountered: