Chart layout/result in output Word document will look like this:
Access Revised Version of a Document
The API now provides RevisionsView public enumeration which allows specifying whether to work with the original or revised version of a document. The document class provides RevisionsView property which can be used to get or set enumeration value. The default value is Aspose.Words.RevisionsView.Original.
The code example given below shows how to use this enumeration and access the revised version.
Download Examples at GitHub Repository – we have published our code examples on the social coding website GitHub.com. Anyone could explore the code examples for learning purposes.
Keeping the Aspose tradition, you are welcome to shape the upcoming releases of Aspose.Words for Java API by posting your suggestions and concerns in the Aspose.Words for Java Support Forum.
It is our honor to announce the latest version of Aspose.Words for Reporting Services i.e. 19.7. We have upgraded it to Aspose.Words for .NET 19.7. Please check the release notes.
You can download the latest release of Aspose.Words for Reporting Services 19.7 from the following link:
Hi guys! We are gratified to announce the new version of Aspose.Words for .NET i.e. 19.8. Starting from this release, you can define default options for data labels of chart series. You can also work with original or revised version of Word document. let’s check out how to work with these features.
Work with Original and Revised Version of Document
Revision (track change) is a way for Word document to keep track of changes you make in a document. We have added new feature in this release to work with original and revised version of a document. A new property Document.RevisionsView has been added for this feature along with RevisionsView enumeration. This property is used to get or set a value indicating whether to work with the original or revised version of a document. Following code example shows how to work with revised version of document.
Define Default Options for Data Labels of Chart Series
You may have worked with data labels of chart series in Word document. Data Labels make a chart easier to understand as they show detail of data series or individual data points. You can add labels to chart series depending on your requirement. We have added new properties e.g. ShowSeriesName, ShowPercentage, ShowLegendKey, ShowBubbleSize, ShowCategoryName etc. in ChartDataLabelCollection class. You can use these properties to set default options for data labels. Following code example shows how to use these properties.
We recommend you please check the release notes of Aspose.Words for .NET 19.8 for complete detail of API changes.
Aspose, a file formats API provider, has decided to rename Aspose.Cells for JavaScript via Java to Aspose.Cells for Node.js via Java. Aspose.Cells for Node.js via Java is a subset component that includes all the important and useful features present in its native Aspose.Cells for Java. Aspose.Cells for Node.js via Java presents all the useful features of Aspose.Cells for Java using Node.js. It is a class library that enables you to perform a great range of spreadsheet processing tasks. Aspose.Cells for JavaScript via Java is a scalable and feature rich API that offers spreadsheet format conversion, styling of worksheets at every level, chart management & rendering, and our reliable Formula Calculation Engine. Aspose.Cells for Node.js via Java supports XLS, XLSX, ODS, SpreadsheetML, CSV, Tab Delimited, HTML/MHTML, PDF, XPS and other formats. With Aspose.Cells for Node.js via Java you can generate, modify, convert and render Excel documents. You will have full programmatic access through a rich APIs set to all MS Excel document objects and formatting that allows to create, modify, extract, copy, merge, and replace spreadsheet content. With Aspose.Cells for Node.js via Java, developers can export data, format spreadsheets to the most granular level, create, manipulate and render charts, apply and calculate complex formulas efficiently and much more.
Important to Know
Please note, The APIs structure still remains the same, so it won’t disturb our existing clients who can still use the APIs without any changes in the code. We will soon revamp the Wiki Conf. Docs accordingly. We will also change Aspose.Cells for JavaScript via Java node to Aspose.Cells for Node.js via Java in Downloads section. Moreover, the Aspose.Cells for JavaScript via Java product pages will be soon updated. Similarly API Reference section for the product and other important areas will be accommodated accordingly.
The world admires Batman and Superman. They both have billions of fans together. They both have a different character, different powers, different qualities, and features. Even the fan base quarrel with each other about which superhero is better than the other one. One can always hear rants about Batman vs Superman. What if there was nothing like Batman vs Superman and they both worked together – serving humanity and saving the world? The world would definitely be a better place to live in!
Well, not for the whole world, but we can make life easier for .NET and Java developers working with XPS and EPS documents. We had Aspose.XPS and Aspose.EPS for manipulating XPS and EPS documents. Now, there is nothing like Aspose.XPS vs Aspose.EPS – They both are working together serving the developers – we call the new product Aspose.Page.
If you were a fan of Aspose.XPS or EPS there is nothing to worry. You can access all the features of both products with your existing license. Now combined together – we can have an even bigger fan base. Now let’s jump inside the code to get highlights of the product.
Convert XPS to PDF
Aspose.Page allows document conversion. For instance, you can convert XPS to PDF. Let’s try out the examples for conversion.
.NET
Java
This is the overview how the product words. The API offers other handful features for manipulate XPS and EPS documents. For more details, please feel free to visit documentation. To explore more examples you can access our open source examples and in case you would have any query, please feel to contact us using our forum.
Aspose.Slides now supports the Morph Transition.The Morph transition allows you to animate in a smooth movement from one slide to the next. This feature is introduced in PowerPoint 2019. You can apply this feature to animate text, shapes, pictures, SmartArt, WordArt, and charts.
Note: Morph is supported in Office 365 and PowerPoint 2019 and as a transition, it is located in the Transition menu inside of the ribbon.
With Morph, you no longer need to use complicated animation sequences which would have been pretty daunting to a non-PowerPoint expert. Morph allows you to create animations which gives off a vibe of seamless continuity. It makes your viewers think you created your presentation with advanced video-editing software and not PowerPoint.
If you are willing to think outside the box a little bit,
you can create the most magical PowerPoint presentations, and your audience
will never think it was done on PowerPoint!
The purpose of this post is to demonstrate how Morph Transition works with Aspose.Slides.
How to Set Up a Morph Transition
To get started with morphing transition effects, you are
going to create a base slide first. This is where you add the objects you want
to morph. Once you are done with your base slide, you are going to need to duplicate
it.
On the duplicated slide, you can move around the objects, you can change the colors, sizes, etc. Basically, what you want your base objects to morph into, that is what you need to do on the duplicated slide. Once you have got your second slide set up, then you can click on Morph and preview the effects.
In the following example, we have demonstrated how to add a clone of the slide with some text to the presentation and set a transition of morph type to the second slide.
The equivalent Java implementation for this is as under:
Finally, after adding the Morph Transition, the output looks as follows:
The complete code of this post is available on GitHub for .NET and Java.
Aspose.BarCode for Java 19.6 is released which contains new properties and improvements which will ease your work to read and write barcodes with ECI encoding information and also make possible to read low-resolution TIFF images. These API changes and other details can be obtained in the release note page of the API documentation. Let me share the details of these new features and their use in the programming.
ECI Encoding
Implementing barcode reading is quite a complex task. Bar code readers need a lot of configurations and information while reading a barcode e.g. the used references for encoding the data in the symbol. This information is embedded in the barcode by adding Extended Channel Interpretation (ECI) setting in the barcode. This mechanism allows usually unsupported national character sets such as Arabic, Greek or Japanese to be used in barcode symbols. When a symbol is scanned, this information is not intended to be the part of the barcode data, that is why it is kept transparent while scanning a symbol. It is just a switch or tick-box that is checked by the reader followed by a symbology-dependent ECI selection. In Basic Channel Mode, the ECI control information is not transmitted from the reader to the host system. In Extended Channel Mode, both the ECI control information and the data are transmitted to the host system.
Aspose.Barcode has implemented this feature by providing a property QrParameters.setQrECIEncoding() and getQrECIEncoding() in the barcode generator class. For example, if you want to set the encoding mode to ECI and encoding scheme to UTF 8 you should use the following statements while creating a barcode.
Following are the ECI encodings which are provided while using this feature.
Some times there are images which are quite low in resolution and cannot be detected like one of the reasons can be fully wiped bars in the barcode. This issue can make them too difficult rather impossible to be read by any barcode reading software. We have put a special effort for this and added a new property to overcome this issue. New public property AllowOneDWipedBarsRestoration has been added to the QualitySettings. It allows engine for 1D barcodes to recognize barcodes with single wiped/glued bars in pattern. Property is enabled by default in HighQuality, MaxBarCodes modes.
Currently the property is used for Code128, GS1Code128, SCC14, EAN14, SSCC18, AustralianPosteParcel, SwissPostParcel barcode types. You can use this feature by calling following line of code before reading information from a BarCodeReader object to signal it to read low resolution TIFF images.
Did you have a look at the above image? Please have a look again and look closely! This is just a glimpse of all the file formats we work on everyday at Aspose; and there are many more formats.
We have helped a lot of customers and developers add file format management capabilities in their products during the past decade. We stand by our customers to support them in building great products having file format processing features.
However, some customers find it difficult to get started quickly due to the availability of so many file processing APIs at Aspose, supporting so many formats and offering a lot of features. That’s why we’re introducing this new free consulting service for our valued customers and developers.
The process is very simple. You just have to have an idea of the requirements of a small project including a feature set of file processing APIs offered by Aspose. The project should be doable in 8 or less working hours by a single developer. It must be related to Aspose APIs. It should help you understand the usage of our APIs in your custom scenario.
You can provide us requirements, along with platform details like operating system and development environment. You can also share the input and required output documents or examples. Any other information that can help us understand your needs and requirements would be helpful for us to provide you a solution quickly.
Once we have the above information, we’ll start working on your custom free consulting project, for you and your team to understand the usage of Aspose APIs easily and quickly. This will help you jump right into your next big project or milestone.
Please note that this should not be a bug report about our APIs or a new feature request to be supported by Aspose APIs. If you have such a request then please post it in our free support forums where our dedicated support team will help you quickly to sort it out.
Do you need to process SXC and FODS file formats and want to have an API to handle these files? Aspose.Cells is the right library which will enable you to open or edit and save both OpenOffice/LibreOffice file types. You may also find other features and enhancements in the new Aspose.Cells for .NET v19.6. So let’s not wait another moment to review the release notes. To get complete details of the public release (Aspose.Cells for .NET v19.6), I am giving you preview of the new features, enhancements and fixes available in it.
Support for SXC and FODS
We always try to provide features which are supported by other spreadsheet handling software. Many users demanded support of SXC and FODS file types which are very common. So, here we are with the support of these file types in the latest release. Following is a brief description of these types along with the detail of their support in Aspose.Cells.
SXC Files
Spreadsheet created by StarOffice Calc; supports formulas, functions, charts, and macros; also includes DataPilot tables, which can automatically extract and summarize data from raw data sets. SXC files are also compatible with Apache OpenOffice Calc and can be exported in Microsoft Excel or IBM Lotus 1-2-3 formats.
FODS Files
Spreadsheet saved in the OpenDocument format, but stored as a flat XML file instead of the ..ZIP container used by .ODS files; allows the spreadsheet information to be more human readable; also can be an easier alternative than the ODS format for generating spreadsheets automatically without needing a spreadsheet editor.
Features provided by Aspose.Cells
Generate file
You can generate SXC and FODS file using FileFormatType as argument in Workbook contructor i.e. use FileFormatType.SXC and FileFormatType.FODS as argument.
Load file
These files can be loaded using enumerator LoadFormat as follows:
SXC FileFODS File
Save File
Saving file of these types is quite easy by using SaveFormat enumerator while calling the Workbook.Save() function with second argument as SaveFormat.SXC and SaveFormat.FODS.
Security warning after re-saving an XLS file format.
Problems with medium lines/thick lines when XLSX saved as ODS.
Detecting whether the object file is chart or oleobject for ODS.
Handled "System.InvalidCastException".
Handled "Shape to image error!" when converting XLSX to PDF.
Handled an exception "System.StackOverflowException" on rendering an Excel file to PDF file format.
To use these features and avail other enhancements and fixes, I recommend you to try the release Aspose.Cells for .NET v19.6. Moreover, I recommend you to browse Developers’ Guide for your complete reference on what you can deliver using the APIs. Also, you are always welcome to share your review, concerns or feedback on forums.
A new version Aspose.Cells for Java 19.6 is released that handles file types SXC and FODS, contains a lot of enhancements and few bug removals. Support for handling file types SXC and FODS is added like you can generate, load and save these files. This release also contains improvements for handling files with large conditional formattings, enhancements in the process of saving Excel files with data formats, filters and chart rendering. You can get the details of all these enhancements and changes in the release notes. You might be curious about the new features, enhancements and exceptions handled in this release, so let us start to review this release in detail.
Support for SXC and FODS
We always try to provide features which are supported by other spreadsheet handling software. Many users demanded support of SXC and FODS file types which are very common. So, here we are with the support of these file types in the latest release. Following is a brief description of these types along with the detail of their support in Aspose.Cells.
SXC Files
Spreadsheet created by StarOffice Calc; supports formulas, functions, charts, and macros; also includes DataPilot tables, which can automatically extract and summarize data from raw data sets. SXC files are also compatible with Apache OpenOffice Calc and can be exported in Microsoft Excel or IBM Lotus 1-2-3 formats.
FODS Files
Spreadsheet saved in the OpenDocument format, but stored as a flat XML file instead of the ..ZIP container used by .ODS files; allows the spreadsheet information to be more human readable; also can be an easier alternative than the ODS format for generating spreadsheets automatically without needing a spreadsheet editor.
Features provided by Aspose.Cells
Generate file
You can generate SXC and FODS file using FileFormatType as argument in Workbook contructor i.e. use FileFormatType.SXC and FileFormatType.FODS as argument.
Load file
These files can be loaded using enumerator LoadFormat as follows:
SXC File
FODS File
Save File
Saving file of these types is quite easy by using SaveFormat enumerator while calling the Workbook.save() function with second argument as SaveFormat.SXC and SaveFormat.FODS.
Improvements in this version
Handling Excel file with large conditional formatting
While converting Excel files having large conditional formatting to PDF, sometimes there was an “Out of memory” exception in JVM. This exception is handled successfully now.
Maintaining data format while saving Excel file
Excel files can have different data formatting settings along with the conditional formatting. An issue was reported about showing value with fraction instead of whole number. This type of issues are handled and now data formats are maintained while saving the Excel files.
Improve reading Excel 95 files
Excel 95 files are still very common and need to be handled error-free while using Aspose.Cells. Sometimes an exception was raised as java.lang.NullPointerException for these files. This issue is removed now and Excel 95 files can be loaded without any issue.
Enhance loading speed after deleting columns
A case was reported where after deleting the columns from an existing file and saving it on the disc, loading was quite slow for this modified file. It is suggested that always take care of the conditional formatting ranges. For these, you should merge them by setting SaveOptions.MergeArea to true before saving them. We have also improved the saving operation and now modified files do not take a long time to load.
Bugs and Exceptions
Users report bugs and exceptions which are resolved and enhancements are done which improves the usability of the library. Following are few bugs and exceptions which were handled in this release.
Conditional formatting can be obtained properly using Cell.getDisplayStyle() after setting different values in the cell containing these conditional formatting based on the cell value. Like foreground colour value which was not obtained correctly earlier in some case can be obtained now.
There was an issue where lines were not rendered in the PDF from an Excel file. This issue is resolved and lines are rendered fine. Following is the depiction of the issue for better understanding.
This is common to add images in the header of an Excel file. It was observed that in some cases, the output file after adding these images, was corrupted and could not be opened in Excel. This issue is resolved and now images can be added without any problem.
Filters should be maintained while opening and saving a file. A user faced an error that filter was lost after saving the file. Similarly in another case filters were changed. This is no more an issue now.
A chart was getting flattened in the saved file after loading it. This issue is resolved in the current release.
While loading an ODS file an exception “Invalid “‘””(“Based on Name “test_name) was observed. This issue is resolved.
A user reported that he is getting exception while calling Name.getRefersTo() function. This issue is resolved in this release.
For all the resources, documentation, examples and forum support please visit here.
