wiige Great, I reflected your translation and it looks perfect!: https://zh.esotericsoftware.com/spine-sdl
Thank you for always being willing to help!

@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 I would like to inform you that the documentation page for the Spine Web Player has been updated. For now, the corrected or added sections have been replaced with English text:
https://zh.esotericsoftware.com/spine-player#%E5%A4%A7%E5%8A%9F%E5%91%8A%E6%88%90

For some reason, the diff didn't load properly on diffy.org, so I've uploaded the differences here:
https://www.diffchecker.com/WrCxqkdc/
(Most of the updates are code updates, and the only updates that require translation are the "JSON, binary, and atlas URL" section and the "Embedding data" section.)

@wiige Sorry for the troubles! I've compiled a set of .diff files, each stepN.diff file corresponds to one commit of the respective step in the notes-spine-unity-split.txt file.

For example VS Code should be able to display the diff properly as +- inline changes as other diff viewers (like TortoiseUDiff for example).

wiige Thank you for the translation! The new translation has been reflected on the spine-player page.

Hi, @wiige. I just wanted to let you know that we have released the spine-ios documentation:
https://esotericsoftware.com/spine-ios

@wiige Thanks very much for your great work, no hurry at all of course! We're really glad that you took on this task!

You are the hero my friend.

@wiige Thank you so much for all your translations! Your translations have been reflected in the documentation for spine-unity, spine-flutter, spine-phaser, spine-godot, and spine-ue.

I fixed the links that weren't working for spine-unity, but as you say, the API documentation also needs to be updated, and the links for the APIs that have been renamed still don't work.

The main updates to the API documentation are the renaming of some APIs, which are also included in the upgrade guide from spine-unity 4.1 to 4.2 that you previously translated for us, and the addition of physics-related sections.
I'm sorry that I can't provide a diff file for this page because it's managed differently, but basically there shouldn't be any changes other than the ones listed above.

The translation of the spine-unity documentation was almost perfect (it's amazing how accurate it is!), but there were still some sections that were left in English. Please check the "Writing your own shaders" section on the Rendering (渲染) page:
https://zh.esotericsoftware.com/spine-unity-rendering#Writing-your-own-shaders

PS: I can not access spine-pixi doc on https://esotericsoftware.com/spine-pixi now, was it removed?

Sorry for the trouble! I guess the reason spine-pixi was hidden was that we were considering changing the repository configuration to add PixiJS v8 support. For now, it has been re-displayed, but the URL may change later.

Thank you for your efforts in creating consistent translations! It's been a great help.

@wiige Thank you so much for the big update and all your great work!
Really glad to see the new updated Chinese spine-unity documentation in place!

wiige Misaki thanks for your meticulousness! I have re-uploaded the revised document of Rendering section of spine-unity documentation to rectify omission paragraphs:

Thanks for the super quick update, we've updated the documentation page accordingly!

@wiige We've added some changes to the English spine-unity-main-components page very recently (I assume it's not part of your latest spine-unity translations yet):

Added Script Execution Order and Manual Update sections to spine-unity-main-components.

1) Moved the simple code section starting with #### C# # Interacting with a skeleton via code requires [..] up. This makes the lower part of the diff a bit hard to read, ignore these in the diff, just move it up.
2) Added section #### Script Execution Order and ``#### Manual Updates, completely new sections, ignore old part of diff. Ends before section# Skeleton`.
3) A few wording sections changed. This is where the diff is helpful, when a sentence is changed. Here the diff shown by diffy.org is a bit clearer.
4) Removed the sentence "For more information on Unity's MonoBehaviour Lifecycle, see: .."

Diff:
https://diffy.org/diff/52209b4c97a84

I've also added another very small documentation addition a moment ago to the spine-unity-main-components page (SkeletonMecanim Mix Mode Match):
Diff:
https://diffy.org/diff/92bb88cf7e5e7