-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Chinese Version Document #1285
Comments
is PR welcome? @brc-dd |
@awxiaoxian2020 I don't think we will be able to have both English and Chinese docs in this repo itself considering that i18n is not yet implemented. In future (after #1339 is merged) it might be possible to have both |
@brc-dd I think I can draft a pull request for |
@buduan @dong-lufei you can review Chinese doc here. |
Great idea, but I'm a little worried that after adding more translation languages in the future, the bundle time and size of the document itself will increase, and the issue/PR will be filled with trivial translation tasks. Can we consider dividing different languages into different repo for maintenance like vite :) Vite: https://github.com/vitejs/docs-cn |
@CHOYSEN Please see vuejs-translations/docs-zh-cn#561 |
Yeah so in future, if there are many requests for different languages we can probably move them to separate repos in translations org, and give the contributors write access there. But for now, it seems fine to have Chinese translations here itself. Till now, I haven't seen requests for any other languages, and considering that the amount of contributors that understand Chinese is significant, I hope it won't be much of a burden to maintain. I'm not a Chinese speaker, so I'm mostly reviewing the PRs using translation tools and stuff. This might not result in top-notch quality for Chinese docs, but it should be fine as long as our Chinese users keep contributing. |
Is your feature request related to a problem? Please describe.
希望官方能出一套中文的文档,感谢
Describe the solution you'd like
希望官方能出一套中文的文档,感谢
Describe alternatives you've considered
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: