docs(pdf): identify exact platform-specific failure sets

This commit is contained in:
cesnimda
2026-10-29 20:45:54 +01:00
parent 4024a89a95
commit 38d7133d20
+1 -1
View File
@@ -8,7 +8,7 @@ The installed primary sources are `pdfminer.layout.LTChar.__init__` (horizontal
The initial unchanged corpora reproduce **28 Windows /20 Linux** failures, all S01-only. Actual baseline differences are at most **0.2232mm Windows /0.4878mm Linux**, within the existing2mm physical bound; separate actual-raster name-ink differences are at most3px. These are diagnostic results, not an approved replacement gate. Font sizes, marker/page membership, other marker positions, completeness/bounds and full-height sidebars remain independently checked. The initial unchanged corpora reproduce **28 Windows /20 Linux** failures, all S01-only. Actual baseline differences are at most **0.2232mm Windows /0.4878mm Linux**, within the existing2mm physical bound; separate actual-raster name-ink differences are at most3px. These are diagnostic results, not an approved replacement gate. Font sizes, marker/page membership, other marker positions, completeness/bounds and full-height sidebars remain independently checked.
Windows and Linux emit different descriptor metadata for the same bundled fonts. For Selawik-Bold the measured Windows ascent/descent is1079.10156/+250.97656, Linux989.74609/−210.44922; Roboto-Bold also differs. Arimo/Gelasio/Poppins descent magnitudes agree, while signs and some other metadata differ. The formula normalises signs as the installed extractor does. Some actual baseline rounding differs by about1px too, but does not explain the multi-mm cell-top discrepancy. Linux's smaller descent-cell offset takes the four technical and four creative documents below the original cutoff; code/modern/executive/elegant remain above it. The final per-document report must verify these sets from actual fresh results, not assume this initial count. Windows and Linux emit different descriptor metadata for the same bundled fonts. For Selawik-Bold the measured Windows ascent/descent is1079.10156/+250.97656, Linux989.74609/−210.44922; Roboto-Bold also differs. Arimo/Gelasio/Poppins descent magnitudes agree, while signs and some other metadata differ. The formula normalises signs as the installed extractor does. Some actual baseline rounding differs by about1px too, but does not explain the multi-mm cell-top discrepancy. Linux's smaller descent-cell offset takes the four technical and four nordic documents below the original cutoff; code/modern/executive/elegant remain above it. The final per-document report must verify these sets from actual fresh results, not assume this initial count.
No layout change is justified merely to force unequal coordinate conventions to agree: it would move correctly aligned visible text or alter intended title sizing. No clipping, lost content, misplaced photo/sidebar or pagination defect was established by these S01 failures. Finite automated findings do not establish human typography/whitespace/print acceptance. No layout change is justified merely to force unequal coordinate conventions to agree: it would move correctly aligned visible text or alter intended title sizing. No clipping, lost content, misplaced photo/sidebar or pagination defect was established by these S01 failures. Finite automated findings do not establish human typography/whitespace/print acceptance.