FullBleed.DotNet 0.1.4: correct regular font selection

FullBleed.DotNet 0.1.4 uses engine 2.5.8 and corrects regular-font selection when an italic face is registered first. Explicit face aliases retain priority. The managed API, native ABI, and runtime dependency graph are unchanged.

dotnet add package FullBleed.DotNet --version 0.1.4

The retained Northstar invoice now uses its intended regular brand face. Its PDF is 40,449 bytes, compared with 34,542 bytes for the older, incorrectly italic output. Extracted text is unchanged; the corrected PDF and page pixels match an explicit regular-face control. That control and the other four retained fixtures remain byte-identical across versions. Review appearance and line breaks when upgrading existing templates.

Twenty-two regular/italic family cases cover both registration orders, explicit faces, CSS mappings, ordinary rendering, fixed records, and reflow records. Independent readers check embedded font names and programs, extracted text, and page pixels. The same checker rejects the previous public 0.1.3 package for selecting an italic face for normal text.

The release passes twelve isolated consumers: .NET 8, 9, and 10 on Windows x64, Linux x64, Intel macOS, and Apple Silicon macOS. All six document fixtures and all twenty-two family cases agree across those consumers. Three fresh Windows consumers also verify the signed public NuGet download against the release artifacts.

The verification ZIP contains licensed font inputs, before/after outputs, independent reader reports, checker source, and CI/publication evidence. These checks cover the supplied fixtures; they do not establish universal parity, 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 checks

Successful release workflow.