Memory bulk editing and maintenance
Use the memory editor for systematic corrections, such as replacing an obsolete product name or repairing a recurring punctuation problem. Filter the table to find the units you need and unlock the ones you want to edit.
Which units each command changes
| Operation | Scope or effect |
|---|---|
| Source/target searches and table filters | Change which loaded memory units are shown |
| Select all | Selects the filtered unit set, including off-screen rows |
| Lock/Unlock selection | Changes the editing lock for selected units; edited selections must be confirmed first |
| Confirm | Saves selected edited units and locks them again |
| Case, punctuation, quotation, and supported tag tools | Use their selected-unit or text-selection scope; inspect proposals before applying them |
| Find and Replace → Replace All | Uses matching content in the filtered memory units, with its From here boundary and lock exclusions |
| Delete units | Removes selected memory records through the deletion workflow |
| Export a memory | Downloads the saved resource as TMX; it is not an export of only the visible editor rows |
Changing a filter does not automatically select the matching rows. Make a fresh selection after preparing the filtered set. Selecting only two units does not restrict a filtered-set replacement to those two units.
Example: correct an obsolete product name
- Open the intended memory and verify its language pair.
- Search the relevant source or target side for the old name.
- Read a sample to confirm that these occurrences refer to the same product.
- Select the locked units you want to edit and unlock them.
- Open Find and Replace and check the language side, find text, replacement, whole-word/case options, and From here setting.
- Test one replacement and read the resulting pair.
- Check that the filters show only the units you want to change, then run Replace All.
- Inspect the edited units, select the corrections you accept, and Confirm them.
- Use Clear all to restore the table and check whether other relevant variants remain.
Replacing a word in a source or target can affect punctuation, grammar, and future lookup behavior. A repeated string is not always the same concept. Find and replace explains the detailed search options.
Review selected memory units with Chat
Select the relevant units, open Searchspeare (Chat), inspect the supplied context, and state a narrow task. For example, ask for a consistency review of a term before requesting changes.
Inspect any proposed differences before applying them. Applied memory edits still need the confirmation workflow. A conversation or preview does not approve the entire reusable resource.
Delete unwanted units
Select the obsolete or incorrect units and use Delete units. Inspect the deletion confirmation before accepting it. This removes memory records; it does not merely hide the rows, clear their target cells, or detach the memory from a project.
Delete can remove locked units
Delete can remove selected locked units too. Check the selected rows before confirming deletion.
If you only want a subset out of view, filter the table. If a client should not use a resource, change the project's memory attachments rather than deleting otherwise useful units.
Import existing translations
Use the memory library's import controls to add supported bilingual material to the intended resource. Check the file chooser, detected languages, and destination memory. Project-file import and memory import are separate workflows with different accepted inputs.
Review a sample of imported pairs before relying on them. For separate source and target documents, alignment creates candidate pairs that should be checked before saving to a memory.
Export a memory
Export selected memory resources as TMX from the memory tools. Confirm pending editor corrections first so the saved resource contains the version you intend to exchange.
The resource selection identifies which memories to export. It is different from selecting or filtering individual units in the editor. A TMX file contains reusable bilingual pairs, not the reconstructed translated document or a complete workspace backup.
See Translation memories for creation, attachments, matches, and pretranslation, and Storage and backups for protecting the wider workspace.