-
Notifications
You must be signed in to change notification settings - Fork 11
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
Problems with Korean’s translation on Weblate #13
Comments
Dear @DDinghoya, Thank you for your exhaustive report, we really appreciate it ! Regarding your first remark, it should be noted that not all strings present in the Slicer GUI are currently listed on Weblate, the translation platform. The remaining strings mainly concern:
As @pieper mentioned in the linked post, there is an ongoing project that addresses this issue and some of their work in progress may interest you.
We are currently working on their integration into the internationalization process and should have convincing results shortly. Thus, missing strings should be available for translation. For your second point, we will investigate it further to see what's causing it. Thank you again for your interests in this project. Best regards. |
Some of this issues are caused by Text that does not appear in translations are generated dynamically from code and they are not marked as translatable. @mhdiop is working on exposing all these strings. This is tracked in #12. Since these issues are already tracked in other issues, I'm closing this issue now. |
Dear,
The above issue has been posted to the 3D Splicer community -> Link
Basically the Korean translation was 100% completed on weblate, and there were two problems.
Sample_Menu *
Sample_settings *
Even if I downloaded the language pack from github and applied it manually, it was not reflected.
I think the problem arises when using a 2 byte character set.
It is hoped that the cause of the problem and improvement will be addressed through this post. :)
Best regards.
The text was updated successfully, but these errors were encountered: