-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Reorganizing README translations into a dedicated i18n directory structure #2149
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
0xnogo
changed the title
Ng/moving-readmes
Reorganizing README translations into a dedicated i18n directory structure
Jan 11, 2025
hi @0xnogo could you resolve the conflict |
- Introduced new language translations for Eliza in Arabic, Chinese, German, Spanish, French, Hebrew, Hungarian, Italian, Japanese, Korean, Dutch, Polish, Portuguese, Romanian, Russian, Serbian, Tagalog, Thai, Turkish, and Vietnamese. - Updated the README structure to include links to the new translations. - Added a new plugin '@elizaos/plugin-hyperliquid' in the pnpm-lock.yaml file with its dependencies. - Adjusted the README links to point to the correct paths for translations.
0xnogo
force-pushed
the
ng/moving-readmes
branch
from
January 15, 2025 06:21
eda1ec2
to
79a9650
Compare
we don't need this one? README_FARSI.md |
|
odilitime
approved these changes
Jan 16, 2025
odilitime
changed the title
Reorganizing README translations into a dedicated i18n directory structure
chore: Reorganizing README translations into a dedicated i18n directory structure
Jan 16, 2025
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.
Relates to
#2210
Reorganizing README translations into a dedicated i18n directory structure
Risks
Low - This is primarily a documentation organization change that:
Background
What does this PR do?
i18n/readme/
directory structure for README translationsWhat kind of change is this?
Improvements (reorganization of existing documentation structure)
Documentation changes needed?
My changes require a change to the project documentation:
Testing
Where should a reviewer start?
Detailed testing steps
i18n/readme/
directoryDeploy Notes
After merging:
i18n/readme
directory if it doesn't exist