Work in two languages,without the translation tab
Requirements arrive in French, tickets ship in English, and the steering email goes back in French. Khint puts your translation behind one keyboard shortcut, in every app: select the text, run a translate action you saved once, and the result pastes back exactly where you were writing, with your product terms left intact.
The bilingual tax is real,
and the translator tab makes it worse
If your organization works across languages, every document crosses the border at least once: the workshop notes are in the local language, the ticket must be in English, the client update goes back translated. The usual fix is a translation website in a browser tab, and it taxes every crossing: copy the text out, lose the bullets and the bold, watch it translate your product's name and your Jira vocabulary, fix all of that by hand, paste it back. Khint moves the translation to where you already are. A translate action is a saved prompt that carries your rules, runs on the text you select, and puts the result back under your cursor. It's built on the same three pillars as the rest of the app (Agents, Capture, and Memory) behind a single palette shortcut.
From foreign-language input to filed output
Five steps, two saved actions, no browser round-trip.
Save your two translate actions, once
In the Action editor, type a one-line description: “Translate the selected text to English, keep the formatting and the Jira terms”, and press Generate. Khint drafts the full prompt; save it as To English. Repeat in the other direction for To French (or German, Spanish, whatever your team writes in). Give each action its own keyboard shortcut with the built-in recorder, and the pair sits ready in your pack.
Translate in place, wherever you write
A client comment lands in French in the middle of your English backlog. Select it, press Cmd+Shift+K, run To English: the translation pastes back exactly where the selection was. Same move for the other direction, in Jira, in your mail client, in a doc. No browser tab, no copy-paste round-trip, no reformatting what the round-trip broke.
Teach it your glossary and your register
Open the action and add the rules a generic translator never knows: which product names stay untouched, that “sprint” and “backlog” are not translated in your organization, whether stakeholder emails are formal or casual. The prompt is plain text you own, and Improve tightens it in place as your rules grow. Every run after that applies the same conventions, which is exactly what ad-hoc chatbot translation loses between sessions.
Translate what you can't even select
The vendor sent a scanned PDF, the slide is a picture on a screen share. Capture handles both: Extract text grabs a region of the screen, OCRs it, and puts the text on your clipboard for your translate action, while Capture & askopens a chat about the capture, so you can ask for the translation directly and follow up with “what is the deadline they mention?”.
Ship the translation where it belongs
The translated text rarely stays in your notes. With the work integrations connected, the same palette files it: the English version of the requirement becomes a Jira ticket, the translated summary is appended to the Confluence page, the reply to the client lands as a Gmail draft you review before sending. One shortcut from foreign-language input to filed output.
Consistent terms, private by default
Translation quality in a product team is mostly terminology discipline: the day “story” becomes “récit” in one ticket and stays “story” in the next, readers stop trusting the text. A saved action applies the same glossary on every run, because the glossary lives in the prompt, not in whatever you remembered to tell a chatbot today. Share the pack with your team and everyone translates with the same rules: how pack sharing works → And the privacy story stays the usual Khint one: an action only ever sees the text you selected, you can opt an action into PII redaction before anything is sent, and your work history bodies stay on your machine. If your other language problem is polishing English you already wrote, that flow has its own page →
Common questions
Which languages can a translate action work between?
The AI models behind Khint handle the major business languages, so the pair you need is almost certainly covered. You name the direction yourself, in plain words, when you write the action: 'Translate the text to English' is a complete instruction. Because an Action is just a saved prompt, one direction is one action; a bilingual team typically keeps two ('To English', 'To French') side by side in the same pack, each behind its own keyboard shortcut.
How do I stop it translating product names and Jira terms?
Write your glossary into the action's prompt: a short list of terms that must stay untouched (your product's name, 'sprint', 'backlog', ticket keys like AUTH-104) and any house rules such as tu versus vous or formal versus casual register. The prompt is yours to edit, and the Improve button refines it in place while keeping your rules. That is the difference from a generic translation tab: your conventions are saved once and applied on every run.
Can it translate a screenshot or a scanned document?
Yes, in two steps or one. Two steps: the palette's Extract text row captures a region of the screen, OCRs it, and puts the text on your clipboard, ready for your translate action. One step: Capture & ask opens a chat about the captured region, so you can ask 'translate this to English' directly and keep asking follow-ups. Captures have their own daily allowance, 5 per day on the free plan, separate from the 10 AI actions.
Is this the same as Khint's Correct and Rephrase actions?
No. Correct and Rephrase, the two actions on a fresh install, polish text that is already in English. A translate action moves text between languages, and you create it yourself in about a minute: type a one-line description in the Action editor, press Generate, and Khint drafts the prompt. If your problem is 'my English reads translated' rather than 'this is in the wrong language', the English polish page covers that flow.
Save the translate action before the next handover
Free with 10 AI actions and 5 captures per day. No credit card. Write your glossary once and translate in place from then on.