• Runtimes
  • Spine Runtime 4.0 zh-CN translation

Related Discussions
...

Thank you for the translations! I should apologize I had overlooked the you planned translation of the download page for spine-unity. In order to upload your translation for this page, I think we first need to make sure that the updates are reflected automatically, so this may take some time to complete.

As for the Spine Web Player page, I have uploaded the translated file. Most of the translations look perfect, but it seems the original English text has been left in the following section, so I would appreciate it if you could check at your convenience:
Spine Web Player: 初始化Player

what a rapid response! thanks @[supprimé]
I have made rectifications about those lines you mationed above here, that's really helpful:
[attachment=0][Rectified][ZH-CN]Web Player.zip[/attachment]

BTW: I finished the Upgrade Guide at:
[ZH-CN]Spine-Unity 3.6 to 3.7升级指南 , the translation of Spine-Unity 3.6 to 3.7 Upgrade Guide

[ZH-CN]Spine-Unity 3.7 to 3.8升级指南 , the translation of Spine-Unity 3.7 to 3.8 Upgrade Guide

un mois plus tard

Thanks very much for your great work @wiige!


FYI: I have added a spine-unity documentation page section about CanvasGroup alpha fadeout:
spine-unity Runtime Documentation: CanvasGroup alpha
And I added two FAQ entries, one about CanvasGroup alpha and one about repacked skin problems.
spine-unity Runtime Documentation: Visual
I hope that these sections will help solve some issues that users are struggling with 🙂.

The diff can be found here:
https://diffy.org/diff/84bc2e92cbdc3

6 jours plus tard

just finish

[attachment=0][ZH-CN]spine-unity Runtime Documentation_CanvasGroup_alpha_and_FAQ.zip[/attachment]

7 jours plus tard

Thanks very much as always for your work! :yes: We've updated the page.
spine-unity 运行时文档


FYI: I have added a few more spine-unity documentation page hints. They explain that when using UPM packages via git URLs, it is necessary to copy the example scenes to the Assets directory since it can't be opened otherwise.

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

Harald a écrit

Thanks very much as always for your work! :yes: We've updated the page.
spine-unity 运行时文档


FYI: I have added a few more spine-unity documentation page hints. They explain that when using UPM packages via git URLs, it is necessary to copy the example scenes to the Assets directory since it can't be opened otherwise.

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

Updated:[attachment=0][ZH-CN]spine-unity Runtime Documentation_UPM packages via git URLs.zip[/attachment]

Wow, that was quick, thanks very much as always! 8)
We have updated the documentation page with your changes:
spine-unity 运行时文档

25 jours plus tard

there is the translation of Binary export format (100%) in the upper ToDoList.
post here cause I reached the limitation of attachment number which is 8

[attachment=0][ZH-CN]Binary export format.zip[/attachment]

and thanks again for your rapid update

Thank you so much for the translation! I have uploaded the translated file and you can see it here:
Spine: 二进制导出文件格式

I did a quick check and it looks perfect. Not only was the translation good, but also the tags were correct. We really appreciate all your efforts!!

Thanks so much for your great work! 8)


FYI:
A new parameter Unscaled Time was added at SkeletonAnimation and also at Spine Timeline Tracks (on the 4.1-beta branch).
So a line was added to the spine-unity documentation for the track property, and another line was moved from the SkeletonGraphic to the SkeletonAnimation section (since it's a common parameter in 4.1 for both components now).

The diff can be found here:
https://diffy.org/diff/58174def23cc1

Harald a écrit

Thanks so much for your great work! 8)


FYI:
A new parameter Unscaled Time was added at SkeletonAnimation and also at Spine Timeline Tracks (on the 4.1-beta branch).
So a line was added to the spine-unity documentation for the track property, and another line was moved from the SkeletonGraphic to the SkeletonAnimation section (since it's a common parameter in 4.1 for both components now).

The diff can be found here:
https://diffy.org/diff/58174def23cc1

translation of spine-unity documentation updated:
[attachment=0][ZH-CN]spine-unity Runtime Documentation_Unscaled Time.zip[/attachment]

9 jours plus tard

Great, thanks very much for your work! 🙂

10 jours plus tard

I found some incorrect translations at Binary export format and JSON export format about description of

softness: A value for two bone IK, the distance from the maximum reach of the bones that rotation will slow. Assume 0 if omitted.

while I working on API Reference. (in order to align with API Reference)

so I put the update here:
[attachment=3][Updated][ZH-CN]Binary export format.zip[/attachment]
[attachment=2][Updated][ZH-CN]JSON export format.zip[/attachment]

BTW, 70% of API Reference are translated. It's sooooooo long and hardly make it 0 slip-up I guess.
if everything went right 😢 , the .md file of complete API Reference translation will be there before July.
API Reference Chinese Translation is based on API Reference but not beta version.

original API Reference markdown file that my translation used:
api_reference_original.zip

here is the semimanufacture(70%), and again, proofreading needed:
[attachment=1][in_progress][ZH_CN]API reference.zip[/attachment]

Thank you for fixing the translation and translating the API Reference!

The corrections have been uploaded:
Spine: JSON导出文件格式
Spine: 二进制导出文件格式

Regarding the API Reference translation, I know it is not completed but I uploaded the current translation and checked the contents:
API Reference - Spine Runtimes Guide

The API Reference is a particularly demanding document in terms of accuracy, so I checked for missing or incorrectly named properties, methods or parameters, and found no such problems. I know this page is very difficult to translate because it's no markdown, but it's wonderfully accurate! However, I found some obvious mistakes, such as some English letters left or the same property written twice, so I corrected those. If you could continue working on the translation, please proceed with the attached file:
spine-api-reference-zh.zip

I just finished the translation and pleasantly surprised to see the correction you posted,
so I did a quick merge with mine, here is the beta version:

[attachment=0][100%][ZH_CN]spine-api-reference-zh.zip[/attachment]

I have to say your quick response help a lot :grinteeth: :grinteeth:

Great, thank you for completing the translation so quickly! 😃 I have updated the API reference page and would appreciate it if you could check if everything is OK:
API 参考文档 - Spine Runtimes Guide

I made a fast scan about the sentences leaving in English or the Chinese translation mix with original English lines, :think: and found some typos:

and the updates is here:
[attachment=0][updated][ZH_CN]spine-api-reference.zip[/attachment]

After those check I think it's stable now, it looks good to me. :detective:
Still, the translation is free to use,
notify me if any inappropriate found in this translation, I will rectify as soon as possible.