https://github.com/noir4y/comment-translate.nvim
Translate code comments and strings in Neovim using online or local LLMs and external translators.
https://github.com/noir4y/comment-translate.nvim
developer-tools llm local-llm localllm neovim neovim-plugin ollama translation treesitter
Last synced: 15 days ago
JSON representation
Translate code comments and strings in Neovim using online or local LLMs and external translators.
- Host: GitHub
- URL: https://github.com/noir4y/comment-translate.nvim
- Owner: noir4y
- License: mit
- Created: 2026-01-10T12:50:38.000Z (4 months ago)
- Default Branch: main
- Last Pushed: 2026-02-15T02:42:53.000Z (2 months ago)
- Last Synced: 2026-04-04T14:06:06.709Z (26 days ago)
- Topics: developer-tools, llm, local-llm, localllm, neovim, neovim-plugin, ollama, translation, treesitter
- Language: Lua
- Homepage:
- Size: 474 KB
- Stars: 11
- Watchers: 0
- Forks: 2
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-neovim - noir4y/comment-translate.nvim - Translate code comments and strings using online as well as local LLMs or external translators. (Language / Assembly)
- awesome-neovim-sorted - noir4y/comment-translate.nvim
README
# comment-translate.nvim
[](LICENSE)
[](https://neovim.io)
Translate comments and strings directly in Neovim using hover or immersive inline views.
Supports classic translation APIs as well as LLM backends, including fully local models via Ollama.
## Why This Plugin
Many translation plugins rely on external services only. `comment-translate.nvim` is designed for teams and individuals who want a practical choice:
- Use hosted providers when you want quality and speed.
- Use local LLMs when you need stronger privacy and control.
- Keep your translation workflow inside Neovim.
## Key Benefits
- LLM translation support (`openai`, `anthropic`, `gemini`, `ollama`)
- Local LLM workflow via Ollama (no source text sent to cloud APIs)
- Hover translation for quick understanding
- Immersive inline translation mode
- Replace selected text with translation
- Tree-sitter aware comment/string detection
## Security and Privacy
This plugin gives you control over where your text goes:
- `translate_service = 'google'` or hosted `llm` providers: text is sent to the configured remote service.
- `llm.provider = 'ollama'` with the default local endpoint keeps translation local; if `llm.endpoint` is set to a remote host, text is sent there.
- Cache is in-memory only and is not persisted to disk by this plugin.
For sensitive repositories, local Ollama models are the recommended setup.
## Requirements
- Neovim 0.8+
- `curl`
- [plenary.nvim](https://github.com/nvim-lua/plenary.nvim) (required)
- Tree-sitter parser support for the languages you want to inspect (recommended)
Note: Internet is not required when you use local translation only (for example, Ollama running locally).
Parsers may come from bundled Neovim parsers, manual installation, or
parser-providing plugin setups such as `nvim-treesitter`.
`comment-translate.nvim` uses Neovim's built-in Tree-sitter APIs and does not
require the `nvim-treesitter` plugin itself.
## Installation
### lazy.nvim
```lua
{
'noir4y/comment-translate.nvim',
dependencies = {
'nvim-lua/plenary.nvim',
},
config = function()
require('comment-translate').setup({})
end,
}
```
### packer.nvim
```lua
use {
'noir4y/comment-translate.nvim',
requires = {
'nvim-lua/plenary.nvim',
},
config = function()
require('comment-translate').setup({})
end,
}
```
If you already manage parsers through `nvim-treesitter`, you can keep doing so.
## Usage
### Hover Translation
```lua
vim.keymap.set('n', 'th', 'CommentTranslateHover', { silent = true })
```
### Immersive Translation
```vim
:CommentTranslateToggle
```
### Replace Selected Text
```vim
:CommentTranslateReplace
```
## Configuration
```lua
require('comment-translate').setup({
target_language = 'ja',
translate_service = 'google', -- 'google' or 'llm'
hover = {
enabled = true,
delay = 500,
auto = true,
},
immersive = {
enabled = false,
},
cache = {
enabled = true,
max_entries = 1000,
},
targets = {
comment = true,
string = true,
},
llm = {
provider = 'ollama', -- 'openai' | 'anthropic' | 'gemini' | 'ollama'
model = 'translategemma:4b',
api_key = nil, -- not required for ollama
timeout = 20,
endpoint = 'http://localhost:11434/api/chat', -- optional
},
keymaps = {
hover = 'th',
hover_manual = 'tc',
replace = 'tr',
toggle = 'tt',
},
})
```
## LLM Provider Examples
### Local (Ollama)
```lua
require('comment-translate').setup({
translate_service = 'llm',
llm = {
provider = 'ollama',
model = 'translategemma:4b',
},
})
```
### Hosted (OpenAI)
```lua
require('comment-translate').setup({
translate_service = 'llm',
llm = {
provider = 'openai',
api_key = vim.env.OPENAI_API_KEY,
model = 'gpt-5.2',
},
})
```
## Commands
- `:CommentTranslateHover` — Display translation under cursor
- `:CommentTranslateHoverToggle` — Toggle auto hover on/off
- `:CommentTranslateReplace` — Replace selected text with translation
- `:CommentTranslateToggle` — Toggle immersive translation globally
- `:CommentTranslateUpdate` — Update immersive translation for current buffer
- `:CommentTranslateSetup` — Setup plugin with default settings
- `:CommentTranslateHealth` — Health check, including parser availability for the buffer that invoked it
Use `:checkhealth comment-translate` for general dependency and configuration checks.
Use `:CommentTranslateHealth` from the file buffer you want to inspect when you
also want parser availability checked for that buffer.
## Development
- Format: `make fmt`
- Format check: `make fmt-check`
- Lint: `make lint`
- Test: `make test`
## License
MIT