Update 2.0 README translations #1249
Comments
Here are all the commits on README, most everything since the last release fits on one page: |
Hi. I'd like to update Russian translation of 2.0 README. |
There is a phrase in section Literal Templates: "if there is a filesystem path or line associated with that string". Maybe and will be more suitable in this context? |
I am currently working on the Spanish translation. |
Update README.ru.md to actual version of English README. Fix small punctuation and stylistic issues.
Check out #1393 with up-to-date RU translation. |
@burningTyger Do you still need pt-BR translation for 2.0 README? |
@raphaeltelatim Sorry, my Portuguese is not good enough to tell if it's up to date :) But if it needs new docs we're happy to merge them! Thank you for your efforts. |
@burningTyger I've checked the pt-BR translation from README and realized that it is outdated, can I work on it? =) |
@Klockner sure, that would be great. |
@burningTyger It is my first contribution. So I will start with this little one (#1497) to take the way and keep moving forward. Should I use this same PR for all the changes that will come or should I do it in separated parts? |
@Klockner this looks good so far. I suggest you translate the explanations around the code samples which you already did along with the different configuration settings and then sqash them into one commit so it looks nice. If all you edit is the md file you can add a One more thing I noticed. Could you try to keep each line with 80 characters or less? ie. make a line break before 80 characters? I know, it's a relic from the past but I found it quite useful later on when comparing line changes. |
@burningTyger I got someone pt-br native to do the review. I have also applied your suggestions on it. |
I would like to add indonesian translation, is there any requirements I need to understand? |
@christopherganda first of all welcome to sinatra! If you would like to translate feel free just start with the basics. The documentation is quite comprehensive and even a subset is a great start. It helps if you have someone you can work with and who can proof read your translations. I will be checking your translation afterwards for style errors and the like. |
@burningTyger Cool! Working on it |
I noticed that pt-br translation needs some updates. @Klockner are you working on this? I can start to work on those updates if you stopped to translate :) |
@jeduardo824 sounds great for me, if it's ok for @burningTyger go ahead! I can also do the pt-br review for you =) We already have this WIP PR: |
sure, just go ahead. |
Anyone need help with the Brazilian Portuguese ? |
Is the topic still valid ? |
@PedroPaulino I updated Brazillian Portuguese translation. Waiting for the merge. |
I've had a very quick glance at it. Please fix the following parts:
|
the issue still valid to new translations? |
Sure, but it would be good if someone took this over from me. |
I can give a go at updating the French readme, looks like it's not been updated for 6 months. |
Got a PR for updates on the French readme : #1568 I might make a separate PR someday for the "sessions" section where a lot of new content is missing. But don't have enough time for it right now. |
My PR for pt-br translations is here: #1573 Soon I'll update the other half of the file |
I already have a PR with an updated PT-BR translation @camillesk #1540 |
Hey guys Any maintainer in particular we should ping about this? |
The Readme is our comprehensive sinatra documentation and deserves a lot of love. Thank you for everybody who has contributed to it so far!
The translations are great but some of them seem incomplete or outdated. For sinatra 2.0 they need a major overhaul and here's a list of languages that need to be worked on:
The text was updated successfully, but these errors were encountered: