Current status for class reference localization in editor and online
VectorWorkshopBaoErJie opened this issue · comments
Recently, we organized community members to complete the translation of the Chinese part of the GODOT API, but we were unable to compile and generate Chinese documents through a workflow.
The content of this page was translated to 100% and was manually verified：
https://hosted.weblate.org/projects/godot-engine/godot-class-reference/zh_Hans/
want to update the build workflow
Great work!
It's a bit difficult currently as I only added support for documentation localization to the master branch of the Godot editor (so Godot 4.0). But when I added the translation catalog on Weblate this was before a lot of changes to the 4.0 API, so there will be significant work needed to update the translations further for Godot 4.0.
The current translations could be used for Godot 3.4, but it would require backporting the relevant editor changes to 3.x (could probably be done). But the more tricky part is that on Weblate we can't easily have two branches for different versions, we would need to duplicate the resource. As translating the class reference is a lot of work, I preferred to focus only on 4.0 (but in retrospective, since 4.0 takes so long to be released, and we now have 3.x feature releases, it would have been better to focus on 3.x).
For the online version of the docs, I haven't had time to work on converting the XML from the PO files to a format that can be used by Sphinx (RST) to match the strings in the generated class reference POT file. This makes things a bit tricky. So it will take more time before the translated strings can be used on docs.godotengine.org.
I need to think some more about how to handle this. I suppose that you would like to have the translations in Godot 3.x?
For the reference, the PRs which added support for class reference translations in the editor are the following ones:
- godotengine/godot#37114
- godotengine/godot#37185
- godotengine/godot#37164
- godotengine/godot#39118
- And maybe godotengine/godot#40107
So all this would need to be included in 3.x and tested if we want to use the current Chinese and Spanish translations in Godot 3.4, before moving the general translation effort toward Godot 4.0.
I'll take a look and try to backport those PRs.
I went ahead and backported the relevant PRs in godotengine/godot#53511, it seems to work well! Next step is to sync the Weblate translations in the 3.x, and then there will be some more work for translations to bring everything up-to-date for 3.4:
- 8000 strings still good
- 2000 strings "fuzzy" (English string changed a bit, needs review)
- 1000 new strings
The Weblate class reference templates have been updated, so now it's reflecting the latest 3.x branch: https://hosted.weblate.org/projects/godot-engine/godot-class-reference/
There's some work to do to review fuzzied strings and translate the new ones, as much as we can before the 3.4 release :)
We will organize follow-up translations on this side, and we very much hope that GODOT will have good support for continuous improvement in multiple languages. We are very much looking forward to the 4.0 version with good localization support for interface, property inspector, API, web documentation, etc., especially the Chinese part.
In China, there are more and more developers interested in GODOT and the community keeps expanding. I also believe GODOT will get better and better, and will become a great software compared to blender. I always mobilize those profitable developers to support GODOT officially financially. I will do the same after the future profit.
For me personally, I have translated a lot of content including documentation, made related tutorial videos on bilibili, and will contribute to GODOT related aspects for a long time in the future.
For the GODOT compilation container, there are still problems, can not be well built, I hope to solve. Because I am compiling this side of the self-translated and modified Chinese enhanced version for everyone to learn to use.
@akien-mga What's the status of this? If I haven't missed anything, then in 4.x, class references are not translated in the inspector, at least when I compile locally.
Use the "Localized" option in the Wrench menu.
It's not turned on by default because these English names are useful in code. To changed the default behavior, change interface/inspector/default_property_name_style in Editor Settings.
Very nice, thank you.