• Runtimes
  • Spine Runtime 4.0 zh-CN translation

Related Discussions
...

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.)

    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:

    zhspine-unity-download.txt
    18kB

      Harald thx so much, I have added it to my gitlab, and here is the corrected version of spine-unity-download:

      zh-cn-spine-unity-download.zip
      5kB
      7 jours plus tard

      Harald may I have the template of spine-api-reference? I thought it's a good idea to keep it update

      @wiige Thanks for asking, sure!

      spine-api-reference-zh.zip
      37kB

      Please note that this page is directly edited, it's not generated from a template like the spine-unity-download variants. At the download pages we generate the content to keep the current download URLs and version numbers in sync.

      @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.

        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!