Cursively VS PdfSharpCore

I was looking at the CSV parser Cursively recently, and I think it is a good simple example of a high performance C# parser and API design.

https://github.com/airbreather/Cursively

Agreed, and agreed. #21 and #22 seek to address this, but these have actually been very low priority for me: as your benchmarks show, if you primarily need a bunch of objects that must be UTF-16 strings, then are other libraries out there that will do the job just fine. The main reason to use Cursively for that would be if you have some use cases where you need the unusual qualities that Cursively offers, but other use cases where you can live with something more traditional, and you don't want to have two different CSV processing libraries.

The usage instructions are in the README on https://github.com/airbreather/Cursively. The most straightforward way to get started (for now) is:

PdfSharpCore https://github.com/ststeiger/PdfSharpCore, a .NET Core port of PdfSharp, might come to the rescue as it has largely removed GDI+.

a) create PDF with https://github.com/ststeiger/PdfSharpCore and then display by using https://www.nuget.org/packages/PdfiumViewer.Updated/ - tested and works in .net 6 desktop app

PdfSharpCore has a compression feature and it's MIT licenced. https://github.com/ststeiger/PdfSharpCore

In one of my pet projects I use PdfSharpCore https://github.com/ststeiger/PdfSharpCore + HtmlRendererCore.PdfSharpCore https://www.nuget.org/packages/HtmlRendererCore.PdfSharpCore. The way it works is something like this:

GitHub - ststeiger/PdfSharpCore: Port of the PdfSharp library to .NET Core - largely removed GDI+ (only missing GetFontData - which can be replaced with freetype2)