* feat: Add a Connected Account Setting for Pull Requests * fix: Watch an Open Account Sign-In and Keep the Retry Button Named * fix: Name the Disconnect Confirmation and Show the Provider the Server Reports * feat: Tell the Client How Long a Pull Request Account Sign-In Lasts * fix: Follow the Sign-In Lifetime and Keep Account Actions Settled Past Settings * fix: Watch an Account Sign-In Until Its Window Closes, Even After Settings Closes * fix: Refresh Pull Requests Once per Change of the Credential They Were Fetched With * fix: Record Every Status the Sign-In Watch Reads * fix: Keep Watching a Severed Sign-In Through Its Landing Page and End Watches With the Session * fix: Drop a Sign-In Begun Before the Session Ended * fix: Keep a Surviving Grant Removable and Tie a Sign-In Watch to Its Own Flow * fix: Ask for the Pull Request Account Wherever Pull Requests Are On * fix: Refresh Pull Requests on a Session's First Status and End a Failed Sign-In's Watch * fix: Ignore an OAuth Failure That Names No Sign-In Flow * fix: Start No Sign-In for a Window Closed Before the Server Answered * fix: Keep a Known Grant Removable While the Status Check Fails * fix: Name a Grant Without a Current App Only as an Account * fix: Keep the Pull Request Account Row Readable on a Phone * fix: Show a Grant Whose App Is Off as Not in Use * fix: Apply a Sign-In Status Asked For Before the Flow Expired * fix: Keep Focus When Removing the Last Pull Request Grant and Reuse Its Status * fix: Resync Pull Request Credentials After Failed Sign-Ins and Disconnects * fix: Ask for the Connection Status Afresh Once a Sign-In Settles * fix: Resync Pull Requests From the Settings Visibility Status * fix: Reconcile Pull Request Credentials Until a Status Read Succeeds * fix: Keep Pull Request Sign-In State Accurate Across Failures and Account Switches * fix: Drop Replaced Sign-In Answers and Reset Status When the Account Changes * fix: Reset Unwatched Connection Status and Keep Focus When a Retry Hides the Row * fix: Hear Late Sign-In Settlements and Explain Connect Failures After Settings Closes * fix: Listen Until a Sign-In Settles and Keep Focus After a Dismissed Disconnect |
||
|---|---|---|
| .. | ||
| ar | ||
| bo | ||
| bs | ||
| ca | ||
| cs | ||
| da | ||
| de | ||
| en | ||
| es | ||
| et | ||
| fa | ||
| fi | ||
| fr | ||
| he | ||
| hu | ||
| hy | ||
| id | ||
| is | ||
| it | ||
| ja | ||
| ka | ||
| ko | ||
| lt | ||
| lv | ||
| nb | ||
| nl | ||
| nn | ||
| pl | ||
| pt-BR | ||
| pt-PT | ||
| ru | ||
| sk | ||
| sl | ||
| sv | ||
| th | ||
| tr | ||
| ug | ||
| uk | ||
| vi | ||
| zh-Hans | ||
| zh-Hant | ||
| i18n.ts | ||
| README.md | ||
| Translation.spec.ts | ||
LibreChat Localization Guide
This guide explains how to add new languages to LibreChat's localization system.
Adding a New Language
To add a new language to LibreChat, follow these steps:
1. Add the Language to Locize Project
- Navigate to the LibreChat locize project,
- Click the "ADD LANGUAGE" button, typically found within the "..." menu of the "Start to translate" card on the project overview page.
2. Update the Language Selector Component
Edit client/src/components/Appearance/Selectors.tsx and add your new language option to the languageOptions array:
{ value: 'language-code', label: localize('com_nav_lang_language_name') },
Example:
{ value: 'bo', label: localize('com_nav_lang_tibetan') },
{ value: 'uk-UA', label: localize('com_nav_lang_ukrainian') },
Note: Use the appropriate language code format:
- Use simple codes (e.g.,
bo) for languages without regional variants - Use region-specific codes (e.g.,
uk-UA) when needed
3. Add Localization Keys
In client/src/locales/en/translation.json, add the corresponding localization key for your language label:
"com_nav_lang_language_name": "Native Language Name",
Example:
"com_nav_lang_tibetan": "བོད་སྐད་",
"com_nav_lang_ukrainian": "Українська",
Best Practice: Use the native language name as the value.
4. Create the Translation File
Create a new directory and translation file:
mkdir -p client/src/locales/[language-code]
Create client/src/locales/[language-code]/translation.json with an empty JSON object:
{}
Example:
client/src/locales/bo/translation.jsonclient/src/locales/uk/translation.json
5. Configure i18n
Update client/src/locales/i18n.ts:
- Import the new translation file:
import translationLanguageCode from './language-code/translation.json';
- Add it to the
resourcesobject:
export const resources = {
// ... existing languages
'language-code': { translation: translationLanguageCode },
} as const;
Example:
import translationBo from './bo/translation.json';
import translationUk from './uk/translation.json';
export const resources = {
// ... existing languages
bo: { translation: translationBo },
uk: { translation: translationUk },
} as const;
6. Handle Fallback Languages (Optional)
If your language should fall back to a specific language when translations are missing, update the fallbackLng configuration in i18n.ts:
fallbackLng: {
'language-variant': ['fallback-language', 'en'],
// ... existing fallbacks
},
Translation Process
After adding a new language:
- The empty translation file will be populated through LibreChat's automated translation platform
- Only the English (
en) translation file should be manually updated - Other language translations are managed externally
Language Code Standards
- Use ISO 639-1 codes for most languages (e.g.,
en,fr,de) - Use ISO 639-1 with region codes when needed (e.g.,
pt-BR,zh-Hans) - Tibetan uses
bo(Bodic) - Ukrainian uses
ukoruk-UAwith region
Testing
After adding a new language:
- Restart the development server
- Navigate to Settings > General
- Verify your language appears in the dropdown
- Select it to ensure it changes the UI language code
Notes
- Keep language options alphabetically sorted in the dropdown for better UX
- Always use native script for language names in the dropdown
- The system will use English as fallback for any missing translations