wiige Thank you for the translation! Harald has not confirmed it yet, but based on my research, I believe that the term "懒加载" is commonly used, so I went ahead and included it.
I also removed some remaining English text, changed some links, and changed the notation in some places where it was necessary for the sake of the heading links. (I changed it because the heading links would be confusing when the same text appeared in different sections.)
I would appreciate it if you could check to make sure there are no problems: https://zh.esotericsoftware.com/spine-unity-on-demand-loading

@wiige Thanks very much for translating the page, much appreciated as always!

wiige note that I translated "On-Demand Loading" as "懒加载/惰性加载" which is Lazy Loading, by my understanding to the doc, because "按需加载"(literal translation) is not a customary expression in Chinese.
are they equivalent? I need an unity expert @Harald

Yes, the terms are equivalent. Thanks for translating it in the most suitable way.

wiige Thanks, we've just updated the sentence on the page accordingly.

wiige Thank you very much for offering to translate the user guide! However, the reason why this page has not been translated into Chinese is because the original English version is still a work in progress. We would appreciate your translation, but please be aware that there may be significant changes in the future. (We apologize for the long delay in updating the user guide.)

wiige I found several mistanslations at https://zh.esotericsoftware.com/spine-unity-download, will rectify them and post here with physics-constraints guide

@wiige Oh, thanks for letting us know! As the spine-unity-download page is generated, might I ask you if you could directly modify the template instead of the generated result page:

@wiige Thanks very much for your quick and thorough update! We've updated the spine-unity-download page accordingly.

@wiige Thanks for asking, sure!

Please note that this page is directly edited, it's not generated from a template like the spine-unity-download variants. At the download pages we generate the content to keep the current download URLs and version numbers in sync.

@wiige BTW: Now would be a rather unstable time to update the API translation, as with the 4.3-beta runtime changes rather large parts of the documentation have changed, and the respective documentation is not up to date yet. The changes affect mainly everything related to bone poses, transforms and applied transforms and constraints. So please do not put any effort into syncing these sections yet.

wiige Harald I seeeeeee........ that means I'd better wait for 4.3-stable and this attachment is exactly same as https://zh.esotericsoftware.com/spine-api-reference/markdown, right?

Yes, it's just the markdown (with some additional header which is irrelevant though)! I assumed that maybe the /markdown functionality was broken and you could no longer access it.

wiige then may I ask a diff of spine-api-reference when the api reference is ready for 4.3 stable? thanks in advance

Sure, we'll let you know!

@wiige FYI: We've added and modified a few lines of the spine-unity-assets documentation page. The main issue was that there was an incorrect statement regarding the Advanced - Apply Additive Material SkeletonDataAssets setting, which stated PMA atlas texture workflow instead of PMA Vertex Color. This is now corrected. Also some Spine Preferences settings were added.

The diff can be found here:
https://diffy.org/diff/95bb093604a13
It would be great if you could again mirror the changes to the Chinese page.

wiige Thank you for your prompt translation! I have updated the Chinese documentation page.

By the way, the design of the Spine Runtimes page has recently been updated, and these changes have been reflected on the Chinese page. The explanatory text has been carried over from the previous version. Please let us know if you notice any issues:
https://zh.esotericsoftware.com/spine-runtimes

wiige Thank you for pointing out the broken link! I have asked the team to fix it.

spine-android has actually been around for quite some time, but I apologize for not sharing it with you earlier. spine-glfw and spine-webcomponents were added relatively recently, and we have not yet announced their release. The documentation may still be updated, so if you plan to work on them, it may be better to start with spine-android, which is relatively stable. Thank you for your cooperation!