We try our best to provide minimal yet appropriate solutions to our customers. Hence, in this month’s release of GroupDocs.Annotation for .NET 19.3 you will observe some new “easy-to-implement” features. Lets start with ellipse annotation. You might be looking for it, we’ve now added its support for different document formats.
Ellipse Annotation
GroupDocs.Annotation for .NET 19.3 provides GetThumbnail method for PageImage class, that helps you in getting thumbnails of PDF document pages.
Get Thumbnails
You’ll be glad to hear that multipage TIFF file can be processed by API. Have a glance at release notes.
Bug Fixes
Now coming to your issues, we’ll discuss some major fixes introduced in this release. There was issue in applying PenWidht and PenColor properties but now this is fixed.
AnnotationImageHandler.GetDocumentInfo exception while evaluating API in trial mode is now resolved. API now closes stream when you import annotations for Images. Lastly, issue in setting comments to shapes in Slides is fixed.
Learn more about API integration and usage check out the docs here.
GroupDocs.Comparison for Java 19.3 rolls out with major bug fixes. When password protected files were compared, result was null. This might be a showstopper for you but not anymore.
Moving ahead, comparing a PDF with itself was not working, result was null. We fixed this issue.
Most importantly, MultiCompare was also returning null. Code below explains how it works.
You can compare a source file with multiple target files. Sounds appealing, isn’t it? Don’t wait, download the latest release and implement this feature.
With our latest release 19.3, some new properties are introduced in ImageSaveOptions class. When converting to a Image format you can now always set brightness and contrast. API permits you to do mirror-reversal across a horizontal/vertical axis using FlipMode property.
Based on your feedback, we resolved some previously logged issues and improved document conversion experience. Such as, image quality is improved when converting to a WebP format. Furthermore, JpegQuality issue is now resolved for PDF to JPEG conversion.
New Properties in ImageSaveOptions
FlipMode offers horizontal, vertical, horizontal and vertical at the same time or no Flip at all. Control gamma correction, brightness and contrast when converting to a image format.
Fix – ImageSaveOptions.JpegQuality Issue
You can select desired image quality when converting to JPEG format. Quality scale must be between 0 and 100. Previously, despite of setting JpegQuality to any value (0-100), API was not reflecting any change in the output. This issue is now fixed.
GroupDocs.Conversion for .NET 19.3 is now available to download. Let us know what you think by sending feedback!
PDF is a widely used document format that also supports interactive elements including annotations, forms, 3D objects, layers, etc. Along with these elements, PDF format also supports setting restrictions such as print restriction, modification restriction, restrictions on data extraction and so on. Such features give the user more control over the document and therefore, the PDF has become a popular document format.
Since we support the rendering of PDF documents, therefore, we always keep looking to introduce features that may give you more information about the documents. Hence, we provided the detection of print restriction in the PDF documents in GroupDocs.Viewer for Java 19.3.
Well, we have made it quite easy for you to detect print restrictions in a PDF document. The following code snippet shows how to get this information using getDocumentInfo() method:
Not only this, but we have also extended the list of our supported document formats with the addition of the following formats in v19.3:
TSV (Tab-separated values)
PCL (Printer command language)
Well, these could be the interesting additions in the API for you. If yes, let’s not wait and download the latest version of GroupDocs.Viewer for Java. To evaluate the API features, you may clone and explore the examples project from GitHub repository. In case you want to share your reviews, concerns or feedback, we welcome you on our forum.
We are happy to announce the release of version 19.3 of GroupDocs.Viewer for .NET. In this release, we have added several new features that target the PDF documents, archives and the source code files of Visual Basic and C#. Along with 2 bug fixes, we have made a couple of improvements for rendering of ZIP archives and vCard documents. For detailed information about the latest release, please have a look at the release notes.
What’s New in this Release?
Setting Passwords and Permissions for PDF Documents
PDF format allows setting the Owner password and the User password to restrict access to the document. The Owner password is used to change the permissions of the document whereas the User password is required when opening a PDF document. Along with the passwords, PDF format supports setting permissions such as allow or deny printing, modification and data extraction. In this release, we have added the support of setting the Owner password, User password, and the file permissions while rendering the document into PDF.
The following is a simple way to create and use the PDF file’s security options using GroupDocs.Viewer for .NET:
Working with Folders within the Archives
In the previous version, we introduced the support of rendering archive documents. The rendering of archive documents shows a list of the items (files and folders) located in the root of the archive. In the latest release, we have made it possible to get the list of the folders within the archive and render the content from those folders. The following sections demonstrate how to work with the folders located in an archive document.
Getting List of Folders within an Archive
The following code snippet shows how to get the list of folders within an archive:
Getting List of Folders in a Specific Folder
There might be the case when you have sub-folders within a folder located in the root of the archive. In that case, to get the list of sub-folders you can simply specify the folder name in ArchiveOptions.FolderName property of HtmlOptions/ImageOptions class.
Rendering Specified Folder within Archive
To render the content of a folder, simply specify the folder name in ArchiveOptions.FolderName property and call GetPages function as shown in the following code snippet.
Support of Visual Basic (.vb) and C# (.cs) Files
Using the latest release, you will be able to view the source code files of Visual Basic and C#. The rendering of these source code files is available in both, the HTML-based and image-based rendering.
Haven’t Used GroupDocs.Viewer Before?
In case you haven’t yet tried our API but are interested in using it, the following resources will be helpful for you to get started.
A configuration file defines the initial or commonly used parameters, options, settings or preferences applied to operating systems, infrastructure devices or applications in an IT context.
When the Need Arises
If you have large size data (may consist of multiple files of different file formats) or corporate sensitive data which need to be redacted without specifying the rules in your code.
What is the Solution
The GroupDocs.Redaction API provides the way to define a removal policy by writing the list of pre-configured redaction rules in an XML file. Hence, you do not need to specify the rules in your code. You can have as many policies, as you need to redact your documents.
The example of redaction policy XML file is as follows:
How to Apply Redaction Policy
The example below shows:
how to apply the redaction policy to all files by giving inbound folder
Save the output files to one of outbound folders
The successfully updated files and failed one will save to their respected folders
The current date and time is used as a part of output file name
The successfully updated files and failed one will save to their respected folders
The complete ready to run code sample is available on GitHub.
Yes, you heard it right. We’ve implemented ability to save document comparison results in image format as well. In this blog post we’ll review the new feature and bug fixes introduced in monthly release of GroupDocs.Comparison for .NET 19.3.1.
Let’s talk about image representation of the document pages. The moment you save comparison results in your directory, you have a control to save results in image format as well using ICompareResult.SaveImages Method. Quite simple, isn’t it?
The good thing is that you just have to pass the output folder path and API will take care of conversion mechanism itself.
Is there a way to get number of converted images? Can images be saved in separate directory?
The answer is yes, you can retrieve a list of converted pages and also save them in some separate directory. Let’s see full implementation of this feature.
Bug Fixes
In addition to the new features, we also emphasis to improve/resolve consistency, usability and issues. We will highlight the major bug fixes below.
SuperScript and SubScript
You may be familiar with these characters. They are slightly below or above the normal line and are usually smaller than the rest of the text.
There was issue in SuperScript and SubScript elements in Word document. API was not processing such characters. But this issue is now resolved.
StyleSettings is not working for HTML
Let us first give you an overview of StyleSettings. Using this you can set following properties:
BeginSeparatorString
Bold
EndSeparatorString
Fontcolor
HighlightColor
Italic
StrikeThrough
Underline
Previously, there was no impact of such properties in the output HTML. Can we now strikeout or change color of deleted component? Of course, we are pleased to inform you that you can now successfully set such properties during HTML comparison and see their impact in the resultant file.
EndNote Comparison
When we want to add reference information about a quoted material, we use Endnote.
Previously, API was not considering Endnotes and there was no Endnote comparison at all. However, its fixed now. In the image below, we have source, target and resultant files. And if you see resultant file, it clearly shows a Endnote comparison.
Further Reading
Get started with GroupDocs.Comparison for .NET Developer Guide.
Go through the release notes in order to get more insights. Articulate your concerns or feedback on Forum.
We’d now recommend you to integrate latest release of the API in your project and enhance your document comparison experience.
In the latest version of GroupDocs.Assembly for Java we have introduced an exciting feature of Inline Syntax Error Messages. Are you thinking about what does make this feature so exciting? Well, I am going to answer it in this post.
First, let’s have a brief overview of how does GroupDocs.Assembly generate the reports. GroupDocs.Assembly uses pre-defined document templates that contain the LINQ statements. These templates are evaluated, processed and then populated by API’s engine during the run-time. An exception is thrown in case something is wrong with the syntax of the LINQ statements. The exception contains the reason and the tag/expression where the error has happened.
This is not a big deal to find and locate the incorrect syntax in a small template with a few LINQ statements. But, how would you find the exact place of error when you are dealing with a complex template containing a number of tags and expressions?
Here comes the usefulness of Inline Syntax Error Messages. With this feature, the API embeds the error message within the generated report at the same place where the error has occurred, as shown in the following screenshot:
Now you may wonder how to achieve this. Well, it’s just as easy as a pie and you only need to set the options using DocumentAssembler.setOptions( DocumentAssemblyOptions.InlineErrorMessages) as shown in the following code snippet:.
For working examples, you may consult our documentation article on how to use inline error messages.
Alright! Now you would have got the real picture of how this new feature may help you in your report generation process. So, let’s try out the API features by downloading the latest version as well as cloning and exploring the examples project from GitHub repository.
Do you have any questions or queries? We welcome you to have a conversation with us on our forum.
GroupDocs.Merger now supports diagram formats such as VSDFX, VSDM, VSSX, VSSM and VTX . It allows you to swap, rotate or trim pages in diagrams. Apart for that, you can also set or remove password protection of diagrams. This API comes in both Java and .NET platforms and could be integrated in any your .NET or Java application without any dependency.
Features for Diagrams Format
Swap Pages:
This feature allows you to exchange the position of two pages in the document. Following are the lines of code which can be used to swap pages in the diagram:
Above lines of code are used to swap pages of following VSDX file:
Finally, after performing swap operation on VSDX, the output looks as follows:
Move Page:
This feature allows you to change position of the pages within the document. Following are the lines of code which can be used to change order of the pages in the diagram:
Remove Page:
Using this feature you can remove single or collection of pages from the document. Following example demonstrates how to remove pages in the diagram:
Split Document:
You can split document into several resulting documents using this feature. Following is the example to split diagram:
Trim Document:
This feature allows you to cut the specific pages of the document. Following are the lines of code which can be used to trim the diagram:
Change Pages Orientation:
This feature allows you to change pages orientation. Following code sample shows how to change orientation of the pages in the diagram:
The Compressed files (e.g .ZIP or TAR) use file compression in order to save the disk space. Also, the compressed archive formats can be used to compress multiple files into a single archive. This post demonstrates the usage of the GroupDocs.Viewer API to render the list of files or folders from an archive file.
Rendering the List of a Folder from the Archive
The GetPages method of both ViewerImageHandler and ViewerHtmlHandler renders the items from the root of archives.
The following code snippet shows that how simple is to render the list of items from the root of an archive:
The output of the above code snippet looks as follows:
Rendering Specified Folder into Image, HTML or PDF
To render a specified folder from an archive into image, html or PDF, all ImageOptions, HtmlOptions and PdfOptions classes have the ArchiveOptions.FolderName property which is used like:
ArchiveOptions.FolderName = "FirstLevelFolder";
When you need to render the list of items or folders contained in a certain folder inside the archive, set the value using ‘/’ path delimiter character like:
The following example shows the rendering of a list of items from a folder “SecondLevelFolder” which is contained inside the “FirstLevelFolder” of the archive:
If the rendering into PDF file is required, you can write the code as follows:
The complete ready to run code sample is available on GitHub.
