Restart the List Numbering Dynamically within Your Document
Nested or the multi-level numbered lists allow you to group the items based on the parent item. Put it simply, you can separately list the items under each group. This becomes very useful when you have to list the items having multiple sub-items. Let’s have a look at the following figure which makes it simpler to understand the scenario.
In this figure, you can observe that there are listed 3 groups and each group further has multiple items listed under it.
Control Documents Comparison Sensitivity
Integrate GroupDocs.Comparison for .NET 19.6 in your project and take control of documents comparison sensitivity. Detecting source and target documents style changes or inserted/deleted items and then highlighting them in the resultant file is a common yet major feature.
But we have something new, something enormous for you. You can now get detailed comparison of the documents. In ComparisonSettings class we added SensitivityOfComparison method using that you can set sensitivity of documents comparison.
Get Image Representation of Document Pages
Getting image representation of document pages is one of the most successful feature that is already implemented in .NET version of the API. Keeping your interest in view, we’ve now implemented this feature for Java developers. GroupDocs.Comparison for Java 19.6 allows you to save document comparison results in image format as well.
What does it take to implement such a feature?
You just have to pass the output folder path to convertToImages method and API will take care of conversion mechanism itself.
Retrieve Count of Credits Consumed In GroupDocs.Conversion for .NET
As you know that API already supports metered licensing.
Can we get count of credits consumed?
Yes, we have a good news for you. There is a new method GetConsumptionCredit() implemented in Metered class. This method returns count of credits that are consumed in case of Metered licensing is used.
Following example demonstrates how to retrieve count of credits consumed.
Let’s talk about the new file formats introduced. Most of you might be working with XLAM, an Excel Macro-Enabled Add-In file format.
Issue with Footnote Number is Resolved
If you worked with earlier versions of the API, you are probably aware that there was issue in footnote number conversion. A Word document with such footnotes was converted to PDF or any other supported file format successfully but the footnote number order was disturbed.
There was one more issue reported in the forum. It was about converting a PowerPoint document with black SmartArt text to PDF. And the SmartArt text in the resultant document was changed to white text.
Embed Custom Objects in Metadata Signature for Images
Yes, GroupDocs.Signature for .NET now supports embedding custom objects as metadata signature in the images. So you can now sign the images with your desired metadata properties. We have introduced this feature in version 19.6 by adding a new public method AddSignature to the ImageMetadataSignOptions class. Not only this, but you can also apply the data encryption to the custom objects. So let’s check out how easy it is to sign an image with custom metadata signature.
Get Image Representation of a Document
Did you ever wish to get image representation of a document? GroupDocs.Merger for Java 19.6 will make your wish come true. This feature is also helpful for front end application development.
Let’s have a look at its implementation.
It will return page number and page stream. Using getPagePreview method you will get list of page image representations for a document of known format. So, source document file format should be specified.
Export Annotations to TIFF Files
This may be a big news for those who annotate TIFF documents, most of the time. Previously, there was issue with this format. API was throwing exception “Cannot open image file”. But now you can:
Import annotations from TIFF file Delete annotations from it Export annotations into it Moreover, in trial mode you were not able to get document info. This issue is now resolved in GroupDocs.Annotation for .NET 19.6.
Extract Data Fields from the Documents using GroupDocs.Parser Product Family
Hello everyone! I am back with something new and exciting for the developers who use to deal with the automated data extraction from the documents. A few years back, we released GroupDocs.Parser API which aimed to extract the text from various document formats. We kept on adding the features to it and today, it has become a giant API that provides a wide range of features including formatted text extraction, highlighted and structured text extraction, metadata extraction, extraction of images and the list goes on.
Big News! GroupDocs.Redaction has been released for Java platform!
Do you have to deal with a frequent exchange of the digital documents? Do your documents contain classified and sensitive information that needs to be protected? If they do, how do you process such documents to hide or remove some specific information before sending them outside your company? Well, these questions will definitely pop out the solution that you are currently using for protecting the sensitive content in your document.