• Runtimes

  • Spine Runtime 4.0 zh-CN translation

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 运行时文档?

      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

          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 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:

              1. Create a directory for the documents to be tracked.
              2. git init . to create a simple local git repository at this directory.
              3. Create your document file like spine-unity.md and paste the current page content in it.
              4. git add spine-unity.md and git commit the addition.
              5. Then after modifying the document, again git add spine-unity.md and git commit the changes.
              6. 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.

                    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

                      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 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 Apologies for my late reply, I was attending a conference (Reboot Develop Blue) last week and have just come back to the office. Thank you very much for your updates and for including the 4.2 update already as well! We have updated the website accordingly.

                                @wiige We have added a posting and a line to the 4.1 to 4.2 Upgrade Guide:
                                Posting added:
                                https://esotericsoftware.com/forum/d/26006-spine-unity-41-to-42-upgrade-guide/3
                                Line added to top-most posting (below the 3. bullet point):
                                [*] Replace any occurrances of `SkeletonGraphicRenderTexture.quadRawImage` with `quadMaskableGraphic`, change the type from `RawImage` to `MaskableGraphic`.[/*]
                                It would be great if you could add it at the Chinese 4.1 to 4.2 Upgrade Guide as well!

                                In the posting, you could skip the excerpt from the changelog, since we normally don't translate the changelog. It's the block starting with "> * SkeletonGraphicRenderTexture example component: protected RawImage quadRawImage was changed [..]".

                                  Harald sure！I am willing to follow up on this change, but I am not allowed to modify the content of that post......

                                      wiige You are right! So if you could add the translation to the thread as a reply, I will edit the original thread and add the addition. Thanks in advance!

                                          @wiige Thanks very much for the quick translation! 😎 👍️

                                          a month later

                                          (I just realized I had posted this on another thread. My apologies!)
                                          Hi, @wiige. We would like to inform you that we have added the new documentation for the spine-sdl runtime: https://esotericsoftware.com/spine-sdl
                                          If you are interested, it would be appreciated if you could translate it for us.

                                          We are also working on documentation for the documentations for the spine-pixi runtime and spine-haxe runtime, which will probably be available soon.
                                          Now that the 4.2 feature development and bug fixes have settled down, we are actively working on the documentation. So document additions and updates may become more frequent.

                                            5 days later

                                            Misaki

                                            Now that the 4.2 feature development and bug fixes have settled down, we are actively working on the documentation.

                                            happy to hear that! working on spine-sdl now, feel free to post any docs here, I will try to translate them all when I am available : )