wiige I see, thank you for clarifying! So I will replace "运行库" to "运行时" and I'll report back here when it's done.

@wiige Thanks very much for the translation update! I've updated the spine-unity documentation page accordingly:
https://zh.esotericsoftware.com/spine-unity

@wiige FYI: We have updated the spine-unity documentation page once more. Changes are:

• Added spine-unity getting started video to Example Scenes section
• Added section about new RenderCombinedMesh component, including references from other sections.
• Added FAQ entry about inner outlines when skeleton requires multiple materials.
• Added Shader subsection on Post-Processing Effects.
• Correction of "two-pass" vs "single-pass" in outline shader description text. Was intended differently originally, but was technically incorrect wording.

The diff can be found here:
https://diffy.org/diff/734e803ab93bd

wiige Sorry for the delay, but we have completed changing the translation of "runtime" to "运行时". Please let us know if you find any old translations that have been left out. Cheers!

@wiige Thanks very much as always for all your work! The documentation page has been updated:
https://zh.esotericsoftware.com/spine-unity

wiige I saw a youtube video was inserted to provide overview of the example scenes, shall we replace it with bilibili video(or some other video from none-network block video streaming site) for mandarin chinese user ?

Oh, yes, please, that would be great!

@wiige Thanks very much for your update and the detailed description!

wiige PS: this post mentioned the mobile bilibili player is more clean than www version, just replace player.bilibili.com/player.html to www.bilibili.com/blackboard/html5mobileplayer.html.

Thanks for the hint. We've just updated the documentation page and also replaced the player embeds with the mobile bilibili player version.

@wiige It seems that the aid=.. and cid=.. parameters are not needed, and that the following URL works as well:
https://www.bilibili.com/blackboard/html5mobileplayer.html?bvid=BV1BD4y1Y7By&page=1&high_quality=1
Omitting these parameters should make your workflow much easier.

I'm not sure what the page=1 parameter changes either, do you have any idea? Otherwise it could just be omitted as well.

We've been using:

https://player.bilibili.com/player.html?bvid=BV1Y14y1z72c

We just change the bvid parameter. Seems the new player also works:

https://www.bilibili.com/blackboard/html5mobileplayer.html?bvid=BV1Y14y1z72c

Maybe we should change all our embeds to the new player? Seems the other parameters aren't needed?

@wiige FYI: We've added one more embedded video and a short description line in front of it reading
"This video will help you with installing and using the Timeline extension package."
The video embed was already added to the Chinese spine-unity page section, so it's just the description line in front of it that's missing currently.

The diff can be found here:
https://diffy.org/diff/3904a621570b6

@wiige Thanks a lot for the translations!

As for the example JSON, I will check with Nate later as I am not sure of the correct condition (what it should be linked to).

I think I should have reflected all the translation files you provided for us, except for the spine-unity documentation, so please check the corresponding pages.
I added some minor fixes to the spine-phaser page: https://zh.esotericsoftware.com/spine-phaser
Fixed the part where the backquote(`) was not closed and the link URL was somehow the one in the English runtime guide.

However, the Spine编辑器文档列表 page may seem incomplete to you. This page was originally intended to replace only some of the translations using PHP, and the parts of the page for which no replacement code is provided cannot be replaced without creating a new page. So I created a new page for Chinese to reflect the translation you provided. In doing so, I mixed the Chinese translation originally reflected by PHP with the translation you provided. If you have any concerns, I would appreciate it if you could prepare a translation file to update it based on the current page.