Thank you for opening your first PR into Matplotlib!

If you have not heard from us in a week or so, please leave a new comment below and that should bring it to our attention. Most of our reviewers are volunteers and sometimes things fall through the cracks. We also ask that you please finish addressing any review comments on this PR and wait for it to be merged (or closed) before opening a new one, as it can be a valuable learning experience to go through the review process.

You can also join us on gitter for real-time discussion.

For details on testing, writing docs, and our review process, please see the developer guide.
Please let us know if (and how) you use AI, it will help us give you better feedback on your PR.

We strive to be a welcoming and open project. Please follow our Code of Conduct.

Thanks for the PR but I think even if we were to want this, it should maybe be a separate repo or folder.

Mostly thinking of how accepting one language will invite others. While I think internationalization is important, I'm wary of us accepting/maintaining documents in languages that few to no maintainers read b/c it means we can't fully verify the translations nor be sure that we'll update the docs correctly.

Attn @melissawm b/c you've dealt w/ translation/internationalization issues.

Limited language proficiency and maintenance effort clearly speak against multi-language docs. IMHO automated translation tooling is good enough by now, so that users can translate to their native language themselves.

I agree with folks - keeping this readme in this repo will have maintenance issues, as it will be impossible to keep it up to date without sustained effort by translators. I'd invite you to join the Scientific Python translation effort if you are interested, although that involves different projects. In particular, I am in need of a (simplified) Chinese reviewer for this PR: numpy/numpy.org#456 Cheers!

@melissawm are there plans to work on Matplotlib translations as part of Scientific Python Translations? Would that be open for contributors showing interest. Is there anything the project has to do to support the translation?

To be clear, it's not a priority to me as I think people can cope with automatic website translation tools, but it would be good to know wether it's worthwhile sending interested contributors to Scientific Python Translations.

Thank you for the feedback. I completely understand the maintenance concerns. Given the large Traditional Chinese developer community, I am committed to maintaining this translation to ensure its ongoing accuracy.

Would you consider placing the translation in a docs/zh_TW folder (or similar) instead of the root directory? This would keep the root clean while still providing value to the community. If not, I'm also happy to look into the Scientific Python translation effort as suggested. Thanks!

Would you consider placing the translation in a docs/zh_TW folder (or similar) instead of the root directory?

Sorry, but I think consensus is that we'd really rather not add docs that we're unable to maintain.