[i18n] SSOC2026 - Implement Full Platform Translation (Hindi/Bengali) Across All Pages

[rhalbhavi]

Description

Closes Issue #94

This PR implements i18n translations for Hindi and Bengali across the entire application, including API errors and internet connection related errors.

• Audited all pages in src/pages/ and components in src/components/.
• Replaced all hardcoded English text strings with the t('key') function from useTranslation().
• Added the corresponding translation keys and values to the Hindi (hi.json), Bengali (bn.json), and English (en.json) translation dictionaries in src/i18n/locales/.
• Ensured dynamic text (like error messages and API responses) is also handled gracefully.
• Added a central i18n.ts file - Function for initializing and exporting the i18next instance

Checklist

• npm run lint passes with no errors
• npm run build compiles without TypeScript errors
• python -m pytest passes (including new tests I added)
• No .env files, API keys, secrets, model weights, or __pycache__ in this diff
• Branch is rebased on main, not merged

---

Screenshots

Hindi Translations

Mode Screen

Scanner Screen

Map Screen

Results Screen

---

Bengali Translations

Mode Select screen

Scanner screen

Map screen

Results screen

Summary by CodeRabbit

Release Notes

• New Features

  • Added internationalization with English, Hindi, and Bengali across the app, including navigation, onboarding, installation prompts, and all major pages.

• Bug Fixes / Improvements

  • Improved error handling so scan, authentication, loading, and camera messages are consistently localized and shown in the UI.

• Chores

  • Updated dependencies and tooling versions.
  • Refreshed i18n resources and related app configuration.

• Documentation

  • Updated the README project structure to include the new internationalization folder.

[rhalbhavi]

@jpdevhub It seems that your CI workflow file (.github/workflows/ci.yml) is using incorrect major versions for some standard GitHub Actions (e.g., actions/checkout@v6). I think correct versions are @v4 and @v5
But I am not sure that's the right reason, for the frontend build test failing

[jpdevhub]

If failed i will see the issue you dont suppose to change the other files

[jpdevhub]

Please git fetch upstream and rebase your branch on the latest main, ensuring you do not overwrite the new features in ScannerPage.tsx and AnalysisDashboard.tsx

And why are you deleting the messages from the channel ? what something happned previously ?

[rhalbhavi]

Please git fetch upstream and rebase your branch on the latest main, ensuring you do not overwrite the new features in ScannerPage.tsx and AnalysisDashboard.tsx

And why are you deleting the messages from the channel ? what something happned previously ?

@jpdevhub I've updated the branch to the latest - done

[jpdevhub]

Thank you for the i18n implementation! However, because your fork is very old, your PR accidentally downgrades React 19 to 18, Vite 8 to 5, and deletes our ESLint Flat Config. It also deletes our new Grad-CAM features. Please back up your translation files (en.json, hi.json, bn.json), do a completely fresh clone of main, and re-apply just the translation files and {t()} functions. We cannot merge a branch with downgraded package.json dependencies

[jpdevhub]

you are going completely wrong direction. Delete your branch from the github and clone it again and do a fresh commit and add the commit as git add . for all not individually. you can contact me personel in discord or any site

[jpdevhub]

You will be ban if this type of pr raised in any reputed or production repo

[rhalbhavi]

Ok sure @jpdevhub will do that

[rhalbhavi]

.

[jpdevhub]

Make a new pr

[rhalbhavi]

@jpdevhub Okay

[rhalbhavi]

Make a new pr

@jpdevhub Done it