feat: Support multilingual menu display using i18next (supports Chinese and English)

[feifei325]

Description

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Checklist:

• My code follows the patterns of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation

Additional context

Roo Code settings menu supports multiple languages

• en(English)
• zh(Simplified Chinese)

Related Issues

Reviewers

---

Important

Adds multilingual support using i18next, with English and Chinese translations, and updates components to utilize translation keys.

• Multilingual Support:
  • Integrates i18next and react-i18next for multilingual support in index.tsx.
  • Adds English (en.json) and Chinese (zh.json) translations in webview-ui/src/i18n/locales/.
  • Configures language detection and fallback in i18n/index.ts.
• Component Updates:
  • Updates components like SettingsView.tsx, PromptsView.tsx, McpView.tsx, and others to use useTranslation for text.
  • Replaces hardcoded strings with translation keys in components such as HistoryView.tsx, McpToolRow.tsx, and ApiConfigManager.tsx.
• Dependencies:
  • Adds i18next and react-i18next to package.json dependencies.
• Miscellaneous:
  • Updates package.json to bump typescript version.

^{This description was created by for 91aff1e. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: fd08886

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mrubens]

Thanks for the PR! I’ll take a look at this soon. In general I haven’t thought a ton about the internationalization strategy - curious what people have seen work in the past. Just using internationalized strings when developing and letting the community translate as follow-ups?

[feifei325]

Thanks for the PR! I’ll take a look at this soon. In general I haven’t thought a ton about the internationalization strategy - curious what people have seen work in the past. Just using internationalized strings when developing and letting the community translate as follow-ups?

Thanks for the response! I’m currently promoting the Roo Code plugin to my colleagues, and in order to help everyone better understand the meaning of the menu settings, I’ve implemented internationalization. I personally believe that using internationalized strings during development helps developers from different countries better understand the meaning of the menu settings.

[im47cn]

I found a i18n ready project, https://gitee.com/coolcline/coolcline/blob/develop/assets/i18n/zh.json

[Shuai-S]

Great, hope to merge ASAP, everyone can better use roo through their native language.

[Shuai-S]

@feifei325 @mrubens @cte Hello, will this PR continue to merge?

[qdaxb]

@mrubens I see this PR has been sitting there for a while and conflicts are always occurring.
Maybe we can introducing the i18n framework and language files first, and then gradually translate them?

[mrubens]

Yes sorry, I would like to pick this up soon! Sorry for the conflicts. And I like @qdaxb's suggested approach.

[mrubens]

Working on this in other PRs, thank you!