.NET

Last week, we created a poll on Twitter , asking you which platform you prefer: The Java platform, The .NET platform, or Another platform These were the results: It seems that the Java platform is the most popular among developers who follow us on Twitter: half of them prefer the Java platform. Looking at the questions posted on StackOverflow, I would have guessed that the numbers would be more in balance, because it feels as if there are about as many questions about iText for Java as there are as about iText for C#. Maybe we...
For many years, our iText PDF software libraries have been available both in Java and .NET and iText 7 is no exception. As such, we are proud to fully roll out iText 7 and three of its add-ons° for .NET, with our Java version already out and enriched with loads of documentation . You can browse through more than 300 items of Q&A items and code examples to help you on your way with iText 7. We will work hard in the coming months to also assist .NET developers with examples, how-tos...
In this chapter, we're going to take a closer look at two sub-standards of ISO 32000. We're going to create PDF/UA files that are compliant with ISO 14289 (Universal Accessibility). We're also going to create PDF/A files that comply with ISO 19005 (archiving, or long-term preservation).
In this chapter, we'll scale, tile, and N-up one file with a different file as result. We'll also assemble files in many different ways. We'll discover that there are quite some pitfalls when merging interactive forms.
In this chapter, we'll add an annotation, some text, and an extra field to an existing form. We'll also change some properties while filling out the form. We'll then move on to PDFs without any interactivity. First, we'll add a header, a footer, and a watermark. Then, we'll play with the size and the orientation of the pages of an existing document.
In the previous chapters, we’ve created PDF documents by adding content to a page. It didn’t matter if we were adding high-level objects (e.g. a 'Paragraph') or low-level instructions (e.g. 'LineTo()', 'MoveTo()', 'Stroke'), iText converted everything to PDF syntax that was written to one or more content streams. In this chapter, we’ll add content of a different nature. We’ll add interactive features, known as annotations. Annotations aren’t part of the content stream. They are usually added on top of the existing content. There are many different types of annotations, many of which allow...
Tags: .NET
When we talk about low-level content in iText documentation, we always refer to PDF syntax that is written to a PDF content stream. PDF defines a series of operators such as m for which we created the MoveTo() method in iText, l for which we created the LineTo() method, and S for which we created the Stroke() method. By combining these operands in a PDF (or by combining these methods in iText) you can draw paths and shapes. Let’s take a look at a small example: -406 20 m 406 20 l S This is PDF syntax...
When I created iText back in the year 2000, I tried to solve two very specific problems. In the nineties, most PDF documents were created manually on the Desktop using tools like Adobe Illustrator or Acrobat Distiller. I needed to serve PDFs automatically in unattended mode, either in a batch process, or (preferably) on the fly, served to the browser by a web application. These PDF documents couldn’t be produced manually due to the volume (the high number of pages and files) and because the content wasn’t available in advance (it needed to be calculated, based on user input and/or real-time...
Tags: .NETiTextSharpUWP
At the technical support team, we have recently received a number of questions regarding support for the Universal Windows Platform . For those not in the know, UWP was designed by Microsoft to improve portability of applications between all possible Windows-style devices. In the older .NET Framework, porting an existing app to a new device family (e.g. wearables, XBox, etc.) is a non-trivial task. UWP aims to solve this problem by introducing a unified backbone that is compatible with all device families, and ensures that an app can be used on all devices that run on a...