-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Abooooout translations. #853
Comments
You may want to coordinate with @nodejs/nodejs-ko, but there is not a limit on seats for translators. More are always welcome! :) You will need one other person from that group to review your work before it goes live, but otherwise feel free to create new pull requests here. |
We're now trying to translate the website. (see, #843 and nodejs/nodejs-ko#381 ) |
@Hojin-Ryu Node.js foundation already has @nodejs/nodejs-ko team, which I belong to. We've been translating contents related to Node.js into Korean for 18 months. You can join us if you're interested in. @Fishrock123 I think you can close this issue. :) |
Closing as per @taggon comment. |
damn. 2016-08-09 19:11 GMT+09:00 Luigi Pinca [email protected]:
|
Korean translation persentage is too low.
Cuz I can do English very well, that wasn't problem.
But it seems there is a problem a lot.
For example, the reference. Moreover different than written in korean.
I don't have much time on it, so i'll make it short.
Is there any seats for translators in node.js's site?
If not, i'll now work on it.
The text was updated successfully, but these errors were encountered: