Split and merge project segments
Use Split and Merge in the Segmentation ribbon for targeted corrections to a translation file. Alignment has its own structural tools; use the alignment toolbar when pairing separate source and target documents.
These project commands require supported bilingual content and an individual file, rather than a combined View. Confirmed and locked units are protected. A confirmed unit remains protected even when its lock is off.
Split at the source cursor
- Select one unconfirmed, unlocked segment.
- Click inside its source text.
- Place the cursor at the intended boundary between two nonempty portions. Do not highlight a text range.
- Choose Segmentation → Split.
- Read the two resulting source segments and check their targets.
For example, if a row contains Open the cover. Remove the filter., place the source cursor before Remove when you want two working segments.
The cursor must be inside the text, not at its very start or end. Both resulting source portions need usable content. A merged group representing several original units cannot simply be split again through this command; inspect its history and use Restore Original when returning to the original boundaries is your intention.
Check the target after splitting
The existing target stays with the first portion; the new second target starts empty. Searchspeare does not decide where a previously written translation should be divided. Move or rewrite the corresponding target text yourself, then review both pairs.
If the original target covered both source sentences, leaving it all in the first row and translating the second again would duplicate wording. Check the actual source–target correspondence before confirming either row.
Merge adjacent rows
- Clear filters that hide intervening rows, so you can check the real document order.
- Select the consecutive unlocked, unconfirmed rows from the same file.
- Choose Segmentation → Merge.
- Read the combined source and target, including any boundary markers.
- Check spacing, punctuation, tags, and the next row before continuing.
With just one row selected, Merge attempts to include its next row. Check that neighbor before using the single-row shortcut. A protected neighbor prevents the merge.
Merge needs consecutive rows in the original file
Several rows that happen to sit next to each other in a filtered view may not be consecutive in the actual file. A cross-file or nonconsecutive selection is rejected. Filters do not turn separated passages into one continuous source span.
Keep the original-boundary markers
Merging different original units introduces boundary markers so Searchspeare can later restore the original structure. Preserve the corresponding markers in the target and place translated content on the appropriate side of each marker.
Those markers have a role in restoration and delivery. Resegmentation explains why a safe restore can require correcting missing or repeated markers.
Why Split or Merge is disabled
Check whether you are in a View, whether either affected row is confirmed or locked, whether the source cursor is available, and whether the file supports this workflow. For Split, also check that no text range is selected and the unit is not an already merged group.
Use Resegment for a recurring boundary problem across the file. Use Restore Original when the desired outcome is the imported structure, rather than another manual rearrangement.