Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr...
by numo16 on Tuesday October 15, 2019 @04:11PM
(#21263160)
For html/dom parsing, I would recommend looking at either AngleSharp[0] or HtmlAgilityPack[1], as they tend to be the most popular in the community.
[0]: https://github.com/AngleSharp/AngleSharp [1]: https://html-agility-pack.net/
Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr...
by UglyToad on Tuesday October 15, 2019 @08:02AM
(#21257578)
Thank you for the response.
Yeah HTML to PDF is a tricky one, presumably wkhtmltopdf/pechkin doesn't work out because of licensing / interop issues? Other than that the only other one I'm aware of is Aspose which is expensive as you say.
Images (along with font subsetting and fixing the gzip implementation) are the next thing I plan to implement so it's helpful to know its a real requirement.
Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr...
by merb on Tuesday October 15, 2019 @08:08AM
(#21257601)
actually wkhtmltopdf/pechkin both won't support pdf/a-3 and have a not so nice output.
aspose is actually really cheap, compared to others, unfortunatly their support is trash: https://forum.aspose.com/t/html-to-pdf-pdf-net-fonts-error-o... i.e. pdf/a-3 does not work on mac (didn't tried linux, but I guess it has similar problems)
btw. itext is a really great library, unfortunatly itext has a problematic licensing and I tought they were jocking after they gave me prices.
basically we don't need a lot, mostly switch fonts/text sizes/images (generated barcodes, logos) and of course pdf/a-3(a/b/u) for invoice. so apis that translate the html into the layouting of pdf is the bigger problem.