Misaki thanks for your meticulousness! I have re-uploaded the revised document of Rendering section of spine-unity documentation to rectify omission paragraphs:
spine-unity-rendering.zip
14kB
Spine Runtime 4.0 zh-CN translation
@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
Harald done with Script Execution Order update of spine-unity document at:
spine-unity-main-components.zip
24kB
and this is the translation of spine-haxe:
spine-haxe.zip
8kB
and a revised version of spine-phaser which correct multiple typos:
spine-phaser.zip
9kB
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
6 Tage später
Misaki this is translation update of:
spine-phaser
spine-phaser.zip
9kB
spine-flutter.zip
10kB
and spine-canvaskit:
spine-canvaskit.zip
7kB
as for spine-pixi, please notify me when PixiJS v8 support added, will try to translate the latest doc. Now I am working on the update of API document, adn it might take a considerable amount of time, so please be patient as well, thx
wow, spine-android found, added to my to-do list
I have corrected some of the links in the spine-canvaskit documentation, but other than that there seemed to be no problem. Thanks again!
Some of the documentation, such as the spine-android documentation, is not yet linked from the Spine Runtimes page, but we are actually planning to revise that page, and links to the documentation will be properly added at that time.
5 Tage später
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!
Misaki ohhh, I see
I paraphrased "Previous" to "Last Chapter(上一章)" and "Next Chapter(下一章)" cause I couldn’t come up with a more concise a translation for ‘Previous’ in this context.
and, 下一节 = next section , 上一节 = last section.
so how to determine the translation of these two words depends on how you view the document structure, that is, whether each page is an independent chapter (which is what I assumed when translating).
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 "下一节: / 上一节:".
21 Tage später
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
Misaki pleasure! the minor update of Skeleton Viewer here:
ZH-CN-skeleton-viewer-startup-method-update.zip
3kB
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.)