Whether you want to optimize, normalize, render, print, output spreadsheets, or convert PDF files to PDF/A, with DynaPDF all this is a snap.
If you develop your applications for more than just one operating system, then the PDF Library has to support the required operating systems too.
Who wants to develop the PDF output for every platform again? Exactly, no one...
DynaPDF is one of the few libraries that supports color management from the creation till to the view, including soft proof!
With the right tool, color management is quite simple...
The focus of development in DynaPDF 4.0 was the development of a new PDF/A 2b and PDF/A 3b converter. The new converter should be able to completely rebuild PDF files.
This requirement has lead to the development of a new content parser that is able to completely regenerate and optimize content streams. This makes it possible to apply much more extensive repairs. Since all content streams will be rebuild, also references of the .notdef character can be removed (in PDF/A 1 it was allowed to reference the .notdef character directly but this is no longer allowed in PDF/A 2 and 3).
This increases the conversion rate drastically and completely error free and optimized PDF files will be created which render and print faster. This is not only interesting for PDF/A conversion, PDF files can also be normalized or just optimized.
Not anything that is possible with the new content parser is already available in corresponding functions. For example, the parser is also the new base for the rendering engine. Since it can read and write page contents, the development of a PDF editor is no problem anymore. Especially images and vector graphics can be edited in addition to text, which was not possible before. In the coming months the new parser will replace the old code more and more.
Examples explain more than thousand words. The entrance should be as simple as possible, so more than 25 new samples have been added. The examples are small and easy to understand.
The C#, Visual Basic 6, Visual Basic .Net, and Delphi interfaces have been reworked and extended. There was not much to do for the Delphi interface; it only lacked a few overloaded string functions. For the other interfaces this was a bit different: Although the C #, VB 6 and VB .Net interfaces contained the complete ANSI and Unicode API, no standard functions without suffix were available. Therefore, for many programmers it was often not clear which function should be actually used. Unicode is the default, so Unicode versions without a suffix have been added in all interfaces.