The short answer
Use a text diff when exact additions, removals and formatting-level edits matter. Use semantic comparison when equivalent ideas appear in different wording or across PDFs, web pages, emails and notes. For consequential documents, use both when possible and verify against the originals.
| Method | Best at | Common limitation |
|---|---|---|
| Text diff | Exact line or character changes in comparable text. | Moved or rewritten passages can create noisy output without explaining significance. |
| Document redline | Tracked insertions, deletions, comments and formatting between document versions. | Usually assumes compatible document formats and known original/revised roles. |
| Semantic comparison | Changed meaning, obligations, amounts or dates across differently structured sources. | Can miss details or infer a relationship incorrectly; evidence review is essential. |
What a text diff actually does
Traditional diff tools compare files line by line and report groups of inserted, deleted or changed lines. The GNU Diffutils manual describes this directly. That precision is valuable for code, configuration and normalized text where the source sequence matters.
What redlining adds
Word’s comparison tools can create a third document with revision marks while leaving the two compared files unchanged. Microsoft documents options for comparing comments, formatting and text at word or character level in its legal blackline guidance. This is often the right tool for formal revisions in compatible Word documents.
What semantic comparison adds
Meaning can change without a neat line-level edit. A delivery commitment may move from a quote table into an email; “within 30 days” may become “Net 45”; responsibility may switch parties while the section structure changes completely. Semantic comparison can group these as decision-relevant differences across source types.
Worked example
Suppose one quote says “Supplier Alpha installs the equipment by October 15.” A later email says “Northstar will arrange installation; delivery is expected November 2.” A text diff may be impossible if the sources are different formats. A semantic comparison can propose two points—responsibility and delivery date—but the reviewer must still open both excerpts and establish whether the email validly changes the agreement.
Choose by risk
- For code, exact clauses and tracked drafting: begin with diff or redline.
- For cross-format review and triage: add semantic comparison.
- For legal, financial or safety consequences: keep human review and source authority explicit.
- For scanned PDFs: perform reliable OCR first and retain the original page for checking.
Where Aelipsis fits
Aelipsis is designed for semantic comparison close to the working context in Chrome. It surfaces material differences with supporting excerpts. It is not a pixel-level redline, does not promise every change, and should not replace authoritative review.