Why standard translation falls short
Standard translators routinely translate variable names, JSON keys, and command-line flags inside code snippets, turning working examples into broken syntax.
How Translator handles translate technical documentation without breaking code
Translator preserves structured page layouts, tables, and code blocks while translating surrounding explanations in parallel streams. Hover any translated technical paragraph to inspect the original term.
環境変数を設定した後、以下のコマンドでローカルサーバーを起動します。
After setting the environment variables, start the local server with the following command.
3-step Chrome setup
- Install & pin: Add Translator - Translate to English from the Chrome Web Store and pin it to your toolbar (Puzzle icon → Pin).
- Open any foreign page: Visit any website across 109 supported languages without configuring API keys or creating an account.
- Translate or auto-translate: Click Translate Page for 1-click full-page translation, highlight any phrase for an instant tooltip, or enable Auto-translate these sites in the popup.
Key capabilities included free
- Layout-preserving engine: Keeps menus, buttons, responsive grids, tables, and code blocks intact.
- Hover-to-original & 0-second toggle: Verify original wording on hover or flip views instantly from local cache.
- Multi-stream parallel speed: Translates long articles, forums, and technical docs rapidly across 109 languages.
- Privacy first: No registration, no browsing history tracking, and zero injected ads.
Frequently asked questions
Why is layout preservation critical for developer docs?
Sidebars, API parameter tables, and code snippets lose usability when containers shift. Translator keeps the documentation layout intact.
Does it work fast on long single-page API references?
Yes. Multi-stream parallel translation processes long documentation pages without stalling.