Multi-Language Support for Disease Scan Results

[jpdevhub]

The disease scanner returns results in English. Use i18next on the frontend or a translation library on the backend to allow farmers to read the disease symptoms and treatments in their native language (e.g., Hindi, Spanish).

[github-actions]

👋 Thanks for opening this issue, @jpdevhub!

We'll take a look soon. In the meantime, please make sure you've included steps to reproduce (for bugs) or a clear problem statement (for feature requests).

— The AgroNavis team

[Excalibur677]

Hey @jpdevhub,

I'd love to claim this issue!

Using the Google Cloud Translation API on the backend is definitely the smartest approach here. Since the ResNet18 model runs inside our FastAPI server, intercepting the English prediction data and translating it server-side before it hits the frontend keeps the client clean and fast.

Here is my game plan according to the codebase standards:

• Backend Layer (FastAPI): Add the Google Cloud Translation SDK to requirements.txt. I'll update the /scan endpoint to check for a locale parameter or language header. If it's non-English (like hi or es), we will pipe the dynamic symptoms and treatment text through Google Translate before sending the JSON response.

• Database Performance Caching (Supabase): To prevent hitting Google's rate limits and racking up API costs, I'll add a database migration in backend/supabase/migrations/ to cache translated disease profiles. If "Tomato Late Blight" has already been translated to Hindi in PostgreSQL, we serve it instantly instead of hitting the external API.

• Frontend Layer (Next.js Pages Router): Integrate i18next for static UI elements. For the dynamic scan results, I'll grab the current language context directly from the Next.js router (router.locale) and pass it along with the API request to fetch the correct localized payload.

If this sounds good, please assign this to me! I'll get started on the FastAPI backend plumbing first.

[arcgod-design]

Hi @jpdevhub! I'd love to work on this feature as part of SSoC '26.

My Approach:

• Integrate i18next + react-i18next on the frontend to manage translation strings for all disease scan result messages
• Create translation JSON files for Hindi and Spanish (and a template for future languages) covering disease names, symptoms, and treatment advice
• Add a language selector dropdown to the user settings and persist the preference in localStorage
• Ensure the backend returns disease result keys (not raw text) so translations can be applied client-side without backend changes

Could you please assign this to me (@arcgod-design)? Thank you!

[jpdevhub]

@Excalibur677 go ahead