fix(i18n): implement robust translation fallback system for all locales#248
Merged
thebentern merged 1 commit intomeshtastic:mainfrom Sep 18, 2025
Conversation
|
@dzienisz is attempting to deploy a commit to the Meshtastic Team on Vercel. A member of the Team first needs to authorize it. |
7cf72bb to
8117d6d
Compare
thebentern
approved these changes
Sep 18, 2025
Contributor
Author
|
@thebentern I needed to add |
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
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.
Description
Implement robust translation fallback system for all locales to ensure users always see meaningful text instead of translation keys. This PR fixes the issue where raw translation keys like 'dfu.error_connection_title' were being displayed to users when Polish translations were missing or when the i18n system failed in Pinia store contexts.
Before (Polish language with missing translations)

After (Polish language with missing translations and fallback to english)

Type of Change
Testing
Hardware Model Acceptance Policy
New Hardware Model Acceptance Policy
Due to limited availability and ongoing support, new Hardware Models will only be accepted from Meshtastic Backers and Partners. The Meshtastic team reserves the right to make exceptions to this policy.
Alternative for Community Contributors
You are welcome to use one of the existing DIY hardware models in your PlatformIO environment and create a pull request in the firmware project. Please note the following conditions:
Getting Official Support
To have your hardware model officially supported and included in the Meshtastic ecosystem, consider becoming a Meshtastic Backer or Partner. Visit meshtastic.com for more information about partnership opportunities.
Protected Files Notice
The following files are protected and changes to them will be automatically rejected:
public/data/hardware-list.json- Auto-generated Hardware definitions (additionally see policy above)types/resources.ts- Auto-generated resource definitionsi18n/locales/**- Translation files (managed via Crowdin)