mirror of
https://github.com/RooVetGit/Roo-Code.git
synced 2026-10-07 02:58:15 +00:00
5507f5ab64
* feat: extract translation and merge resolver modes into reusable skills - Add roo-translation skill with comprehensive i18n guidelines - Add roo-conflict-resolution skill for intelligent merge conflict resolution - Add /roo-translate slash command as shortcut for translation skill - Add /roo-resolve-conflicts slash command as shortcut for conflict resolution skill The existing translate and merge-resolver modes are preserved. These new skills and commands provide reusable access to the same functionality. Closes CLO-722 * feat: add guidances directory with translator guidance file - Add .roo/guidances/roo-translator.md for brand voice, tone, and word choice guidance - Update roo-translation skill to reference the guidance file The guidance file serves as a placeholder for translation style guidelines that will be interpolated at runtime. * fix: rename guidances directory to guidance (singular) * fix: remove language-specific section from translator guidance The guidance file should focus on brand voice, tone, and word choice only. * fix: remove language-specific guidelines section from skill file * Update .roo/skills/roo-translation/SKILL.md Co-authored-by: roomote[bot] <219738659+roomote[bot]@users.noreply.github.com> --------- Co-authored-by: Roo Code <roomote@roocode.com> Co-authored-by: Bruno Bergher <bruno@roocode.com> Co-authored-by: roomote[bot] <219738659+roomote[bot]@users.noreply.github.com>
50 lines
1.7 KiB
Markdown
50 lines
1.7 KiB
Markdown
---
|
|
description: "Translate and localize strings in the Roo Code extension"
|
|
argument-hint: "[language-code or 'all'] [string-key or file-path]"
|
|
mode: translate
|
|
---
|
|
|
|
Perform translation and localization tasks for the Roo Code extension. This command activates the translation workflow with comprehensive i18n guidelines.
|
|
|
|
## Quick Start
|
|
|
|
1. **Identify the translation scope:**
|
|
- If a specific language code is provided (e.g., `de`, `zh-CN`), focus on that language
|
|
- If `all` is specified, translate to all supported languages
|
|
- If a string key is provided, locate and translate that specific string
|
|
- If a file path is provided, work with that translation file
|
|
|
|
2. **Supported languages:** ca, de, en, es, fr, hi, id, it, ja, ko, nl, pl, pt-BR, ru, tr, vi, zh-CN, zh-TW
|
|
|
|
3. **Translation locations:**
|
|
- Core Extension: `src/i18n/locales/`
|
|
- WebView UI: `webview-ui/src/i18n/locales/`
|
|
|
|
## Workflow
|
|
|
|
1. If adding new strings:
|
|
- Add the English string first
|
|
- Ask for confirmation before translating to other languages
|
|
- Use `apply_diff` for efficient file updates
|
|
|
|
2. If updating existing strings:
|
|
- Identify all affected language files
|
|
- Update English first, then propagate changes
|
|
|
|
3. Validate your changes:
|
|
```bash
|
|
node scripts/find-missing-translations.js
|
|
```
|
|
|
|
## Key Guidelines
|
|
|
|
- Use informal speech (e.g., "du" not "Sie" in German)
|
|
- Keep technical terms like "token", "Prompt" in English
|
|
- Preserve all `{{variable}}` placeholders exactly
|
|
- Use `apply_diff` instead of `write_to_file` for existing files
|
|
|
|
## Examples
|
|
|
|
- `/roo-translate de` - Focus on German translations
|
|
- `/roo-translate all welcome.title` - Translate a specific key to all languages
|
|
- `/roo-translate zh-CN src/i18n/locales/zh-CN/core.json` - Work on specific file
|