Add Simplified Chinese Translation | 增加简体中文翻译

[DaZiDian]

No description provided.

[ChampionAsh5357]

Hello! You are welcome to localize the files; however, you must do so according to docusaurus's internationalization format. The main files should not be touched.

Are you doing this as supersede to #19?

Also, I will warn you that this will take a while to review as we do not have a localization team at the current moment.

[DaZiDian]

Dear NeoForge Team: Hello. I am an independent localization translator. After seeing your reply, I have a general understanding of the current problems. I will correct them as soon as possible. Please forgive me. I am still a high school student and do not have too much time to participate. This matter, but I will try my best to solve it as quickly as possible. For #19, I should focus more on promoting the progress of localization translation. I will contact the fork author and discuss it. As you know, the Minecraft community in China is very large, and we all aim to promote the development of the Minecraft community. I apologize for the inconvenience caused by my team. Thanks.

…

________________________________ 发件人: ChampionAsh5357 ***@***.***> 发送时间: 2024年5月8日 21:43 收件人: neoforged/Documentation ***@***.***> 抄送: DaZiDian ***@***.***>; Author ***@***.***> 主题: Re: [neoforged/Documentation] Add Simplified Chinese Translation | 增加简体中文翻译 (PR #67) Hello! You are welcome to localize the files; however, you must do so according to docusaurus's internationalization format<https://docusaurus.io/docs/i18n/introduction>. The main files should not be touched. Are you doing this as supersede to #19<#19>? Also, I will warn you that this will take a while to review as we do not have a localization team at the current moment. ― Reply to this email directly, view it on GitHub<#67 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A26YYOHIZOXGMPA2QZWYZ43ZBITYVAVCNFSM6AAAAABHMQ2YH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBQGYYTCMRWGE>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[DaZiDian]

Dear NeoForge Team,

I hope this message finds you well. I am writing to inform you that I have recently completed revisions on a set of documents, meticulously aligning them with the general guidelines outlined in Docusaurus' Internationalization (I18N) documentation, which can be theoretically found at https://docusaurus.io/docs/i18n/introduction. Regrettably, it appears the specific page may currently be unavailable, though the framework's overall instructions have been my guiding light throughout the process.

My efforts focused on ensuring the content is primed for seamless translation and localization, adhering to best practices for multilingual support as detailed by Docusaurus. This included, but was not limited to, updating metadata, preparing translation files, and verifying compatibility with various language configurations.

I kindly request your team to review the modifications I've made. Your expert eyes will undoubtedly spot any discrepancies or areas for improvement that might have escaped my notice. Your feedback is invaluable in ensuring our documentation meets the highest standards of international accessibility and user experience.

Please let me know if there is a preferred method or platform for submitting these revised files for review. I am also more than willing to walk through the changes with someone from your team if that would facilitate the process.

Thank you in advance for your time and consideration. I am looking forward to your insights and further collaboration in enhancing our global users' engagement with our documentation.

[ChampionAsh5357]

After discussing translations with some of the other members, we ended up determining we do not have the capacity and the infrastructure to accept translations to other languages. It would be difficult to validate the quality of the PR and keep it maintained without a dedicated team or review process. We have discussed other solutions such as third party links or Crowdin translations, but those have the same issues with validation and infrastructure that we are not yet set up to handle.

We will be revisiting translations in the future once we have more team members that can take off some load from our existing team and some more stable infrastructure, however. So, until then, we will keep this PR open. We would also like to ask if you could mark this as a draft since the documentation will likely be updated many times before we can get around to revisiting this topic.

Thank you for the contribution, and apologies for the inconvenience.