Add Documentation for I18n Support in README #55
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
This commit includes details about the tool's support for the i18n API, including how to localize UI labels using the i18n dictionary in the `tools` section. A link to more instructions on Editor.js internationalization was also added.
yossibeck
approved these changes
May 30, 2023
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.
Summary
This PR updates the README to include information about the support for the I18n API within the Nested List Tool for Editor.js. It provides a detailed example on how to localize UI labels using the i18n dictionary under the
toolssection. A reference to more in-depth instructions on Editor.js internationalization is also included.Key Additions
These additions will help users who are new to the tool understand its i18n capabilities and how to use them effectively.
Related Issues
Type of change
Documentation Update
Checklist
How was this tested?
Visual review of the updated README content was performed to confirm correct markdown syntax and accurate content description.