-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Remove non-english docs? #27499
Comments
I prefer to keep both EN and CN, because both finished about 90%. |
I would also remove zh-cn, I doubt it's really 90% complete. Who knows how many updates are missing in it. Many PRs only update en-us, so with every one of these, it will get more inaccurate. |
I didn't even know that we have docs in other languages until a few weeks ago. I think we should keep pages like language-specific translation information, but it would be easier for everyone if we went English-only for everything else. |
We have implemented outdated translations reminder, if one page is outdated, there is a hint on top the page to notice user this translated page is outdated and he can help to update it. But I also agree we should focus on better documentations in English. |
There are exactly two viable options here:
I prefer 1. |
If we could achieve 1. it would be ideal, but that also would mean a change of our main translation system. |
Even Gitea at crowdin, only less languages have been translated completely before releases. So I don't think the tool improvement can help too much. I will chose 2 if I have to chose one between the two. And we can move other languages documents to external repositories. |
I mean, weblate brings this functionality by default. |
Since the docs repository moved as a standalone repository. I think this can be closed and new issue could be created there. |
This can de facto be marked as completed since #27530. zh-CN still exists but it also is in a reasonable state. |
Non-english docs are very incomplete/outdated in this repo, and I question whether it wouldn't be better to only offer english docs, because those are the only ones guaranteed to be accurate and complete. It is a hindrance for contribution if someone needs to update a doc in a language they don't speak.
Certain languages like de-de can be machine-translated very well. I think if we want multi-language docs, this would be a better option.
The text was updated successfully, but these errors were encountered: