Save and confirm translations
In a project file, Searchspeare saves text edits as you work. Confirm is a separate decision: you approve a segment and, in a bilingual project, save its source–target pair to the attached translation memories.
Saved text can still need review
A saved draft is not necessarily confirmed. A proposal visible in a panel has not changed the target until you insert or apply it. Read the target itself before approving the segment.
Find Confirm
Open a project file and select a segment. Use Confirm in the segment toolbar, or press its default shortcut, Ctrl+Enter. If the button is hidden, open the toolbar’s gear, find Confirm under Translation Commands, and select it.
Confirm one translation
- Click the intended row so it is the only selected segment.
- Read the source and the current target together.
- Check terminology, numbers, names, punctuation, and required tags.
- Resolve comments and tracked changes that still need a decision.
- Run Confirm.
- Check for a warning or save error. With one row selected, the editor normally moves to another unlocked segment that needs confirmation, when one remains.
In bilingual work, attach the intended memory through Project home → Memories before confirming. If Searchspeare asks for a memory, use the offered resource action or attach one through Project home, then confirm again.
Single-language review does not need a bilingual memory attachment. It approves the text being reviewed.
Confirm several selected segments
Select a range with Shift-click, add separate rows with Ctrl/Command-click, or use the segment Select all command for the filtered set. Read the selected content before confirming the group.
Check the table filters first. Select all uses every matching row, including rows outside the screen. A short visible table can still represent only part of the open file.
Check later repetitions
Confirmation can also copy the approved target into later segments with identical source content in the open file or View. Those repetitions can be hidden by filters. Check their context before approving wording that must differ between occurrences.
See Selecting segments and batch actions for the full operation-scope tables.
Saving, status, and locks do different things
| Action | What it means |
|---|---|
| Edit a project target | Changes the working text and saves the edit; it can still need approval |
| Insert or apply a proposal | Changes the target; inspect the inserted wording before confirmation |
| Confirm | Approves the selected content and performs the applicable memory-saving workflow |
| Choose a status label | Changes the workflow label; it does not replace the confirmation workflow |
| Lock a segment | Protects it from operations that respect locks; locking is separate from approving its wording |
| Export | Produces an output file; downloading it does not approve every draft |
| Finish the project | Runs the project-level completion workflow after its checks |
An insertion preference can confirm a segment after you apply a complete proposal row. Check Settings → Advanced → Suggestions → Confirm segment after applying all row changes if applying a proposal also changes its approval state.
If confirmation does not complete
Read the message before trying again:
- Empty target: write the missing translation. An empty target in a selected group can stop confirmation of that group.
- No attached memory: in bilingual work, select or create the intended project memory.
- Tag problem: inspect the source and target tags and use the relevant tag tools. Matching tag counts alone do not prove correct placement.
- Save failure: inspect which segments remain unconfirmed and resolve the reported problem before closing the workspace. See Storage and backups.
If the command advances without editing a locked or already completed row, inspect that row’s state and the next active segment before repeating it.
Memory and glossary editors save differently
The automatic text-saving description above concerns project files. In the resource editors, ordinary wording corrections remain pending until confirmation:
| Workspace | How to keep a wording correction |
|---|---|
| Translation memory | Unlock the unit, edit it, and Confirm the pending correction |
| Glossary or termbase | Unlock the entry, edit it, and Confirm; Properties → Save first applies property changes to the working entry |
| Temporary glossary | Review and confirm useful entries, then choose a permanent glossary destination when needed |
Use the dedicated memory saving guide and term saving guide before changing reusable resources.
Before leaving the file
Check any save or validation message, inspect the remaining unconfirmed text, and use Clear all if temporary filters hide part of the file. Run the relevant QA and spelling checks before delivery. Open the exported document to verify its contents and layout.