PdfPig
library
DISCONTINUED
Our great sponsors
PdfPig | library | |
---|---|---|
7 | 10 | |
1,430 | 1 | |
4.7% | - | |
9.0 | 3.1 | |
6 days ago | about 3 years ago | |
C# | C# | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
PdfPig
-
Just Say No
Maybe (most likely) this is a problem of GitHub's terminology. For genuine bugs, e.g. here's the repro, the stack trace, the code to replicate it, it happens 100% of the time if you follow these steps, I'd agree that just having it open and in the backlog would be preferable.
The problem is those make up maybe at a generous estimate, 10-15% of issues in a projects backlog. In the interests of full disclosure here's mine (I don't use stalebot) https://github.com/UglyToad/PdfPig/issues?page=1&q=is%3Aissu.... As you can see from the backlog I close almost nothing. This was a deliberate choice to avoid closing things until the fix was confirmed by the reporter.
But equally that's the first time I've opened the repository in a couple of months and the amount of angst and dread I feel just from the size of that list means I'll probably find yet another excuse not to do anything on it this coming month.
Discussions on this topic feel a lot like "technical solutions to social problems"; by which I mean "well in the ideal world a perfectly logical person would do x, y, z so the system should reflect that". And while a stalebot is the archetypal technical solution to a social problem it at least works with how maintainers work. Sometimes in life you want to ignore a problem and have it go away. When you can't do that, e.g. government bureaucracy, work stuff, social obligations, that's where stress comes from. And asking volunteer maintainers to add a whole new source of stress in their life falls apart when people get busy, or their life circumstances change, or they get ill or tired or whatever.
Yes, in a perfect world the issue backlog would be sacrosanct and perfectly groomed/prioritized. But we're just fleshy sacks of chemicals and we're not perfect. Unrealistic expectations from users are the cause of maintainer burnout.
Because GitHub closed issues are still viewable and searchable (I'd guess most people search it through a search engine not the terrible inbuilt search) I'd disagree that they're deceiving users somehow.
-
There is framework for everything.
What about PdfPig? It's under Apache 2.0.
-
How to read pdf files in C#?
PDF Pig is open source and allows you to read text and even extract images.
-
Add, Remove, Extract and Replace Images in PDF using C#
https://uglytoad.github.io/PdfPig/ https://github.com/empira/PDFsharp
-
Are there any good PDF generation libraries with no paid licensing?
Example of document creation API here https://github.com/UglyToad/PdfPig#document-creation-005 and wiki with more details here https://github.com/UglyToad/PdfPig/wiki/Document-Creation
library
-
QuestPDF 2022.01 - a new version of the open-source, C# library for generating complex PDF documents with fluent API, now with complex table-layout support ๐ Please help me make it popular ๐
Give the official QuestPDF repository a star โญ so more people will know about it. Most developers evaluate project maturity based on the star count so let's help them make the right decision!
-
QuestPDF 2021.11 - a new version of the open-source, MIT-licensed, C# library for generating PDF documents with fluent API, now with several community-driven improvements ๐ Please help me make it popular ๐
There are already a couple of free or paid libraries in the .NET ecosystem that can be used to generate PDF files. The way how QuestPDF differs is simple: instead of relying on an HTML-to-PDF conversion, it implements its own layouting engine that renders the full content using the SkiaSharp library (a Skia port for .NET, used in Chrome, Android, MAUI, etc.).
-
QuestPDF 2021.10 - a new version of the open-source, MIT-licensed, C# library for generating PDF documents with fluent API, now with extended text capabilities. Please help me make it popular :)
Hi, can you please elaborate more about your question? Or create a discussion on the repository page? https://github.com/QuestPDF/library/discussions I am not sure exactly what requirement you would like to achieve :)
Two months ago, I have shared with you my open-source library designed for generating PDF documents in .NET applications. The way how QuestPDF differs from other libraries is simple: instead of relying on an HTML-to-PDF conversion, it implements its own layouting engine that renders the full content using the SkiaSharp library (a Skia port for .NET, used in Chrome, Android, Xamarin, etc.). I have written this layouting engine with full paging support in mind. That means the document content is aware of page size, can be moved to the next page (if there is not enough space) or even be split between pages (e.g. table rows) - there are many elements to help you implementing the desired paging behaviour. Additionally, you have full access to various simple elements (e.g. border, background, image, text, padding, etc.) that are essential building blocks of complex layouts. This way, you have a set of easy to learn and understand tools that are highly composable and predictable which reduces the time of development.
- Best way to deal with PDF file generation
-
Generate a PDF with dynamic header and footer
QuestPDF is my go-to.
-
QuestPDF - my open-source C# library for creating PDF documents with Fluent API needs your help
Give the official QuestPDF repository a star โญ so more people will know about it,
Hi :) That is a good point about most of the APIs available. I truly believe that it does not apply to the QuestPDF library. The Fluent API here is used only to describe the document's content, to create new element instances and assign them to parents. In other words, there is no business logic involved in this code area. Please analyze the QuestPDF.Fluent namespace. You will find that most of the API invocations are super simple and straightforward.
- Best way to generate a pdf file using dotnet 5?
-
Server side pdf and charts... sad state
check out https://github.com/questpdf/library
What are some alternatives?
ITextSharp - [DEPRECATED] .NET port of the iText library, only security fixes will be added โ please use iTextย for .NET
PDFsharp - PDFsharp and MigraDoc Foundation for .NET 6 and .NET Framework
Docotic.Pdf - Docotic.Pdf library can create, edit, draw and print PDF files in .NET Core, ASP.NET, Windows Forms, WPF, Xamarin, Blazor, Unity, and HoloLense applications. The library is a 100% managed assembly without unsafe blocks. The assembly has no external dependencies.
iTextSharp (LGPL / MPL) 4.1.6 for .NET Core - Unofficial .NET Core port of iTextSharp 4.1.6. Last version to be released under the Mozilla Public License and the LGPL.
docnet - DocNET is as fast PDF editing and reading library for modern .NET applications
Pdfium.Net SDK