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 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 Thanks very much for your quick and thorough update! We've updated the spine-unity-download page accordingly.

@wiige Thanks for the quick translation, that was very fast! ️ We've updated the spine-unity documentation page accordingly.

wiige Thanks for translating the remaining pages of the General Runtime Guide! I updated the pages with your translation and it seems perfect, including the links. Thanks for your contribution!

wiige Thank you for your prompt response! I have updated the Chinese spine-godot documentation. Your support has always been invaluable to us and many Chinese users. We truly appreciate it!

@wiige FYI: We've just added a documentation section for a recently adde RenderExistingMeshGraphic utility component (a SkeletonGraphic variant for RenderExistingMesh). I've already added an analogous Chinese translation here:
https://zh.esotericsoftware.com/spine-unity-utility-components#RenderExistingMeshGraphic
If I made a mistake there with the translation, please let me know.

wiige Thank you so much! I updated it with your translation:
https://zh.esotericsoftware.com/spine-godot

@wiige We have recently split the spine-unity documentation page into multiple pages, and improved the documentation in the installation section since we noticed it was not so clearly structured and missing a few things.

I've created a step-by-step guide on what best to change in which order with links to diffs (and commit URLs, which unfortunately reference a private repository and only serve the purpose so that we later know which change was which). I hope that the guide helps keeping the work as minimal as possible, please let me know if anything is unclear or confusing. I've also uploaded the relevant .md files in case that helps (link see the notes txt file below). In general there should not be much to translate (except for additions in the Installation section), mostly moving text around to the right places, and updating cross-references.

It would be great if you could also split and update the Chinese spine-unity page in the same way. Thanks again for all your hard work!

wiige Thank you for your thoughtful suggestion! We have considered the same thing and looked into it, but have not yet found the best way to use it with our CMS.
Whatever method we use, it will probably not be public outside of our team, but at least if I can track the updates properly, I will be able to contact you in a more efficient way.
We don't want to put any additional burden on you, so we would appreciate it if you would wait until we can prepare a proper procedure.

wiige Thank you! I have updated the page: https://zh.esotericsoftware.com/spine-runtime-documentation

This is in response to your message to Harri, but there is currently no consistent way to check for differences. Now that 4.2 has been released, I think the user guide should need a major update and translation soon, so I hope to be able to confirm the management way of easily found differences in the Spine team at that time.

Fixed! It seems that the problem was caused by converting the part that originally used half-width spaces to full-width spaces.

wiige Thank you for the clarification! Sorry, apparently I had left the previous zip on my local, and I had mistakenly unzipped it and misunderstood. What you have translated is correct! The JSON export format page is updated: https://zh.esotericsoftware.com/spine-json-format

Thanks very much for the update @wiige! We've updated the documentation page with your changes.

I cannot visit markdown text with /markdown at spine-godot Runtime Documentation while API 参考文档 works well

Perhaps the problem is just the added section anchor #spine-godot-Runtime-Documentation, as the following URL does not provide markdown for me:
https://esotericsoftware.com/spine-godot#spine-godot-Runtime-Documentation/markdown
while this URL does:
https://esotericsoftware.com/spine-godot/markdown

The /markdown URLs are working for me. Maybe it was fixed since you reported it.

That like should be: http://esotericsoftware.com/spine-points
We'll fix it, thanks!

As always, thank you for the updated files!

@wiige FYI: We have just added a single line of example code to the Chinese spine-unity page here, as it was missing in the first skins example code block:

skeletonAnimation.AnimationState.Apply(skeletonAnimation.Skeleton); // skeletonMecanim.Update() for SkeletonMecanim

Just that you know to get the latest version before making any updates yourself.

Great! I have updated the Spine运行时文档 page with the latest translation:
Spine: 运行时文档

Also, I have confirmed all the links on the spine-ue4 and spine-cpp documentations. Every link should be working correctly now.

新年快乐！