feat: add i18n support with react-intl and initial translations #125
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
|
@ckemmler is attempting to deploy a commit to the LangChain Team on Vercel. A member of the Team first needs to authorize it. |
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.
This PR adds internationalization (i18n) support to the Agent Chat UI project, making it easy to localize the application into multiple languages.
Changes Included:
• Integrated react-intl for internationalization.
• Created a global I18nProvider to manage locale switching dynamically.
• Added a basic
LanguageSelectorcomponent to allow users to switch languages client-side without page reloads.Created initial translations for the following languages:
• English (en)
• French (fr)
• Dutch (nl)
• Portuguese (pt)
• Spanish (es)
• Italian (it)
• German (de)
• Russian (ru)
Translated the following UI strings:
• “Send”
• “Hide tool calls”
• “Thread history”
• “Type your message”
• Default locale is set to English (en).
Why?
• Improves accessibility for non-English speakers.
• Prepares the application for wider public and international deployments.
• Provides a scalable structure for adding more translations later.