Add zh version of README

[windsonsea]

Sync with the current README.md. Hope this action can:

• trigger more localization versions, PR, and issues come.
• create a basic style for localization variants

[musvaage]

cf: #641 (comment)

manageable as it is limited in content

cf: #687 (comment)

ill advised to have much foreign language content

Recently I've opened #729, which would add an .rst formatted file.

I like segregating the original English in an .rst file, with provision of translations thereof relegated to a .pod file.

For this purpose a TRANS.pod file could be created, where TRANS is short for TRANSLATION.

[windsonsea]

Hi @musvaage , thanks for your advice.
However, I'm not very understanding why you use the complicated journey? Could we make it simple and easy to get by all contributors?

[musvaage]

cf: #729

The rendering on GH of .pod unlike the current .rst has the capability to include html content above the first section.

The file INTRO.rst is a suggested but optional additional file.

In README.md presently is an excerpt from the Technical Report Introduction section.

It wouldn't surprise me were INTRO.rst added that PRs will be submitted to "improve" the English language therein. Such potential users prior to opening these hypothetical PRs wouldn't take the time to read the Technical Report. So INTRO.rst would remain untouched, PRs outright rejected owing to its content derived from the Technical Report. On the other hand translations of the Technical Report Introduction section could be supported or unsupported by the core developers, and appear in a top level TRANS.pod file. But maintaining that file would not be a high priority for the core developers, consequently not a burden on their current work schedules; where maintaining numerous full translations of the current markdown format files would be construed as a burden on such work schedules.

Please be mindful that the foregoing is my opinion and might not be representing the consensus of the developers.

[musvaage]

I don't find any reason for this in the translation; indeed throughout the file ## (H2) was rewritten as ### (H3).

+ ### 4. 评估结果
+ 
+ #### 基础模型
+ 
+ ##### 标准基准测试

[windsonsea]

Hi @musvaage, please do not push, call, or ask any more relevant changes before #729 gets merged, which may cause extra cost to study and learn if it's failed to be merged.

Note:

• You can add specific comments by clicking + in front of any line.
• If you have any proposal like above mentioned, please open an issue to discuss.

[musvaage]

Ubiquitous are browser offers of generated translations.

The GH user hasn't been outgoing in presenting information on whether or not this PR's content was created manually.

That is pointed out as feasibly a given repo's Maintainers might be disinclined to support a generated translation.

The above noted some repos do factually provide top-level and/or subdirectory README file translations.

https://github.com/bytedance/sonic

README.md
README_ZH_CN.md

The above files don't have a logo and badges, where absent such content at the top is a translation list and hyperlink.

Please be mindful that the foregoing is my opinion and might not be representing the consensus of the developers.

---

DeepSeek_V3.pdf

The above file is no longer part of this current repository.

So, the INTRO.rst, would have provided additional readily accessible information.

PR #729 adding INTRO.rst I have now closed due to age.