Big News! We are going to launch GroupDocs.Redaction API for Java platform very soon. Similar to the .NET version, GroupDocs.Redaction for Java would be a backend API for removing sensitive and classified information from the popular document formats. As far as the supported features are concerned, this is going to be a replica of GroupDocs.Redaction for .NET. Through this API, we aim to provide you a single, format-independent interface containing a set of redaction methods to redact text, metadata, and annotations.
Let’s have a look at the salient features that you are going to get in the first version of GroupDocs.Redaction for Java.
Exact Phrase Text Redaction
Case-Sensitive Exact Phrase Text Redaction
Text Redaction with Colored Rectangle
Text Redaction using Regular Expression
Support of region redactions for image files
Metadata Redaction
Searching and Filtering Metadata for Redaction
Annotation Redaction
Removal of Sensitive Information from Annotation
Document Format Detection
Detailed Redaction Logging
Saving File in Original Format
Saving File as a Rasterized PDF
Ability to specify a set of redaction rules (policy) in an XML file
You are going to get the above-mentioned features for the following document formats:
PDF (.pdf)
MS Word (.doc, .docx, .dot, .odt, .dotx, .docm, .dotm, .rtf)
MS Excel (.xls, .xlsx, .xlt, .xltx, .xlsm, .xltm, .csv)
MS PowerPoint (.ppt, .pptx, .pps, .ppsx, .potx, .pptm, .ppsm, .potm)
Now, you might be interested in when you would get the first version of GroupDocs.Redaction for Java. Well, we won’t let you wait for enough because:
“Sometimes waiting is the hardest thing.”
Dean Koontz
At the moment, we are finalizing the first release of GroupDocs.Redaction for Java and hoping that you will be able to grab it very soon. Please stay tuned to our blog for more news and updates.
Guys, are you ready? Before we dive into its details: I want you to get an essence of the public release. I am giving you little preview of the new features and other enhancements available in the release for quick reference. I guess you know the valuable usage of MS Excel’s auto-fit rows/cols feature. Yet, you are one step ahead and perform the operation on merged cells by Aspose.Cells. While working in MS Excel IDE, you might not dislike formatted Tables but sometimes you need to convert to raw range. Here comes the library to accomplish these tasks via the APIs. Some of you might also like importing from JSON. So let’s not wait another moment to review the release notes. Do you want to know all exciting features and other enhancements? Here you go.
Autofit Rows for Merged Cells
Autofitting rows is a very common operation which you perform while working with the Excel files. This feature was already there in Aspose.Cells API however many people asked for more control over this operation. To fulfill this requirement we have provided AutoFitMergedCellsType enumerator which contains the following options:
None: Ignore merged cells.
FirstLine: Only expands the height of the first row.
LastLine: Only expands the height of the last row.
EachLine: Expands the height of each row.
Here is a snapshot of this feature where the effect of one of the options EechLine is shown.
You can test this feature using following sample code.
Conversion of the table to a range was available earlier. However what if you want to control the formatting of destination range like formatting only the partial output. The good news is that this feature is available now and you don’t need to write extra code to format the output range. We have introduced a new class TableToRangeOptions where LastRow property is available to set the last row to which formatting is copied from the source table. Here is the view of a sample table and converted range which is formatted up to row 5.
Here is a sample code which is used to create the above range.
For detailed information on conversions follow this link.
Import data from JSON
As you know that JavaScript Object Notation is a common data interchange format which is quite lightweight and can be read by human and machines easily. Now, for example, you get data from some Web API in JSON format and need it to be imported into some Excel file, then Aspose.Cells is there to provide this facility.
JSONUtility class is introduced by Aspose.Cells for this purpose having ImportData method that not only imports data but also performs different conversions and formatting using the JsonLayoutOptions object during the import process. You may try this exciting feature by following article Importing Data from JSON. Here is a sample code to use this feature:
You can see that result is cool as fully formatted Excel file is created without using any extra code to parse the JSON string from any source like Web API. Isn’t it? For example, if you get the following string from Web API, then output Excel file is shown in the image below:
Microsoft Excel supports external links for fetching data from different sources. We have provided the option to retrieve these links from the Excel file using Name.GetRefferedAreas method. This method returns ReferredArea which has many useful properties as follows:
EndColumn: The end column of the area
EndRow: The end row of the area
ExternalFileName: Get the external file name if this is an external reference
IsArea: Indicates whether this is an area
IsExternalLink: Indicates whether this is an external link
SheetName: Indicates which sheet this reference is in
StartColumn: The start column of the area
StartRow: The start row of the area
You may find details on how to get range with external links for your reference. In the following example, an external file having named range “Names” is linked with the Excel file. We can access this named range in the linked file and display its properties mentioned above.
Keep separators for blank rows during spreadsheet to CSV
Many times you convert the Excel sheets to CSV for using it in some other environment or applications. You may need to decide yourself about the separators for blank rows in the spreadsheet while exporting it to CSV. For example, there is a blank row in the source spreadsheet and you want either a blank row in the CSV or have a row with predefined separators. We have provided this feature now and you can get details about this feature here.
For better understanding, have a look at the following image which shows the result of this feature.
Following is a sample code which demonstrates this new feature.
To use these useful features and avail other enhancements, I recommend you to try the release Aspose.Cells for .NET v19.3. And, if you have more time, browse Developers’ Guide for your complete reference on what you can deliver using the rendering extension API. You are always welcome to share your review, concerns or feedback on forums.
Big smiles as I am here to announce the release of the latest version of Aspose.Cells for Java. In this post, I am going to give you a glimpse of all the new exciting features for best utilization of the API along with the improvements and fixes. Links to the relevant articles and resources will also be available for quick reference. So let us start reviewing what is there in this release.
Import data from JSON
As you know that JavaScript Object Notation is a common data interchange format which is quite lightweight and can be read by human and machines easily. Now, for example, you get data from some Web API in JSON format and need it to be imported into some Excel file, then Aspose.Cells is there to provide this facility.
JSONUtility class is introduced by Aspose.Cells for this purpose having ImportData method that not only imports data but also performs different conversions and formatting using the JsonLayoutOptions object during the import process. You may try this exciting feature by following article Importing Data from JSON. Here is a sample code to use this feature:
You can see that result is cool as fully formatted Excel file is created without using any extra code to parse the JSON string from any source like Web API. Isn’t it? For example, if you get the following string from Web API, then output Excel file is shown in the image below:
Conversion of the table to a range was available earlier. However what if you want to control the formatting of destination range like formatting only the partial output. The good news is that this feature is available now and you don’t need to write extra code to format the output range. We have introduced a new class TableToRangeOptions where LastRow property is available to set the last row to which formatting is copied from the source table. Here is the view of a sample table and converted range which is formatted up to row 5.
Here is a sample code which is used to create the above range.
For detailed information on conversions follow this link.
Get Range with External Links
Microsoft Excel supports external links for fetching data from different sources. We have provided the option to retrieve these links from the Excel file using Name.GetRefferedAreas method. This method returns ReferredArea which has many useful properties as follows:
In the following example, an external file having named range “Names” is linked with the Excel file. We can access this named range in the linked file and display its properties mentioned above.
Keep separators for blank rows during spreadsheet to CSV
Many times you convert the Excel sheets to CSV for using it in some other environment or applications. You may need to decide yourself about the separators for blank rows in the spreadsheet while exporting it to CSV. For example, there is a blank row in the source spreadsheet and you want either a blank row in the CSV or have a row with predefined separators. We have provided this feature now and you can get details about this feature here.
For better understanding, have a look at the following image which shows the result of this feature.
Following is a sample code which demonstrates this new feature.
Autofit Rows for Merged Cells
Autofitting rows is a very common operation which you perform while working with the Excel files. This feature was already there in Aspose.Cells API however many people asked for more control over this operation. To fulfill this requirement we have provided AutoFitMergedCellsType enumerator which contains the following options:
Text extraction from cells using Cell.getDisplayStringValue() was returning different results for Ricty Diminished font. The new version returns appropriate string now.
Text alignment in the resultant PDF is made more accurate.
In some cases, the black text color was changed to red in the converted HTML, that is no more an issue.
Scatter chart and 2D bubble chart will be rendered to PDF without any problem.
Range.Copy() will copy the font settings and other objects now onward.
Workbook.hasExernalLinks() will return proper results for DDE links.
Note: You may download this project from GitHub to get the template files and running examples used in this blog post.
Hi guys! Do you want to preserve legacy control characters in Word documents? Many of you must want to work with font fallback for Google Noto fonts? You will love to export the list labels of Word document into TXT file format with specific character and change the text alignment of axis tick labels of chart. So what’s the solution?
So how to work these features? Let’s talk about these one by one.
Preserve Representation of Legacy Control Characters While Exporting Document to OOXML
Some document formats support legacy control characters. MS Word does not save these symbols to DOCX format (more accurately in OOXML formats). However, we added new property KeepLegacyControlChars in OoxmlSaveOptions class to preserve such control characters. So far only one legacy character (ShortDateTime) is supported which declared in the “DOC” format.
Here’s how you can use this property:
Predefined Font Fallback Settings for Google Noto Fonts
You may know about Noto. It is a font family comprising over a hundred individual fonts. We have added predefined font fallback settings for Google Noto fonts. These are free fonts licensed under SIL OFL.
Let me clarify two things here:
The predefined settings uses only Sans style Noto fonts with regular weight.
Aspose.Words does not support advanced typography. So, the Noto fonts that use advanced typography may be rendered inaccurately
Following code example shows how to use predefined font fallback settings.
Don’t stop reading now! There are more Aspose.Words’ features for you. Amazing, isn’t it?
Text Alignment of Axis Tick Labels
By default, MS Word aligns Chart Label to the center. However, you can change it using ChartAxis.TickLabelAlignment property. We have simple example for you here:
Sound good? Yes, it is!
Allow to Specify How List Levels are Indented When Exporting Document to Plain Text Format
Starting from Aspose.Words 19.3, you can get the ListIndentation object and specify how many and which character to use for indentation of list levels. By default, no indentation is exported to text file format.
Here’s how to work with list indentation.
Using Tab Character
Using Space Character
Using Default Indentation
Wait, there’s many other features, enhancement, and bug fixes included in this release. Here you can get the detail!
When time allows you can check out API examples at Github, talk about this release and other API related issues in our forum.
February release of Aspose.PDF for .NET has been rolled out and is thriving with exciting features and enhancements. Our efforts to implement most requested functionalities has brought up the API this far that its feature set has become such enriched and appealing. Being specialized API in order to process PDF documents, Aspose.PDF for .NET 19.2 brings more interesting features in this revision. In this post, we will be going to explore what is new in this release and having insights into further improvements. Without waiting so much, let’s learn what this update of the API offers and how it can be consumed to perform newly introduced functionalities.
Signing a PDF document from a Smart Card
Signing PDF documents with digital signatures is common exercise when you intend to secure them. By doing this you make sure that their content is not changed and they are from trusted source. Certifying PDF documents, on the other hand, is slightly different because it allows you to specify changes which are allowed to document without invalidating its security. This functionality can be achieved using Adobe Reader by following “Adding Signatures and Security” guide.
In above referred guide, you need to perform all steps manually by using Adobe Reader. But, automating this entire process and get this done programmatically sounds more efficient and time saving. Isn’t it? At this point, Aspose.PDF can definitely save you big time from efforts. Those who are already users of the API, may know that it offers functionality to digitally sign PDF documents as well as certify them using PFX file.
Well, extending its feature set in the region of signing and security, Aspose.PDF for .NET now offers the functionality to add digital signatures from a key store location. Which means you will be able to apply the signature by accepting the certificate provided by certificate store, smart card or PIV card connected to the system at run-time. All of the mentioned functionality can be achieved by just using following simple code snippet(s):
Using Signature Field
Using PdfFileSignaure
Major Enhancements for Creating Tagged PDFs
We are not yet done with the updates this release of the API
has brought. There have been many requests for the feature to create Tagged
PDFs (PDF/UA) which is finally offered by the API. With every release of the
API, this feature is being richer with useful enhancements. You can now achieve
following by using this release of the API:
Styling Text Structure: Support of setting text style for structure elements was implemented to TaggedPdf. Access to necessary property perform through StructureTextState property of StructureElement. (Only for Structure Element which implements the ITextElement interface). All properties can be null. Use null to inherit necessary property from parent Structure Element. (Default value is null).
Access Structure Elements Attributes: Access to structure elements attributes was implemented to TaggedPdf. StructureAttributeCollection, StructureAttributes and StructureAttributes classes is intended for work with attributes. AttributeOwnerStandard, AttributeKey and AttributeName classes contain valid values for corresponding entities.
As per the history of monthly API revisions, this release of
the API has also been improved for performance and usability. Following is the list
of useful improvement and fixes in Aspose.PDF for .NET 19.2:
HTML to PDF Conversion Engine has been further
improved
Text Extraction scenarios have been taken care
of to return precise coordinates
Memory consumption in processing text paragraphs
has been optimized
API is further improved to work in non-windows
platforms
Inter-File format conversion is further improved
Text replacement and searching scenarios have
been improved
It would surely be exciting to use API with such above mentioned improvements, enhancements and of course new feature. Now you must have pretty good idea of what’s new in the API and how it can improve your experience to automate PDF documents processing.
Well, story does not end here as you can also check release notes page of this release of the API for every minor detail of the updates. In case you still have inquiries in this regard, you are most welcome to post them in our forums. For more exciting features and news, stay tuned with us.
Its time to augment your document conversion experience. You will be pleased to hear the new features, improvements and bug fixes that we’r going to elaborate in this blog post. Did you ever think of converting and rotating a document at the same time? We make your wish come true with this month’s release of GroupDocs.Conversion for Java 19.4. You can now set page rotation angle when converting to a PDF or Image format. And it only takes a single line of code.
We implemented following new properties:
setRotate(PdfSaveOptions.Rotation.On90)
setRotateAngle(45)
Rotation Feature when Converting to Image Format
We enriched ImageSaveOptions class with a new property that takes rotation angle value as parameter.
Rotation when Converting to PDF
PdfSaveOptions class covers a new property that takes PdfSaveOptions.Rotation enumeration.
More File Formats and Font Substitution Options
Some new document formats are also introduced. Like you can do conversion from EPS, TSV, PCL.
API also permits to set default font and font substitution option when converting from .one file.
Measure Conversion Time
Can we measure or track time for a document conversion? You might be thinking of such a feature. Because its appealing. Therefore, we’ve introduced this in current release. Let’s have a look at its implementation.
Include Hidden Slides in Converted Document
Yes, this is absolutely right. We’ve implemented a property setShowHiddenSlides using that you can decide either to convert or skip hidden slides when converting a Slide document.
Improvements
We always introduce improvements for better usability. This release covers following improvements.
HideWordTrackedChanges option to WordsLoadOptions class
HidePdfAnnotations option to PdfLoadOptions class
HideComments option to CellsLoadOptions, SlidesLoadOptions and WordsLoadOptions class
Bug Fixes
We listen your feedback carefully and make sure to fix the disruptions that you face. Spreadsheets are one of the best way to represent data. Most of the time you add graphs in it. Previously, API was not converting spreadsheets with graphs properly. It was not showing complete data. However, this issue is now fixed.
Width and Height not Working
Furthermore, there was no impact of width and height in the output that you set in ImageSaveOptions. This issue is also now resolved.
Will we get PasswordProtectedException?
Yes, we fixed obfuscation config for com.groupdocs.conversion.exceptions package. You will now get proper exception on processing a password protected document without applying password. Eventually, this exception could be then handled.
To learn more about API integration and usage check out the docs here.
To see the implementation and functionalities, check out the GitHub repository.
At least Windows users won’t deny the advantages of XPS (The XML Paper Specification) format. Forget if it is a paginated fixed-layout format that retains the look and feel of your documents. But, being a shape of electronic paper, the XPS format provides a better way in which you can easily create, share and print digital documents. And, above all, XPS documents can be neither manipulated nor edited easily and can only be viewed on computer systems that have an XPS Viewer installed.
Render your report definition file to XPS
While working in report server to transform report data and layout information into XPS, you might think why SQL Server Reporting Services did not include this format as one of their built-in rendering extension. No worries, Aspose.Cells for Reporting Services is here to cope with it and now it supports the format. Here is a document to check complete list of supported document formats.
To use this useful feature and avail other enhancements, I would recommend you to try the release Aspose.Cells for Reporting Services 19.3. And, if you have a little time, browse Developers’ Guide for your complete reference on what you can deliver using the rendering extension API. You are always welcome to share your review, concerns or feedback on forums.
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.
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.
