fix: add locales for tradition names - #363
Merged
Otaiki1 merged 1 commit intoSep 4, 2026
Merged
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
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.
What changed
Implemented the localization support requested in Issue #297 by adding dedicated locale dictionaries for the traditions referenced by the Sharibo README.
Added locales
fr.ts— French / tontinept.ts— Portuguese / consórcioyo.ts— Yoruba / ajo and esusutl.ts— Filipino / paluwaganzh.ts— Chinese / huihi.ts— Hindi / chit fundEach new locale mirrors the existing English locale key structure so the application can safely resolve the same translation keys across supported languages.
The tradition-specific terminology is preserved in each locale instead of replacing the names with unrelated generic translations. This keeps the terminology aligned with the communities and traditions referenced by the project README.
Why
The application previously shipped with only English and Spanish locales even though the README recognizes traditions from a wider range of linguistic and cultural communities.
This change closes that localization gap and allows the UI to represent those traditions using their own commonly used names.
The existing i18n implementation already performs exact and base-language matching, so regional browser languages such as
pt-BRcan resolve to the newptlocale without requiring unnecessary changes to the localization loader.Issue
Closes #297
Testing
en.tspt-BRcan fall back toptthrough the existing browser-language matching logicScope
This PR intentionally keeps the implementation minimal.
No changes were made to the existing localization architecture because the current
i18n.tsimplementation already discovers./locales/*.tsdynamically and already supports regional language fallback.The primary change is the addition of the requested locale dictionaries.