Line ending differences in a supplier contract: fixes

You compare two supplier contract copies and the result marks nearly every line as changed, even though the wording looks the same. A common cause is different line endings, the invisible characters used to mark where each line stops.

Line ending differences can make a comparison noisy, but they do not necessarily mean the contract text changed. Check the original files, compare copies with matching line endings, and review any actual wording changes before accepting or signing a contract.

Find the cause

1. Open the Text Compare tool and compare the two contract copies. It compares texts or files and shows what was added, removed, or changed.
2. Check whether the visible wording is actually different. Look for ordinary changes such as a revised date, amount, party name, clause, or punctuation.
3. If nearly every line is marked as changed, inspect each file's line-ending setting in a text editor. In Visual Studio Code, the status bar at the bottom shows values such as CRLF or LF for the open file.
4. Check whether the copies came from different systems, text editors, or export steps. Windows text files often use CRLF, while Linux and current macOS text files commonly use LF. File conversion can also change line endings.

Do not assume that a large number of marked lines is harmless. First confirm that the contract wording, numbers, and clause order match. Line endings can explain noisy results, but they do not rule out real edits.

What the result means

Almost every line appears changed, but the words look identical

This often points to a formatting difference, such as CRLF in one file and LF in the other. A comparison program may treat lines as different when the invisible line-ending characters differ. Confirm the line-ending setting before treating the output as a contract revision.

Only a few lines are marked

There may be actual edits, or other small differences such as spaces, tabs, punctuation, or a different line break inside a paragraph. Read each marked section in context. A changed number, date, or word like “not” can matter even when the overall diff is short.

Lines appear joined, split, or out of order

The files may have different formatting, or one copy may have been exported or copied in a way that changed paragraph breaks. Check the original contract in the application that created it. Do not rely on a plain-text comparison to verify page layout, comments, tracked changes, or signatures.

The text looks different after opening the file

Line endings are not the only possible cause. The files could use different character encodings, include a byte order mark, or contain changed spaces and tabs. A text comparison shows textual differences, but it cannot by itself tell you which version is legally authoritative.

How to fix the comparison

1. Keep the originals unchanged. Make separate working copies of both contract files before converting anything. Preserve the received files, especially if they are signed, approved, or stored in a document management system.
2. Match the line endings in a working copy. In Visual Studio Code, open the copy and check the line-ending indicator in the status bar. Select the same line-ending type used by the other copy, then save the working copy. Do not overwrite a signed or official source file just to make a diff look cleaner.
3. Compare the copies again. Reopen the two working copies in Text Compare. If the line-ending mismatch caused the noise, the comparison should be easier to read. Review remaining marked lines as possible content changes rather than dismissing them.
4. Check spaces and tabs if differences remain. A line can look unchanged while containing extra spaces, tabs, or trailing whitespace. Inspect the affected wording in a text editor that can display whitespace, and compare the same passages in the original contract.
5. Verify the final contract in its original format. For a Word document, use Word's document comparison feature or review its tracked changes, then inspect the final document itself. Confirm party names, dates, payment terms, attachments, and signature blocks before approval.

When a plain-text comparison is not enough

Text Compare is useful for comparing two text files or text content, but a contract may contain more than plain text. A Word document can include comments, tracked changes, headers, footers, tables, footnotes, formatting, and signatures. A PDF can also contain layout and signature information that is not represented by a simple text diff.

If the contract is a DOCX or PDF, use the comparison or review features of the application that handles that document format, and inspect the complete final file. Do not convert a legal document to plain text and treat a matching text comparison as proof that every element is unchanged.

Keep the original and normalized copies clearly named, and record which copy you used for the review. Text Compare works on the text or files in your browser, so those files are not uploaded.