Repository navigation
Conversation
Two broken merges into hi/translations.json (9f47487, 8158c1d) left the file invalid, and the follow-up fix (6245964) made it parse again but dropped ~60 existing Hindi strings and left an orphaned top-level copy of the Nav keys after AssetList. - remove the unused top-level Edit/Sketch/Auth/... block - restore lost translations from history (Preferences.CustomVersion*, About.Contact, Feedback, CollectionView, MobilePreferences, MobileDashboardView, Explorer, *_mobile headers, etc.) - translate "Asset" consistently as "ऐसेट" - fix RenameVariable: "चरण" (step) -> "वैरिएबल" (variable) Fixes processing#3812 Co-authored-by: Urvi <urviagarwal2711@gmail.com>
Member
Author
ksen0
approved these changes
Oct 22, 2026
ksen0
left a comment
Member
There was a problem hiding this comment.
Thank you! I think it can be included in the next release, cc @doradocodes
This branch is waiting to be deployed
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.
Fixes #3812
Two broken merges into
hi/translations.json(9f47487, 8158c1d) left the file invalid. The follow-up fix (6245964) made it parse again, but it dropped ~60 existing Hindi strings and left an unused top-level copy of the Nav keys afterAssetList.This supersedes #3813, as discussed in the issue.
Demo:
Changes:
Edit/Sketch/Auth/ ... blockPreferences.CustomVersion*,About.Contact,Feedback,CollectionView,MobilePreferences,MobileDashboardView,Explorer,*_mobileheaders, etc.)Nav.Auth)RenameVariable: "चरण का नाम बदलें" → "वैरिएबल का नाम बदलें"Keys that never had a Hindi translation (e.g. log-in tooltips,
LoopProtection*, the newStepUpstrings) still fall back to English and can be translated in a follow-up.Co-authored with @Urvi2727
I have verified that this pull request:
npm run lint)npm run test)npm run typecheck)developbranch.Fixes #123