-
-
Notifications
You must be signed in to change notification settings - Fork 9.9k
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
Translated of README.markdown and CONTRIBUTING.markdown into Japanese. #2081
Translated of README.markdown and CONTRIBUTING.markdown into Japanese. #2081
Conversation
What do you think about putting these in a folder called @kansaichris, would you be willing to read these over and advise as to organization of translated core documentation? Would be most appreciative. ❤️ |
I think putting these into a docs folder would be fantastic. |
Thank you for merge. Next, I'm going to translate the docs of Where should put translating docs ? |
For the site, it may be more productive for you to do what @matheus has done with @mattr- and I can't read or write Japanese, so we'd prefer not to have to maintain it. 😃 |
I personally think that translated versions of README and CONTRIBUTING should be placed in the root directory where they are easy to find—ruby/ruby already follows a similar convention for its README. If you would prefer not to maintain translated versions of the entire Jekyll website ( |
@kansaichris so they'd be README.jp.md and CONTRIBUTING.jp.md in the project root, right? |
@mattr- Yeah, that sounds about right. Of course, because the original (English) files use the |
@kansaichris ❤️ Thanks! |
Just testing the waters, but what do people think about adding information for translators in the README? I could submit a pull request with some preliminary wording if you'd like. |
@kansaichris I think that's a fantastic idea. My biggest worry is maintainability, however – I can speak German well enough to look over a PR and I could fumble through a pull request for a Welsh translation, but Japanese is well beyond my current linguistic abilities. What are your thoughts on this? Should we separate out doc translations so the onus is not on @mattr- and I to maintain docs in a language neither of us can speak, or do we keep them around here with the disclaimer that they aren't actively maintained by either of us? |
@parkr That's a good question. To be clear, I only think that translations of the documents in the root directory (like README and CONTRIBUTING) would ever belong in this repository. Translations of the Jekyll site itself probably belong in forks, possibly owned by the Jekyll organization. This would really reduce the number of pull requests with non-English content that you'd have to deal with. My only concern is that a poor translation could hurt the Jekyll name/"brand" without you or any of the other active maintainers being aware of it. I agree that a disclaimer would be really important to dispel any potential confusion about which information is canonical and which is not. |
Thanks a lot. Last, If I have finished translating overall documents, then try to mimic the repository method of @matheus. Is it OK ? |
I think that's a great solution for this. I agree with @kansaichris. As translations mature a bit, I want to start pulling those translated sites into the Jekyll organization, similar to how Boxen does it with the various add-on repos forked from other people. Thanks for translating! ❤️ |
✨ @gosyujin For the record, that repository is https://github.com/gosyujin/jekyllrb.com.jp, correct? |
@kansaichris That's right.
I had been consider how managed. |
I don’t want to ruin the party, but translations are a huge waste of time. Foreign coders don’t trust them, because translations are always bad maintained. Please read The Ugly American Programmer by Jeff Atwood for better understanding. |
Good Post! But even Jeff Atwood translated the Stackoverflow to Portuguese http://blog.stackoverflow.com/2014/02/cant-we-all-be-reasonable-and-speak-english/ |
Thank you for important advice.
I began to translate https://github.com/gosyujin/jekyllrb.com.jp! |
For those of you who don't read Japanese, this appears to be the note in question:
Here it is in English:
✌️ 😄 |
Thank you @kansaichris and @gosyujin! ❤️ |
@kansaichris That' right! |
I translated README.markdown and CONTRIBUTING.markdown into Japanese.
But I didn't know the following...
I've read CONTRIBUTING.markdown and "Updating Documentation" of http://jekyllrb.com/docs/contributing/ .
I will follow the rules.