Add ko.json to support Korean localization #583
Merged
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
|
Fantastic! Thank you 🙏 Merging, and will be included in Pagefind's next release (hopefully soon!) |
bglw
approved these changes
Mar 26, 2024
|
Thanks @bglw Have a nice day! |
|
Released in released in v1.1.0, thanks again! |
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.
Hello maintainers!
Thanks for this nice project.
I am one of the maintainers of the CNCF Cloud Native Glossary Project
We are trying to apply the PageFind to our website.
It seems Korean UI strings are not supported yet. Hope to add Korean ko.json.
Please note that I am a native Korean and contributing to several Korean localization projects. :)