Repository navigation
FullBleed.DotNet 0.1.3 ? smaller PDFs with verified font output
FullBleed.DotNet 0.1.3 uses Fullbleed engine 2.5.7, which compacts embedded font metadata. The managed API, native ABI, and application dependency graph are unchanged.
dotnet add package FullBleed.DotNet --version 0.1.3Measured whole-PDF sizes for the retained synthetic fixtures:
| Document | Package 0.1.2 | Package 0.1.3 |
|---|---|---|
| Styled Northstar invoice | 81,227 bytes | 34,542 bytes |
| Bold-text fixture | 84,462 bytes | 43,626 bytes |
| Two fixed records | 48,286 bytes | 7,299 bytes |
| Two reflow records | 70,506 bytes | 29,779 bytes |
| Unicode font fixture | 54,189 bytes | 7,377 bytes |
Extracted text, native previews, and independently rendered PDFium pixels match the previous public package. FontTools checks the retained glyph programs, metrics, mappings, checksums, and notices. Four source fonts are exercised; a fifth registered sample font is unused in these outputs. Savings depend on document content and fonts.
The same assembled package passes twelve isolated consumers: .NET 8, 9, and 10 on Windows x64, Linux x64, Intel macOS, and Apple Silicon macOS. Every fixture's PDF and saved-PDF preview bytes match across these consumers. Native tests, managed tests, formatting, Clippy, package architecture checks, and required CLI integration also pass. The previous public package is retained as a negative control for the new font-metadata gate.
The verification ZIP contains source inputs, licensed fonts, before/after outputs, independent reader reports, CI evidence, and public NuGet verification. These checks establish behavior for the supplied fixtures; they do not establish general parity, rendering speed, or standards conformance. The NuGet package contains no document fonts; applications register their own assets.
NuGet package · C# quickstart · ASP.NET starter · Reproduce the font comparison