• Runtimes

  • Spine Runtime 4.0 zh-CN translation

Related Discussions
...

Thanks very much for your super quick translation work once again! :fiesta: 8)
I've updated the page with your content accordingly:
spine-unity 运行时文档

unified diff of the last two diffs do great help, thanks！

Strangely I don't see the translation part of the first commit (which was included in the unified diff), did you perhaps send us the wrong file?
https://diffy.org/diff/719f261817f03
Anyway, it's just a minor addition that is not so important.

I also noticed that for some reason the cross-section links like e.g.

[link text](从Spine导出文件到Unity)

as I've added for testing are behaving strangely on this single page: they don't scroll to the selected heading as they should, but when opening the link in a new tab it works as intended. I will see what we can do about it.

Do you also see the same behaviour with the first link in this section here reading 从Spine导出文件到Unity.:
spine-unity 运行时文档: 导入问题
Or is it working in your browser, scrolling to the right section? At least for us using Firefox or Chrome it does not scroll unfortunately.

appreciate for your chariness! I compared the present translation for Spine/Sprite/Pixel Lit and Universal Render Pipeline/Spine/Sprite with diffs, the excrescent sentences The only shader that receives per-pixel realtime shadows. and Receives per-pixel realtime shadows. had been purged.

As for the strange behaviour of in-page cross-section links, I do have the same trouble. Click the link of 从Spine导出文件到Unity do not scroll to the right section.

Screen_2022-08-05_00-01-34.zip

if the suffix of link (#从Spine导出文件到Unity) caused encoding problem? my edge browser show the URL like this:

http://esotericsoftware.com/spine-unity-zh#%E4%BB%8ESpine%E5%AF%BC%E5%87%BA%E6%96%87%E4%BB%B6%E5%88%B0Unity
wiige wrote

I compared the present translation for Spine/Sprite/Pixel Lit and Universal Render Pipeline/Spine/Sprite with diffs, the excrescent sentences The only shader that receives per-pixel realtime shadows. and Receives per-pixel realtime shadows. had been purged.

Oh I see, sorry, I didn't notice that the initial diff I have posted was in the wrong order of commits (I've confused "diff @~1 @" with "diff @ @~1"), so it incorrectly showed addition as removal :wounded: . The unified diff showed the sentences correctly as added.

As for the strange behaviour of in-page cross-section links, I do have the same trouble. Click the link of 从Spine导出文件到Unity do not scroll to the right section.

Thanks for testing the link with your browser, good to see this issue confirmed.
[Edit:]
Misaki pointed out that references on the Japanese spine-unity page require an additional prefix to work for strange reasons: when adding /spine-unity in front (/spine-unity#从Spine导出文件到Unity) it works as intended. So the format /spine-unity#heading-title shall be used for cross-section references from now on. 🙂
For example, a markdown link in the .md file will look like this:

[从Spine导出文件到Unity](/spine-unity#从Spine导出文件到Unity)

And with full text

请确保你的atlas文件的扩展名为`.atlas.txt`而非`.atlas`. 详见[从Spine导出文件到Unity](/spine-unity#从Spine导出文件到Unity).

Nice ! I left cross-section links untouched when I translated spine-unity documentation before. It may take more time and patient to allow me correct every link so that they can locate the right section. It will be upadted ASAP. 😃

Misaki pointed out that references on the Japanese spine-unity page require an additional prefix to work for strange reasons: when adding /spine-unity in front (/spine-unity#从Spine导出文件到Unity) it works as intended. So the format /spine-unity#heading-title shall be used for cross-section references from now on.

here is an uncertainty perplex me: Japanese spine-unity page can be accessed by both spine-unity-ja URL and spine-unity URL, and own multiple variations of cross-section links:

「[マテリアル](#%E3%83%9E%E3%83%86%E3%83%AA%E3%82%A2%E3%83%AB)」

,

[Unity向けのバイナリエクスポート](/spine-unity-ja#Unity向けのバイナリエクスポート)

and

「[SkeletonGraphicコンポーネント - CanvasGroupアルファ](/spine-unity#CanvasGroupアルファ)」

, they locate sections correctly , scrolling well.

So, what's the proper form of those links allow them work as intended? And please let me know which one can be the best style ? :

[从Spine导出文件到Unity](/spine-unity#从Spine导出文件到Unity)
[从Spine导出文件到Unity](/spine-unity-zh#从Spine导出文件到Unity)
[从Spine导出文件到Unity](/spine-unity-zh#%E4%BB%8ESpine%E5%AF%BC%E5%87%BA%E6%96%87%E4%BB%B6%E5%88%B0Unity(Character In Hex byte with GB2312))

Looking forward to your advices sincerely :think:

:derp: minor update for per-pixel realtime shadows notification:
[attachment=0][Update]spine-unity-zh_CN-per-pixel_realtime_shadows.zip[/attachment]

Thanks @wiige for all your efforts! Your latest changes have been integrated:
spine-unity 运行时文档

wiige wrote

So, what's the proper form of those links allow them work as intended? And please let me know which one can be the best style ? :

Please use the style without the -zh suffix, so please use this one (first in your list):

[从Spine导出文件到Unity](/spine-unity#从Spine导出文件到Unity)

The -zh or -ja suffix references should actually never be used anywhere, we have corrected the Japanese translation. Thanks for reporting!

Nate wrote

@[deleted], please check your email. 🙂

sure! :grinteeth: :grinteeth:

Harald wrote

Please use the style without the -zh suffix, so please use this one (first in your list):

[从Spine导出文件到Unity](/spine-unity#从Spine导出文件到Unity)

The -zh or -ja suffix references should actually never be used anywhere, we have corrected the Japanese translation. Thanks for reporting!

Great to hear that! And I updated my ToDo list,
Here is my New Translation To-Do List:

Great! Thanks for all your hard work! 8)

I have finished the update of cross-link in spine-unity documentation :sogood: :
spine-unity_zh_link_update.zip

BTW, I found two failed in-page links at line 2270 and 2262:

it made me feel that link

[Spine AnimationState Track](/spine-unity#Spine-AnimationState-Track)

failed because there exist no section called "Spine AnimationState Track" anymore, need to be correct :wailing:

BTW2:
I put some labels of translation in the section title(for disambiguation) that made it brackets included.
Shall I decorate any escape character before brackets contained in the cross-link to let markdown parse normally?

Please give me your advices. :fiesta: :fiesta:

Wow, that was super quick! Thanks so much for this big update, and for reporting the two broken Timeline links!
:fiesta: :cooldoge: :fiesta: 8)

We have integrated all your changes on the documentation page:
zh.esotericsoftware.com/spine-unity
Regarding using brackets: all seems to be fine, I could not find any problems. It should be safe to use brackets, even text like [code] will work unless the closing tag [/code ] is found following it.

I have a also fixed the two Timeline links in the Chinese page to point to the correct section now ("SkeletonAnimation-Track-与-SkeletonGraphic-Track"), and one link that was missing a dash -, the diff can be found here:
https://diffy.org/diff/c81afe813bc5b

In case I messed anything up, please let me know, I will of course be happy to fix it! 🙂
Thanks again for your great contributions! :nerd: :cooldoge:

5 days later

Nice! I have a translation update about the note of BlendModeMaterialsAsset here :nerd: :
[attachment=0][ZH]spine-unity-doc_BlendModeMaterialsAsset_Note.zip[/attachment]

2 months later

Thanks very much for the update! We have integrated your changes. :fiesta:

FYI: We have added some more additions and corrections to the spine-unity documentation page:
https://diffy.org/diff/cd7b37f689b3b
Please note that we have previously added a short remark in two locations of the Chinese spine-unity page ourself, simple added code comments: // skeletonMecanim.Update() for SkeletonMecanim. So please be sure to base any modifications on the updated page.

4 days later

I have finished the update of changes in spine-unity documentation :sogood: :
[attachment=0][ZH_CN]spine_unity.zip[/attachment]

7 days later

Thanks very much for the update, always much appreciated! :sogood: We have updated the documentation page accordingly.

FYI: We have uploaded yet another update regarding the documentation pages, this time spine-unity-events:
https://diffy.org/diff/05cd88bd40e4b

7 days later

OK, will update it ASAP

Done :coding: :coding: , here it is:
[attachment=0][UPDATE][ZH_CN]Spine Events and AnimationState callbacks.zip[/attachment]

20 days later

nice timing! I am finishing the tanslation [ZH_CN]spine_unity_cpp.
I will combine these two in the new TODO list ASAP. :fiesta: :fiesta: :fiesta:

Done! :sun: :sun: :sun:

Wow, that was amazingly quick!! :nerd: :cooldoge: :sun: Thanks a lot!
We have just updated the Chinese spine-unity documentation page with your additions.

spine-cpp Runtime Documentation translation complete, here is the update of TODO list:

After I check the spine-cpp Runtime Documentation, the update of spine-unity Runtime Documentation which mainly about Youtube links addition made me talk. I guess Chinese users may never visit the FAQ video concerning import problem since Youtube page cannot be legally viewed by most Chinese users.
Is there any way replace those two helpful Youtube links with other video source that own more accessibility for Chinese user? May be Acfun/Bilibili/iQiYi/Youku links or something else? :hmm: :hmm: :hmm: