Этот сайт лучше всего просматривать в современном браузере с включённым JavaScript.

Spine Runtime 4.0 zh-CN translation

Harald

wiige Great to hear that it hasn't been too annoying, thanks very much for you update!
We've updated the documentation page accordingly.

wiige i noticed that * show up now, shall I reformat the entire documentation ? I have replaced them with - for alignment.Please let me know if it's better to correct that. 🙂

The dashes look perfectly fine and the result seems to be the same, so no need to reformat anything. But thanks for the offer! 🙂

wiige

Misaki no problem! feel free to remind me the update of document. I am glad to help the community as always~

ZH_CN_spine-ue4-ur53notice.zip

10kB

Misaki

wiige Great, thanks for always responding so quickly! I uploaded the translated file and it looks perfect! 🙂 https://zh.esotericsoftware.com/spine-ue4

wiige

a render error found on page Amplify-Shader-Editor

is it just my browser problem, or page was broken?

Misaki

wiige Thanks for reporting the issue! That section was actually broken, so I tried to fix it, and while it was an improvement over what you reported, I noticed that for some reason I could not display that part correctly in the same way as other language pages, even when I copied and pasted the same text. I will look into it later.

I will reflect the updates in the Phaser and Flutter docs!

wiige

here are updates of page:
spine-phaser

spine-phaser-typo-update.zip

9kB

and
spine-flutter

spine-flutter-typo-update.zip

9kB

Misaki

Fixed! It seems that the problem was caused by converting the part that originally used half-width spaces to full-width spaces.

Misaki

Hi, @wiige . We have updated the documentation for the spine-ue runtime and could use some help updating the Chinese page. I have already updated part of it, but I would like you to help update the "导出虚幻引擎可用的资产", "导出Unreal-Engine-5.3资产", and "将资产导入虚幻引擎" sections.

The changes are as follows:
<Update completed>

Changed the runtime name from "spine-ue4" to "spine-ue".
Removed the link to the section on exporting for UE5.3 from the "安装运行时" section.

Merge the "导出Unreal Engine 5.3资产" section to the "导出虚幻引擎可用的资产" section.
Add "将资产导入虚幻引擎" section to indicate that .atlas files should also be selected for import.

Here is the file for the current Chinese documentation:

spine-ue4-zh.zip

10kB

Sorry I didn't save the differences in a simple format. I would appreciate it if you could update it based on the current English documentation: https://en.esotericsoftware.com/spine-ue4
Thank you in advance!

wiige

Misaki

zh-cn_spine-ue.zip

10kB

please check if any section or sentences I have missed ~
I guess you also need to modify spine-runtime-documentation cause it's still using the name ‘spine-ue4’, lol

Harald

@wiige FYI: We have improved the spine-unity documentation page some more to explain the SkeletonGraphic parameters of the Advanced section more precisely, i.e. which settings are required under which circumstances. Also, the documentation now mentions the recently added Detect buttons which have been added to automatically assign the correct settings and the correct material. I'm sorry to say that the sections are a bit long since they mention correct settings for both spine-unity 4.2 vs 4.1-and-older, nevertheless we hope that this provides less frustration in the end.

The complete diff can be found here:
https://diffy.org/diff/b903e51a8c3dc
As always, it would be awesome if you could again provide us with a Chinese translation. 🙏

Misaki

wiige Thank you for the translation! I thought it was perfect and have reflected it:
https://zh.esotericsoftware.com/spine-ue

The spine-runtime-documentation page has also been modified! Also, at the time I asked you, the URL was still "spine-ue4", but that has been corrected to "spine-ue" as well. 🙂

wiige

Misaki nice of you, now I have an update of Spine运行时列表, changes come from:

Add 'spine-phaser' as item
fix some sentence fluency problems

zh-cn_spine-runtime-list.zip

1kB

Harald

@wiige FYI: We have also just published the new spine-unity 4.1 to 4.2 Upgrade Guide on the forum:
https://esotericsoftware.com/forum/d/26006-spine-unity-41-to-42-upgrade-guide

The markdown text is as follows:

forum-upgrade-41-42.txt

3kB

Most of it remained unchanged compared to previous Upgrade Guide with just the version numbers changed. A diff can be found below, in case it helps:
https://diffy.org/diff/0c0b4ea7e6fa7

wiige

Harald thanks so much for your detailed explanation! the markdown text was helpful on format alignment as always 🙂

I had posted the Upgrade Guide at here and working on spine-unity documentation update.

your diff file is highly effective on locating documentation changes, is there any unified way I can track other documentation changes like spine-phaser 运行时文档 or spine-godot 运行时文档?

Harald

@wiige We've also updated the version numbers on the spine-unity documentation page accordingly for 4.2 and added a line to the current English Upgrade Guide here. So if you didn't start any translation yet, please be sure to get the latest update first. In case you already started any translation, don't bother integrating the changes yourself, I should be able to quite easily merge them automatically via git.

wiige

Harald
this is the latest 4.2 update based on latest spine-unity 运行时文档

zh-cn-spine-unity-doc-42-update.zip

63kB

Harald

wiige I had posted the Upgrade Guide at here and working on spine-unity documentation update.

Awesome, thanks very much!

wiige your diff file is highly effective on locating documentation changes, is there any unified way I can track other documentation changes like spine-phaser 运行时文档 or spine-godot 运行时文档?

Very glad it helps! I created the diffs the following way, using git-bash when using Windows:

Create a directory for the documents to be tracked.
git init . to create a simple local git repository at this directory.
Create your document file like spine-unity.md and paste the current page content in it.
git add spine-unity.md and git commit the addition.
Then after modifying the document, again git add spine-unity.md and git commit the changes.
Then use git to view the diff between versions. I used git diff @~1 @ | clip to copy the diff between the previous (@~1) and the last commit (@) to the clipboard, then I paste it at https://diffy.org to share it with others.

I've shared the precise steps in case it helps others.

Misaki

wiige Thank you! I have updated the page: https://zh.esotericsoftware.com/spine-runtime-documentation

This is in response to your message to Harri, but there is currently no consistent way to check for differences. Now that 4.2 has been released, I think the user guide should need a major update and translation soon, so I hope to be able to confirm the management way of easily found differences in the Spine team at that time.

wiige

Harald Misaki Given the large volume of text in there documents, is there a convenient way to track text changes across multiple different web pages? This would allow me to start translating promptly. For instance, a git project dedicated to document translation or even an RSS feed. My goal is to be automatically notified when a web page changed, and then provide translations for the modified content. It’s quite taxing to read through all the runtime documents each time. :}

wiige

Harald thanks for your detailed step-by-step tutorial. It was very helpful and easy to follow.
but I am using Powershell and it report:

 # git diff @~1 @ | clip
At line:1 char:10
+ git diff @~1 @ | clip
+          ~
Unrecognized token in source text.
At line:1 char:14
+ git diff @~1 @ | clip
+              ~
Unrecognized token in source text.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : UnrecognizedToken

so I turned to git show e3211778 > 4.2_diff.output and pasted it here, hope it can be use:
4.2_diff.output

This is the 4.2 update of spine-unity 运行时文档 based on outdated page:

zh-cn-spine-unity-documentation-4-2 update.zip

63kB

Misaki

wiige Thank you for your thoughtful suggestion! We have considered the same thing and looked into it, but have not yet found the best way to use it with our CMS.
Whatever method we use, it will probably not be public outside of our team, but at least if I can track the updates properly, I will be able to contact you in a more efficient way.
We don't want to put any additional burden on you, so we would appreciate it if you would wait until we can prepare a proper procedure.

wiige

Misaki sure! will keep waiting

« Предыдущая страница Следующая страница »