i18n: Improve Korean localization quality#2
Open
GOODJINC wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refined Korean UI translations for better readability and consistent terminology.
I am very pleased to see that much of the application has been localized into Korean. However, I have noticed that some terms remain in English or are missing from the localization files. Additionally, due to structural differences between English and Korean, some sentences appear grammatically incomplete, and there are instances where the UI layout is affected. I plan to organize these issues and share them with the community in the near future.
Thank you for your ongoing efforts in localization.