Choose list comparison or text difference

Two different questions

“Which entries are missing?” is a membership question. “What changed in this document?” is a sequence question. A list comparison ignores where a member appears. A text difference treats order as part of the material being compared. Choosing the wrong operation can produce a technically correct but unhelpful result.

Work through a small pair

List A: apple, pear, pear
List B: pear, cherry

With one entry per line, the shared group contains pear. A-only contains apple; B-only contains cherry. Union is apple, pear, cherry. A has one duplicate occurrence, but pear remains one set member.

If B instead contains pear, apple, membership matches A even though the order and number of occurrences differ. Use text difference if you need to see those sequence changes.

Set matching rules deliberately

Case and surrounding spaces are significant by default. Enabling either ignore option changes the comparison key while retaining the selected original spelling. Unicode NFC normalization helps match canonically equivalent accents; it does not remove every visually similar character.

Do not normalize identifiers automatically if their system considers case or whitespace meaningful. A blank line within a list is an entry; a final newline terminates the last entry.

Read a document diff

For “The draft is ready.” versus “The final draft is ready.”, word comparison exposes the inserted word. Line comparison treats the sentence as a changed line. Repeated passages can have several equally valid edit paths, so the highlighted path is not a judgment about authorship or intent.

After comparing lists, deduplicate and sort only if the receiving workflow needs unique or ordered entries. A CSV with quoted multiline fields needs record-aware tools rather than line operations.