feat: add Spanish translation file#2458
Merged
sandangel merged 4 commits intoChainlit:mainfrom Aug 28, 2025
Merged
Conversation
agutierrezmorag
requested review from
asvishnyakov,
hayescode and
sandangel
as code owners
dosubot
bot
added
size:L
sandangel
approved these changes
Aug 27, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This PR adds
backend/chainlit/translations/es.jsonusing neutral Spanish, suitable as a fallback for all Spanish-speaking regions.When using variants (like es-419), the app logs:
Translation file for es-419 not found. Using parent translation es.Since the fallback is intentional and the translation is neutral, suppressing this log for Spanish could be a good improvement, or I could also just add the variants as their own file, though they wil all have the same content. Let me which approach is preferred.