PDF is by far the most important export format and one of the targets virtually every user is actually working with. Over the years, we've employed a number of different SDKs and versions of these SDKs in order to write decent PDF files. While the results were excellent already for "normal" cases, there were a couple of restrictions in more advanced scenarios. This has changed in version 26.
List & Label has supported a number of text based export formats for quite a while. You can have XML, CSV and layout TXT export in different variants. That way, you can use List & Label as a convenient way to convert your data from one of the supported data sources to something you can use in other applications again. But one very popular format was missing so far that's been around for quite a while: Java Script Object Notation aka JSON.
This is another of those "huh, you didn't have that before" features. As a WYSIWYG layout oriented reporting tool, the page has always been king for List & Label. While this is nice in many circumstances, when it comes to reporting for the web or XLS and printing is not planned at all, the result can be unwanted although looking beautiful.
With List & Label you can export reports in different formats like PDF, Word, Excel and many more. The resulting reports can either be stored directly in the file system or – in .NET – in a stream, in order to transfer them manually into a database, a document management system or similar. Reports can also be automatically stored directly in so-called cloud storage services. The cloud storage providers for GoogleDrive, Microsoft OneDrive or Dropbox are available in List & Label for .NET for this purpose.
While I've been blogging about the major and most-UI-visible features during the last few months, of course there are gazillions of minor and less visible changes underneath the hood in LL24. This blog post sums up some more reasons to be cheerful.
So far, it hasn't been possible to export to all of our export formats from the preview window. The simple reason is that we're using the EMF file format internally while the exporters need completely different information that cannot be extracted from the EMF. Thus, we were only able to support image file formats and – of course – PDF, which is created from EMF vector information.
The Scalable Vector Graphics format has been around for quite a while. The first specification was released in 2001, and meanwhile all browsers offer solid support for SVG. During the years, we've received a couple of requests to support SVG in List & Label. Initially, I was hoping for Microsoft to make SVG rendering support a Windows feature that we could just use. However, that hasn't happened so far. And so we had to come up with a different solution.