-
-
Notifications
You must be signed in to change notification settings - Fork 902
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
docs: Support for Other Language #2346
Comments
Thank you for your feature proposal. We marked it as "waiting for user interest" for now to gather some feedback from our community:
We would also like to hear about other community members' use cases for the feature to give us a better understanding of their potential implicit or explicit requirements. We will start the implementation based on:
We do this because:
|
Thats interesting. As a german, I actually hate reading translated documentation. Often, most words remain in English due to the contextual relevance or if everything is translated it tends to sound unnatural and awkward. May I ask which translation languages you'd like to see in our documentation? |
@xDivisionByZerox |
We could potentially use a Crowdin or similar service to maintain the translations, that way we don't have to manage them in code. @CoolPlayLin Are you willing to maintain the Chinese translations for at least a year, if we decide to add them? (Currently, there doesn't seem to be that much of a need, if we look at the votes) |
@ST-DDT I'm willing to do it if I have free time. I am going to maintain it almost every weekends. Also, I think docs could add more version for different kinds of languages if there is someone willing to maintain it. |
Clear and concise description of the problem
As a developer, I'd like docs would support for local language so that I could have better reading experience.
Suggested solution
Create another repo to save translated docs. The translation work could leave it to contributors to do.
Alternative
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: