-
Notifications
You must be signed in to change notification settings - Fork 35
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
English layout changed, translations/reorganization needed for remaining languages #51
Comments
My suggestion is either to make a small TOC with the languages available at the beginning of the README and add the translations in the same file, or make different README in different languages and link to them from the main README file. I don't have a strong preference here, but maybe the first one is better since the README is not too verbose and mainly links to existent user guides |
I like the ideas. How about a TOC with links to other README languages that are hosted in kovri-docs? If we keep everything in one README, or even have another README, there will be too many PRs to the kovri repo that are unrelated to code and will clutter the log. Does that make sense? Any better solutions? |
That sounds like a good solution to me. If that's good for you i can start to work on it |
Yes, thank you. |
TOC created (monero-project/kovri#906) and Italian translation submitted (#53) |
Reviewed. |
NOTICE: THIS ISSUE HAS BEEN MOVED TO GitLab. Please continue the discussion there. See #102 for details. |
The building guide has been removed and build instructions moved to https://github.com/monero-project/kovri/blob/master/README.md. Other files/data have been moved into
user_guide.md
anddeveloper_guide.md
and include some minor changes.Also, as discussed here, #47 (comment), now that the build instructions are in the kovri README, we'll need to have a clear plan on how to handle translating the kovri README. This wouldn't be a website effort, the issue is about translating the kovri README either within the kovri repo or here. Input needed.
Ping @erciccione.
The text was updated successfully, but these errors were encountered: