Unified Diff - Raw UTF-8 Non-ASCII Paths
The same change with `core.quotepath=false`, so the path is written as raw UTF-8 and the header is not quoted. Compare with the quoted twin to confirm a parser resolves both spellings to the same file.
--- a/docs/café/guía-de-usuario.md 2026-03-02 09:14:03.000000000 +0000
+++ b/docs/café/guía-de-usuario.md 2026-03-02 10:41:55.000000000 +0000
@@ -1,3 +1,3 @@
# Guía
-Instalación en cinco minutos.
+Instalación en dos minutos.
Specifications
- Seed
- 20260807
- Diff Format
- unified
- Files
- 1
- Quote Path
- false
- Path
- docs/café/guía-de-usuario.md
- Line Endings
- LF
- Encoding
- UTF-8
Testing contract
Expected to pass- Scenario
- Parse the unquoted twin of the octal-escaped fixture and compare the resolved paths.
- Expected result
- Both fixtures resolve to the identical path and identical content change.
What is a .diff file?
A .diff file records the difference between two versions of one or more text files. The unified format — the default almost everywhere — names the old and new files on `---` and `+++` lines, then lists hunks introduced by `@@ -old,count +new,count @@` in which context lines are unprefixed and changed lines are prefixed with `-` or `+`. Older context and normal diff formats exist but are rarely produced today.
How to use this file
Use an example .diff file to test diff parsers, syntax highlighters, and merge tooling — verifying hunk-offset arithmetic, correct handling of context lines that begin with a space, and behaviour on files whose changes include trailing-whitespace or line-ending differences.
How to use this file for testing
“Unified Diff - Raw UTF-8 Non-ASCII Paths” is a deterministic Novus Examples fixture for Encoding detection, Visual diff / regression, Editor testing. UTF-8, UTF-8-BOM, UTF-16, and Latin-1 files with documented encodings and line endings for testing charset detection.
Documented properties for this file: seed 20260807 · UTF-8 · LF. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Diff and patch fixtures name their target paths and the exact edge case they exercise — rename, mode change, binary hunk, CRLF↔LF, or missing trailing newline. Apply or render them against the documented before-state; every author, path, and hash is fictional.
Related files
- diffUnified Diff - CRLF Line Endings ThroughoutByte-for-byte the same diff as its LF twin except that every line ends CR LF, which is what a diff produced or saved on Windows looks like. Readers that compare a hunk line against expected content without stripping the CR find that no line matches.
- diffUnified Diff - LF Line Endings ThroughoutThe LF half of the line-ending twin pair: identical text content to the CRLF fixture, differing only in the terminator bytes. Diff the two downloads to see nothing but line-ending changes, and use the pair to score end-of-line normalisation.
- diffUnified Diff - Line-Ending Conversion as Content ChangeThe file itself is LF-terminated, but every removed line carries a literal CR as its last character because the change under review is a CRLF-to-LF conversion. Renderers that do not show the CR display a hunk in which every removed and added line looks identical.
- patchGit Patch - CRLF Line Endings ThroughoutThe whole patch file uses CRLF terminators, as it would after a round trip through a Windows editor or a mail client. `git am` needs `--keep-cr` to be told the CRs belong to the patch rather than to the content, and the `-- ` signature line now ends with space-CR-LF.
- patchGit Patch - LF Line Endings ThroughoutThe LF half of the patch twin pair, identical in text content to the CRLF fixture. Diff the two downloads to get a change that is invisible in every renderer and fatal to a byte comparison.
- diffUnified Diff - Bare Line Number in the Hunk HeaderA one-line file changed in place. Both ranges have length one, so the header is written `@@ -1 +1 @@` with no comma and no count — the abbreviation the unified format allows and that regexes of the form `-(\d+),(\d+)` fail to match.
Generated by generation/version_control.py. Free for any use, no attribution required — license.