A client email may need formal wording, while a chat reply can be more casual. Save those preferences as separate translation scenes.
You can also add preferred translations for terms and instructions for polishing. Select the scene before translating, then check the result in the floating window.
Translate a message before sending it
Press Command+J and choose input translation. Type or paste your draft, select the scene you need, and translate it.
If you want to adjust the wording, click Polish in the result window. Check names, numbers, and commitments before sending the message.
What a scene can remember
- Translation requirements, such as concise wording or a formal register.
- Fixed expressions for product names, roles, domain terms, and recurring phrases.
- Polishing requirements for clarity, tone, sentence length, and natural phrasing.
- The model or service that fits this type of material.
Different situations need different defaults
| Situation | Useful scene direction | What to check |
|---|---|---|
| Casual chat | Natural, brief, and conversational | Do not make a simple reply sound formal |
| Client email | Polite, clear, and steady | Keep commitments and conditions exact |
| Product or technical document | Preserve fixed terms and structure | Do not rewrite names, numbers, or commands |
| Formal material | Restrained wording and consistent titles | Remove casual phrasing without adding claims |
| Research reading | Favor meaning and domain terminology | Keep uncertainty and qualifications in the source |
Polish without changing the meaning
A smoother sentence is not automatically a better translation. Check names, numbers, negation, conditions, and technical terms against the source before using a polished result.
Start with one translation. Compare other models only when wording, ambiguity, or terminology leaves a real choice. This keeps routine work quick and gives important text a second look.
Choose local or cloud processing by content
Scenes can support repeated workflows, but the active model still determines where processing happens. Use a local model for sensitive drafts that should remain on the Mac. A cloud service or your own API key sends the required text to that provider.
Check the active model before polishing client messages, internal documents, or unreleased material. Text polishing can expose the same content as translation.
Create one scene for work you repeat
Start with the email, chat, document, or specialist material you translate most often, then save the corrections you usually make.