-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Japanese Translation of Warudo Handbook #13
Comments
Hi, @unsolublesugar ! Thank you for your attention and support! Currently, the Japanese version of the documentation is just being established. I have already uploaded the first Japanese document in When there is no available Japanese document, the English version document will automatically display instead. While machine translation is an option, And of course, I am ready to receive any merge requests. Looking forward to your contributions! 🤗 |
@Nekotora Thanks for sharing the status! Thanks for letting me know how to verify that it works. I'll try to work with the existing directory structure as a reference. One question, are there any detailed rules for branch operations and branch name creation? Is the current form just to name the developer. It might be a good idea to have detailed rules within the project, as it is easier to manage if there are operational rules and naming conventions such as git-flow. Please consider incorporating such development and operation rules for the future development of this project. |
Hi @unsolublesugar, while I'll leave the details of repo contribution to @Nekotora, I would like to thank you for willing to improve the Japanese translation! Side note regarding the translation status: We planned to let our Japanese translator work on the translation for the documentation site as well, but unfortunately they can only translate from Chinese -> Japanese, not from English -> Japanese, and we haven't had time to translate the current English documentation into Chinese yet. If you or you know someone who would like to work on the translation, please feel free to let us know - happy to pay and/or offer complimentary indie Warudo Pro licenses in return! |
@TigerHix Thanks for the additional explanation! It will take some time to translate all the pages since I'll be working on the side of my day job. Is that okay? |
That would be greatly appreciated - Thank you and take your time! :) Kindly let us know if you need help with anything! |
Just merged your pending PRs and updated the website! |
🤩 Substantial HUGE updates in the Japanese document! I agree that we should establish more git guidelines. The previous documents were quite internal, and the translation guys may be unfamiliar with booming front-end development stuff. Let me try to add those guidelines to the document recently. And thanks again! |
@Nekotora Glad you agree with my suggestion. Looking forward to your improvements. Speaking of which, I appreciate the detailed explanation on your document contribution page! I'll create an issue if there is anything else to discuss. |
It's been a while since the last update, but I think I'll be able to continue translating from next week💪 |
Hi contributors!
I'm a Warudo user in Japan, and I want to thank you for developing such a great software for VTubers!
I want more users in Japan to try Warudo and I would like to challenge to help with Japanese translation.
Currently,
/i18n/jp/docusaurus-plugin-content-docs/current
does not exist, and it seems that the text remains in English text even when Japanese was selected in Warudo Handbook language.I found a reference to the Japanese translation in a past post on Discord. What is the current status?
https://discord.com/channels/1053915524280614983/1155315680896360449/1217073068984238111
Do you plan to first apply machine-translated Japanese as mentioned in the aforementioned post? I believe I and other Japanese-speaking developers can help with the translation, including adjusting nuances during translation.
Are you already at the stage of preparing to apply the most recent translation?
I would be glad to know the status!
The text was updated successfully, but these errors were encountered: