Readme Korean localization (|10n/ko-k0r/README.md) #463
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## latest #463 +/- ##
==========================================
+ Coverage 90.35% 90.54% +0.19%
==========================================
Files 47 47
Lines 4374 4379 +5
Branches 586 587 +1
==========================================
+ Hits 3952 3965 +13
+ Misses 287 280 -7
+ Partials 135 134 -1 ☔ View full report in Codecov by Sentry. |
goatshriek
approved these changes
Oct 7, 2024
goatshriek
added
the
hacktoberfest-accepted
|
Thank you:) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Localization English Readme to Korean(|10n/ko-k0r/README.md).
and Like '|10n/zh-cn' folder, I made assest folder as Korean in '|10n/ko-kr'
*Question
Hello. I want to ask about localization.
I didn’t translate linking words that are proper nouns or specific terms, such as Twitter hashtags, function names, or technical terms. For example, the #StumplessLib hashtag was left untranslated. Is it Okay?
Translate about "Severity Shorthand"
I translated "Severity Shorthand" to "로그 레벨(Severity) 단축 명령어," which means "Log Level Shorthand." I tried to find a proper word for "severity" in Korean. The direct translation is "심각도," but this term is not commonly used and could lead to misunderstandings. Therefore, I opted to use "로그 레벨." Is this approach acceptable?
Location
I put Chinese Readme > English Readme > [Key Features] | [Build and Install] | [Basic Usage | [Contributing](transltation these words in korean)
Is this location aceeptable?