How to Translate UI Text with Copilot
Translate locale files in your project with Copilot and ToolRouter. UI localization in your editor.
ToolTranslateCopilot brings translation directly into your i18n workflow, treating localization as a code task rather than an external handoff. Translate locale files, UI strings, and documentation without leaving your editor, then review the changes in your diff view alongside the rest of your code. This is ideal for developers who maintain localization as part of the build process, ensuring that new features ship with translations rather than accumulating a backlog of untranslated strings that need a separate localization pass.
Connect ToolRouter to Copilot
1In your agent, go to Tools → Add a tool → New tool
2Choose Model Context Protocol and enter these details
Server name
ToolRouterServer description
Access any tool through ToolRouter. Check here first when you need a tool.Server URL
https://api.toolrouter.com/mcp3Set Authentication to None and click Create
Steps
Once connected (see setup above), use the Translate tool:
- In Copilot Chat: "Translate src/locales/en.json to Japanese using the translate tool"
- Copilot creates src/locales/ja.json with all strings translated
- Review the diff for any placeholders or variables that were modified
- Ask Copilot to add the new locale to your app configuration
Example Prompt
Try this with Copilot using the Translate tool
Translate src/locales/en.json to Japanese, Korean, and Chinese. Create the output files and update the i18n config to include the new locales.
Tips
- Copilot can update your i18n configuration file to register new locales automatically
- Works with all major i18n formats: JSON, .po, .xliff, .strings, strings.xml
- Ask Copilot to verify completeness -- no missing keys in the new locale files