Spine Runtime 4.0 zh-CN translation
Hi, @wiige ! A completely new page, ”On-Demand Loading UPM Packages,” has been added to the spine-unity runtime documentation. Could you help with the translation?
The diff is below, but as for the table of contents, I can add the links to each page, so you don't need to prepare the .md files for each page, just let me know the translation text:
https://diffy.org/diff/d421898072269
Thanks in advance!
- Изменено
Misaki got, here is the translation of On-Demand Loading UPM Packages:
for TOC and page indicator:
懒加载扩展 UPM 软件包 == On-Demand Loading Extension UPM Packages
note that I translated "On-Demand Loading" as "懒加载/惰性加载" which is Lazy Loading, by my understanding to the doc, because "按需加载"(literal translation) is not a customary expression in Chinese.
are they equivalent? I need an unity expert @Harald
wiige Thank you for the translation! Harald has not confirmed it yet, but based on my research, I believe that the term "懒加载" is commonly used, so I went ahead and included it.
I also removed some remaining English text, changed some links, and changed the notation in some places where it was necessary for the sake of the heading links. (I changed it because the heading links would be confusing when the same text appeared in different sections.)
I would appreciate it if you could check to make sure there are no problems: https://zh.esotericsoftware.com/spine-unity-on-demand-loading
@wiige Thanks very much for translating the page, much appreciated as always!
Yes, the terms are equivalent. Thanks for translating it in the most suitable way.
Harald fast response!
I am working on https://zh.esotericsoftware.com/spine-physics-constraints now
and I found several mistanslations at https://zh.esotericsoftware.com/spine-unity-download, will rectify them and post here with physics-constraints guide
wiige Thank you very much for offering to translate the user guide! However, the reason why this page has not been translated into Chinese is because the original English version is still a work in progress. We would appreciate your translation, but please be aware that there may be significant changes in the future. (We apologize for the long delay in updating the user guide.)
Misaki I am relieved that I was informed you in advance about https://zh.esotericsoftware.com/spine-physics-constraints translation. will now suspend the translation process of spine-physics-constraints guide. Please call me when guide is ready.
wiige I found several mistanslations at https://zh.esotericsoftware.com/spine-unity-download, will rectify them and post here with physics-constraints guide
@wiige Oh, thanks for letting us know! As the spine-unity-download page is generated, might I ask you if you could directly modify the template instead of the generated result page:
Harald thx so much, I have added it to my gitlab, and here is the corrected version of spine-unity-download:
@wiige Thanks very much for your quick and thorough update! We've updated the spine-unity-download page accordingly.
Harald may I have the template of spine-api-reference? I thought it's a good idea to keep it update
@wiige BTW: Now would be a rather unstable time to update the API translation, as with the 4.3-beta runtime changes rather large parts of the documentation have changed, and the respective documentation is not up to date yet. The changes affect mainly everything related to bone poses, transforms and applied transforms and constraints. So please do not put any effort into syncing these sections yet.
Harald I seeeeeee........ that means I'd better wait for 4.3-stable and this attachment is exactly same as https://zh.esotericsoftware.com/spine-api-reference/markdown, right?
then may I ask a diff of spine-api-reference when the api reference is ready for 4.3 stable? thanks in advance
wiige Harald I seeeeeee........ that means I'd better wait for 4.3-stable and this attachment is exactly same as https://zh.esotericsoftware.com/spine-api-reference/markdown, right?
Yes, it's just the markdown (with some additional header which is irrelevant though)! I assumed that maybe the /markdown
functionality was broken and you could no longer access it.
wiige then may I ask a diff of spine-api-reference when the api reference is ready for 4.3 stable? thanks in advance
Sure, we'll let you know!