Fill missing es/pt/de/zh translations across frontend and backend#695
Merged
Conversation
cristian-tamblay
approved these changes
Jun 15, 2026
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.
Summary
All four non English locales (es, pt, de, zh) are now at 100% translation coverage, both on the frontend and the backend. This was purely missing data, no logic was changed.
On the frontend, every i18next key present in
ennow exists ines,pt,de, andzh. On the backend, everyMultilingualString(...)literal now carrieses,pt,de, andzhkeyword arguments alongsideen. A static AST based checker script was also added so future gaps can be caught without running the app.Type of Change
Changes (by file)
Frontend - locale JSON files
src/utils/i18n/locales/de/common.json,datasets.json,explainers.json,models.json: fill missing de keyssrc/utils/i18n/locales/de/hub.json: new file, full hub namespace translation for desrc/utils/i18n/locales/pt/common.json,datasets.json,explainers.json,models.json, etc.: fill missing pt keyssrc/utils/i18n/locales/pt/hub.json: new file, full hub namespace translation for ptsrc/utils/i18n/locales/zh/common.json,datasets.json,explainers.json,models.json,home.json,hub.json,generative.json: fill missing zh keyssrc/utils/i18n/locales/es/models.json: add missing_manyplural formssrc/utils/i18n/locales/pt/models.json: add missing_manyplural formsfront/i18next.config.js: add pt, de, zh to the locale list soi18next-cli statusreports themFrontend - components
src/components/tour/NavbarTourButton.jsx,TourButton.jsx: replace hardcoded "Start Tour" / "No tour available" strings witht()callssrc/utils/i18n/locales/*/common.json(all locales): addstartTour,noTourAvailable,tourNotAvailablekeysBackend -
MultilingualStringcoverageDashAI/back/models/scikit_learn/*.py(32 files): addzh,de,ptkwargs to allMultilingualStringcallsDashAI/back/models/hugging_face/*.py(21 files): sameDashAI/back/models/*.py(base_torchvision,cnn,efficientnet_b0,lenet5,mlp,resnet18,resnet50): sameDashAI/back/dataset_sources/*.py,dataloaders/classes/image_dataloader.py,exploration/explorers/*.py: sameTooling
scripts/check_translations.py: new AST based script that scans allMultilingualStringliterals and reports coverage per locale; supportsstatus(table) andlint(exit 1 on gaps) modesTesting
npx i18next-cli status(run fromDashAI/front) reports 100% for all four localespython scripts/check_translations.pyreports 100% for all four locales across 1341 backend literals