@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

wiige Thank you for your quick response! The translation has been applied to all three pages:
https://zh.esotericsoftware.com/spine-unity-main-components
https://zh.esotericsoftware.com/spine-haxe
https://zh.esotericsoftware.com/spine-phaser

@wiige Thanks very much for your quick update! Much appreciated as always!

wiige Thanks for the translation! I have reflected the contents of the three translated files.
I have not yet checked all the links on the spine-canvaskit page, so I will check it tomorrow.

wiige Sorry for not addressing this part! It's not something that can be done from the markdown, so please wait until we're done.

wiige We have checked to see why the link is not being added properly, and it appears to be due to a change in the translation of "Previous:" and "Next:" on the Chinese page. Other documents in Chinese (e.g., general runtime guide and user guide) use "下一节: / 上一节:" , but the spine-unity runtime documentation uses "下一章: / 上一章:" , which seems to be causing the detection to fail.
If there is no particular reason why this should be the case, I would like to use "下一节: / 上一节:" to match the other documents. Do you think we should use "下一章: / 上一章:", including the other pages? Let me know your opinion!

wiige Thank you for explaining in detail! From your description, it sounds like it would be better to use "下一节: / 上一节:", as each page of the spine-unity documentation is structured to be followed by content that assumes that the previous section has been explained, rather than completely independent content. So I'll change it to "下一节: / 上一节:".

Hi, @wiige. We recently added a section to the Skeleton Viewer documentation that mentions how to run it from the trial version, but I now realize that the Chinese documentation seems to have been outdated for quite some time. I apologize for not being able to provide a clear diff file, but I have added the missing section in English and hope you will check it out when you have time:
https://zh.esotericsoftware.com/spine-skeleton-viewer

wiige Thank you for your very quick response! I have updated the Chinese page with the translation you provided and it looks perfect:
https://zh.esotericsoftware.com/spine-skeleton-viewer

Hi, @wiige!
Yesterday we released the spine-pixi-v8 runtime and with it a major update of the spine-pixi documentation: https://esotericsoftware.com/spine-pixi

So we would be grateful if you could translate it when you have time.
(Incidentally, the runtime page has not yet been updated, but this documentation can be accessed via the spine-pixi-v8 release blog.)