• Runtimes
  • Spine Runtime 4.0 zh-CN translation

Harald

digged several google results, the blog and this column refer some thing may helpful.

page=1 parameter works only for multi-page video collection e.g. this Satfiled OST Collection: set page=5 at https://www.bilibili.com/blackboard/html5mobileplayer.html?bvid=BV1sP411Y7am&page=5&high_quality=1 that player will stream the 5th video of collection. I guess you are right -- it's not an efficient parameter for single page bilibili video.

as for aid and cid: aid stand for av code which was changed to bvid years ago, these articles see it as a legacy for compatibility. And I assumed cid stand for clip id, because bvid identified the whole collection while cid become the identification of single video in the video collection, that might be useful for web video scraper rather than embed video.

Related Discussions
...

We've been using:

https://player.bilibili.com/player.html?bvid=BV1Y14y1z72c

We just change the bvid parameter. Seems the new player also works:

https://www.bilibili.com/blackboard/html5mobileplayer.html?bvid=BV1Y14y1z72c

Maybe we should change all our embeds to the new player? Seems the other parameters aren't needed?

  • wiige ответили на это сообщение.

    Nate Maybe we should change all our embeds to the new player?

    html5mobileplayer work for me when reading those blogs which studying bilibili API. I don‘t know too much about embed player but if you post a pool for player replacement I vote a big yes.

    Nate Seems the other parameters aren't needed?

    as far as I know now, all single-page bilibili video links only with bvid are working well , unless you decide to embed a tutorial playlist collection.
    I can't verify my assumption while bilibili.com removed "Share" button of web page.......

    2 месяца спустя

    @wiige FYI: We've added one more embedded video and a short description line in front of it reading
    "This video will help you with installing and using the Timeline extension package."
    The video embed was already added to the Chinese spine-unity page section, so it's just the description line in front of it that's missing currently.

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

    • wiige ответили на это сообщение.
      • Изменено

      Harald I see, let's update!

      one-line-update.zip
      60kB

      BTW, line 12 of JSON 导出文件格式, the link of Example JSON is failed, please check

      • Harald ответили на это сообщение.

        spine-phaser Runtime Documentation translation finished:

        zh-cnspine-phaser.zip
        9kB

        as always: notify me if any inappropriate found in this translation, I will rectify as soon as possible.

        @wiige Thanks a lot for the translations!

        As for the example JSON, I will check with Nate later as I am not sure of the correct condition (what it should be linked to).

        I think I should have reflected all the translation files you provided for us, except for the spine-unity documentation, so please check the corresponding pages.
        I added some minor fixes to the spine-phaser page: https://zh.esotericsoftware.com/spine-phaser
        Fixed the part where the backquote(`) was not closed and the link URL was somehow the one in the English runtime guide.

        However, the Spine编辑器文档列表 page may seem incomplete to you. This page was originally intended to replace only some of the translations using PHP, and the parts of the page for which no replacement code is provided cannot be replaced without creating a new page. So I created a new page for Chinese to reflect the translation you provided. In doing so, I mixed the Chinese translation originally reflected by PHP with the translation you provided. If you have any concerns, I would appreciate it if you could prepare a translation file to update it based on the current page.

        @Misaki what an instantaneous response! And thanks a lot for correction you have made!

        here is the update of your new page of Spine编辑器文档列表:

        editor-list-update.zip
        704B
        • Misaki ответили на это сообщение.
        • Misaki оценил это.

          @wiige The broken link on the JSON export format page has been fixed. The link was originally at the end of the section, but the following sentence has been added and the link has been moved there:

          Spine JSON exports can be found for each example project in the Spine Runtimes.

          https://en.esotericsoftware.com/spine-json-format#JSON-export-format

          A similar sentence has been added to the Binary export format page as well:

          Binary export files can be found for each example project in the Spine Runtimes.

          https://en.esotericsoftware.com/spine-binary-format

          It would be great if you could translate them when you have time!

          here is the quick update:
          for spine-binary-format :

          bin.zip
          7kB

          and for spine-json-format:

          json.zip
          8kB
          • Misaki ответили на это сообщение.
          • Misaki оценил это.

            wiige Harald I see, let's update!

            Thanks very much for all your great work @wiige!
            The spine-unity-zh page has been updated accordingly.

            wiige Thanks for your quick response! But, the binary one is perfect, but the JSON one does not seem to be updated. Perhaps the English page update itself did not load properly on your end? I am attaching here the .md file of the current English version of the JSON export format page just in case you need it:

            spine-json-formatmd.zip
            7kB
            • wiige ответили на это сообщение.

              Misaki I added the translation of git example page at line 3 and removed the deprecated line 12:

              Whether there exist more content update of spine-json-format that I have missed? but, so sorry I failed to locate them all......

              Could you please offer me a diff file/link for spine-json-format so that may relieve my burden of tracking content changes?

              json.zip
              8kB
              • Misaki ответили на это сообщение.

                wiige Thank you for the clarification! Sorry, apparently I had left the previous zip on my local, and I had mistakenly unzipped it and misunderstood. What you have translated is correct! The JSON export format page is updated: https://zh.esotericsoftware.com/spine-json-format

                • wiige оценил это.
                2 месяца спустя

                @wiige FYI: We've added two new documentation lines to the spine-unity documentation page, regarding recently added Physics Constraints Inspector settings at both SkeletonRenderer and SkeletonGraphic components:
                https://diffy.org/diff/16052a61d5755

                • wiige ответили на это сообщение.

                  Harald got, here is your update:

                  spine-unity-physicsconstraints-update.zip
                  60kB