mirror of
https://github.com/HACKERALERT/Picocrypt.git
synced 2024-12-28 10:24:19 +00:00
Improvements
This commit is contained in:
parent
07513865ed
commit
2bd357f4cf
1 changed files with 4 additions and 4 deletions
|
@ -1,8 +1,8 @@
|
|||
# Help Translate Picocrypt!
|
||||
Are you fluent in another language? Help make Picocrypt more accessible to the world by translating the README into your language!
|
||||
# Translations
|
||||
Are you fluent in another language? Help make Picocrypt more accessible to the world by translating the README into your language.
|
||||
|
||||
## I'm Adding a New Translation
|
||||
Awesome. Simply fork this repository, add your translation, and submit a pull request. When adding your translation, you can use the raw markdown of the main README as a template and simply translate the English strings within the document to your language. Be careful not to mess around with any of the formatting, links, or numbers. Other than that, good luck!
|
||||
Awesome. Simply fork this repository, add your translation, and submit a pull request. When adding your translation, you can use the raw markdown of the README as a template and simply translate the English strings within the document to your language. Be careful not to mess around with any of the formatting, links, or numbers. Other than that, good luck!
|
||||
|
||||
## A Translation Already Exists
|
||||
Great. Now improve it! Since Picocrypt's translations are a community effort, they may contain a few grammatical errors here or there, and may be slightly out-of-date. If you notice any of these things, you're more than welcome to fix it. Try to make the document grammatically correct, smooth, and consistent with the formatting of the main README.
|
||||
Great. Now improve it! Since Picocrypt's translations are a community effort, they may contain a few errors here and there, and may also be slightly out-of-date. If you notice any of these things, you're encouraged to help fix them. Try to make the translation grammatically correct, naturally flowing, and consistent with the formatting of the README.
|
||||
|
|
Loading…
Reference in a new issue