Add localization support for Roo Code extension in multiple languages

[samhvw8]

• Created new localization files for Catalan, German, Spanish, French, Hindi, Italian, Japanese, Korean, Polish, Portuguese (Brazil), Turkish, Vietnamese, Chinese (Simplified), and Chinese (Traditional).
• Enhanced user experience by providing translated command titles and descriptions for various functionalities within the extension.

Context

Implementation

Screenshots

before	after

How to Test

Get in Touch

---

Important

Add localization support for Roo Code extension in multiple languages, updating command titles and messages to use localized strings.

• Localization:
  • Added localization files for Catalan, German, Spanish, French, Hindi, Italian, Japanese, Korean, Polish, Portuguese (Brazil), Turkish, Vietnamese, Chinese (Simplified), and Chinese (Traditional).
  • Updated package.json to use localized strings for displayName, description, and command titles.
  • Updated extension.ts to use localized strings for activation and deactivation messages.
• Commands:
  • Localized command titles and descriptions in package.json using placeholders for translation.
• Scripts:
  • Added l10n:export, l10n:pseudo, and l10n:xlf scripts in package.json for localization management.

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7aabf24

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

[ellipsis-dev]

Inconsistent terminology: The term 'पाथ' is used in line 11 while 'पथ' is used in line 31. Consider standardizing the term ('पथ') across the file for consistency.

Suggested change

	"command.setCustomStoragePath.title": "कस्टम स्टोरेज पाथ सेट करें",
	"command.setCustomStoragePath.title": "कस्टम स्टोरेज पथ सेट करें",

[samhvw8]

@mrubens i see that (cmd + shift + P) -- Command Plate Has support localization, but the display name of extension on extension market doesn't change anything

[mrubens]

@mrubens i see that (cmd + shift + P) -- Command Plate Has support localization, but the display name of extension on extension market doesn't change anything

Is it just that we hardcode the strings still in src/core/CodeActionProvider.ts?

export const ACTION_NAMES = {
	EXPLAIN: "Roo Code: Explain Code",
	FIX: "Roo Code: Fix Code",
	FIX_LOGIC: "Roo Code: Fix Logic",
	IMPROVE: "Roo Code: Improve Code",
	ADD_TO_CONTEXT: "Roo Code: Add to Context",
	NEW_TASK: "Roo Code: New Task",
} as const

[samhvw8]

@mrubens i see that (cmd + shift + P) -- Command Plate Has support localization, but the display name of extension on extension market doesn't change anything

Is it just that we hardcode the strings still in src/core/CodeActionProvider.ts?

export const ACTION_NAMES = {
	EXPLAIN: "Roo Code: Explain Code",
	FIX: "Roo Code: Fix Code",
	FIX_LOGIC: "Roo Code: Fix Logic",
	IMPROVE: "Roo Code: Improve Code",
	ADD_TO_CONTEXT: "Roo Code: Add to Context",
	NEW_TASK: "Roo Code: New Task",
} as const

yeah, the code action is hard code, we can make follow up pr too add more in our i18next