docs: fix i18n in Home #21288
Draft
docs: fix i18n in Home #21288
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
Jesse205
force-pushed
the
fix-doc-i18n
branch
2 times, most recently
from
a976ccb to
97467fb
Compare
Contributor
Author
|
How to fix this Semantic PR error? |
Contributor
Author
|
@KaelWD How do I verify this PR to make sure that the text on the homepage can be translated into other languages? |
Contributor
Author
|
Thanks for helping fix my title error. Also, I've got rid of all the extraneous changes, and now it's my job to see if the strings are translatable, but I don't know what to do. |
KaelWD
force-pushed
the
master
branch
4 times, most recently
from
142b234 to
bb54746
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Try to fix i18n in home，example title，description，features.
Markup: