Add internationalization (i18n) support

[big14way]

Support multiple languages for the target audience (English, French, Spanish, Portuguese, Swahili).

Acceptance Criteria:

• Set up next-intl or similar i18n library
• Extract all UI strings to translation files
• Add language switcher
• Start with English and French translations

Files: frontend/package.json, new directory frontend/src/messages/

[aliraza556]

@big14way Could you please assign this issue to me? Also, if you don’t mind, could you please mention the bounty payment details as well?

[nifanpinc]

Hi @big14way, I'd like to work on this i18n feature. I have experience with next-intl and can implement support for all 5 languages (English, French, Spanish, Portuguese, Swahili). Could you please assign this issue to me and share the bounty details (amount and payment method)? Thanks!

[cryptodane-leduke]

Hi @big14way , I opened a PR for this bounty here:

sorosave-protocol/sorosave#101

I targeted the monorepo because the acceptance criteria mention frontend/package.json and frontend/src/messages/, and that repo contains both frontend/ and the sdk/ workspace package needed by the frontend.

[cryptodane-leduke]

Also happy to add Spanish, Portuguese, and Swahili message files in a follow-up if you want the full target-language set in this bounty.

[trevorbarnes]

Hey SoroSave team — saw this i18n issue for the Next.js frontend: next-intl or similar, extracted UI strings, language switcher, and English/French to start.

This is a clean 7-day sprint because the proof is objective:

• translation file structure
• routed language support
• working language switcher
• English + French starter messages
• screenshots and build logs showing both paths work

I can scope this as a paid operator sprint: one PR/submission, proof artifacts, and a short handoff note so more languages can be added without reworking the app.

Want me to send a concrete implementation checklist for the current frontend?

[haim1120]

Hi, I can take this on with a focused first PR. Plan: add a small Next.js i18n setup, extract the current visible UI copy into English and French message files, add locale-aware routes, and include a language switcher in the navbar. I will keep the existing default English URLs working through redirects and include build/type-check notes in the PR.

[zhaog100]

I claim this bounty. GitHub: zhaog100 🌶️ (小米辣)