Introducing Point Annotation for Words in GroupDocs.Annotation for Java 18.10

Logo ImageWe are excitedly announcing another monthly release of GroupDocs.Annotation for Java 18.10. Using this latest version, you can add Point, Polyline and Watermark annotations in Words and Diagrams document. Beside this, a multitude of bug fixes are also introduced in this release. We therefore recommend you to download this latest release for a better API experience.

Features

Add Watermark, Polyline and Point Annotations in Words and Diagrams document

You can add Watermark, Polyline and Point Annotations in Words and Diagrams document using this latest release.
Following example demonstrates how to add Point annotation in Words document:

// Initialize list of AnnotationInfo
List annotations = new List();
// Point annotation
AnnotationInfo pointAnnnotation = new AnnotationInfo();
pointAnnnotation.setCreatedOn(new Date());
pointAnnnotation.setType(AnnotationType.Point);
pointAnnnotation.setBox(new Rectangle(150.32f, 99.22f, 0, 0));
pointAnnnotation.setPageNumber(0);

annotations.add(pointAnnnotation);

Change Highlight Color of Fonts in Words

This latest release of the API allows users to change highlight color of fonts for Text Annotations in Words document.

Support of Metadata in Slides

Support for Metadata in Slides document is also introduced in this latest release.

Fixes

  • Cleanup in PDF doesn’t remove watermarks
  • Highlight color is not changed in footnotes for highlight annotations in Words
  • Exception while running project on macOS
  • isValidLicense() property of License class always returns false
  • An exception raises while accessing the source document
  • TIFF/Multi TIFF file is either corrupted or black and white when annotated
  • Some annotations are missing while exporting to file
  • Exception while exporting Line and Distance annotation
  • Unable to retrieve un-annotated page image from annotated document

Available Channels and Resources

Here are a few channels and resources for you to download, learn, try and get technical support on Documentation Annotation API:

Feedback

As always, you are welcome to share your feedback to improve this product. We will be happy to know your thoughts. Just create a forum thread and our dedicated support team will be there to respond.

Feedback

We always appreciate and welcome to our valuable users to share their feedback to improve this product. We will be happy to know your thoughts and suggestions. Just create a forum thread and our dedicated support team will be there to respond.

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn
Posted in GroupDocs.Annotation Product Family | Tagged | Leave a comment

Remove Embedded Files in PDF in GroupDocs.Conversion for .NET 18.10

GroupDocs.Conversion

GroupDocs.Conversion for .NET 18.10 comes with some bug fixes and a improvement. Border missing issue in ODS output is now resolved. Please refer to GroupDocs.Conversion for .NET 18.10 release notes for further reference.

Improvements

  • Implement option for removing embedded files in Pdf

Bug Fixes

  • The image inside presentation isn’t the same in ODP output
  • Missing border in ODS Excel output
  • XLSX file eats almost 2 GB RAM while converting and the process never completes

API Resources

Here are a few channels and resources for you to download, learn, try and get technical support on GroupDocs.Conversion:

Feedback

We always welcome you to share your feedback to improve this product. We will be happy to know your thoughts. Just create a forum thread and our dedicated support team will be there to respond.

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn
Posted in GroupDocs.Conversion Product Family | Tagged | Leave a comment

Introducing Image Extraction in GroupDocs.Parser for Java 18.10

GroupDocs.Parser for Java

We are delighted to announce the release of GroupDocs.Parser for Java 18.10. The latest release has come with a useful feature of extracting images from the documents. This feature is introduced for PDF, spreadsheet, presentation and text document formats. For more details, please have a look at the release notes of version 18.10.

Features Introduced

Extracting Images from Documents

To extract images from the page of the document, getImageAreas methods are used. getImageAreas has following overloads:

public IList getImageAreas(int pageIndex);
public IList getImageAreas(int pageIndex, ImageAreaSearchOptions searchOptions);

The method with one parameter returns all images from the page with zero-based pageIndex. The method with ImageAreaSearchOptions optional parameter returns only the images which meet the conditions of the searchOptions. Both versions of the method return a collection of ImageArea objects. ImageAreaSearchOptions class has only one property – Rectangle. If it’s set, the method returns only the images which are intersected with the given Rectangle.

At the moment, this feature is introduced for PDF, text, presentation and spreadsheet documents only. For working examples of extracting images, please refer to the following documentation articles:

Available Channels and Resources

Here are a few channels and resources for you to download, learn, try and get technical support on GroupDocs.Parser:

Feedback

As always, if you have any questions or suggestions, feel free to write on our forum.

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn
Posted in GroupDocs.Parser Product Family | Tagged , , , , , , , | Leave a comment

Extract Images from the Documents using GroupDocs.Parser for .NET 18.10

GroupDocs.Parser for .NET

We are back with another monthly release of GroupDocs.Parser for .NET. The latest release has come with a powerful feature of extracting images from the pages of the document. This feature is introduced for PDF, spreadsheet, presentation and text document formats. For more details, please have a look at the release notes of version 18.10.

Features Introduced

Extracting Images from Documents

To extract images from the page of the document, GetImageAreas methods are used. GetImageAreas has following overloads:

public IList GetImageAreas(int pageIndex);
public IList GetImageAreas(int pageIndex, ImageAreaSearchOptions searchOptions);

The method with one parameter returns all images from the page with zero-based pageIndex. The method with ImageAreaSearchOptions optional parameter returns only the images which meet the conditions of the searchOptions. Both versions of the method return a collection of ImageArea objects. ImageAreaSearchOptions class has only one property – Rectangle. If it’s set, the method returns only the images which are intersected with the given Rectangle.

At the moment, this feature is introduced for PDF, text, presentation and spreadsheet documents only. For working examples of extracting images, please refer to the following documentation articles:

Available Channels and Resources

Here are a few channels and resources for you to download, learn, try and get technical support on GroupDocs.Parser:

Have Queries?

If you have got any queries or concerns about the API, please feel free to get in touch with us over the forum. We’ll be glad to address your concerns.

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn
Posted in GroupDocs.Parser Product Family | Tagged , , , , , , , | Leave a comment

Pen Style is Improved in GroupDocs.Annotation for .NET 18.9

GroupDocs.Annotation for .NET

This month release of GroupDocs.Annotation for .NET 18.9 comes up with some improvements and fixes. Using this latest version, you can annotate documents with improved pen styles. We therefore recommend you to download this latest release of the API to enhance your document annotation experience.

Improvements

  • FontColor cleanup in Slides
  • PenStyle property for following formats:
    • Words
    • Cells
    • Diagrams
    • PDF
    • Slides
    • Images

    Bug Fixes

    • TIFF/Multi TIFF file is either corrupted or black and white when annotated
    • Unstable sorting for Slides and Diagrams documents

    Available Channels and Resources

    Here are a few channels and resources for you to download, learn, try and get technical support on GroupDocs.Annotation:

    Feedback

    We always appreciate and welcome to our valuable users to share their feedback to improve this product. We will be happy to know your thoughts and suggestions. Just create a forum thread and our dedicated support team will be there to respond.

    Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn
    Posted in GroupDocs.Annotation Product Family | Tagged | Leave a comment

    PDF Comparison is Improved in GroupDocs.Comparison for .NET 18.9

    GroupDocs.ComparisonGroupDocs.Comparison for .NET 18.9 comes with some improvements and bug fixes. PDF and HTML anchors comparison is now improved. Please follow the release notes here for further details. We’d recommend you to try latest version of the API and share your feedback.

    Improvements

    • Html Anchors comparing
    • PDF comparison
    • Improve HTML aligner

    Bug Fix

    • Error when comparing Words files protected with password
    • Cannot compare PDF documents

    Available Channels and Resources

    Here are a few channels and resources for you to download, learn, try and get technical support on GroupDocs.Comparison for .NET API:

    Feedback

    You are always welcome to share your feedback and suggestions to improve this product, we take it very seriously and try to incorporate it as much as its possible for upcoming releases . We will be happy to know your thoughts. Just create a forum thread and our dedicated support team will be there to respond.

    Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn
    Posted in GroupDocs.Comparison Product Family | Tagged | Leave a comment

    Exclude Specific Fonts from Output HTML using GroupDocs.Viewer for .NET 18.10

    Document Viewer API

    We are pleased to announce the release of GroupDocs.Viewer for .NET 18.10. The latest version allows setting the list of the fonts that should be excluded from the output HTML to decrease the size of the output files. Furthermore, the inclusion of 5 improvements and 6 bug fixes have made the API more promising. Below is the list of new features, improvements, and fixes added in v18.10.

    Features Introduced

    Setting List of the Fonts to be Excluded

    Adding fonts into HTML ensures that the text from the original document will appear similar in HTML, regardless of whether fonts are installed on the viewer’s device or not. At the same time, this improvement comes with the cost of the increased size of the output file. Therefore, GroupDocs.Viewer API provides a new setting – HtmlOptions.ExcludeFontsList, that prevents adding specific fonts (that are commonly available on most of the devices). The code sample below shows how to prevent adding fonts into output HTML.

    // Setup GroupDocs.Viewer config
    ViewerConfig config = new ViewerConfig();
    config.StoragePath = @"C:\storage";
      
    // Create html handler
    ViewerHtmlHandler htmlHandler = new ViewerHtmlHandler(config);
    string guid = "presentation.pptx";
      
    HtmlOptions options = new HtmlOptions();
    options.ExcludeFontsList.Add("Times New Roman");
    options.ExcludeFontsList.Add("Arial");
    List pages = htmlHandler.GetPages(guid, options);
      
      
    foreach (PageHtml page in pages)
    {
        Console.WriteLine("Page number: {0}", page.PageNumber);
        Console.WriteLine("Html content: {0}", page.HtmlContent);
    }

    For more details on this feature, please visit this documentation article.

    Improvements

    We have included following improvements in version 18.10:

    • Prevent showing items beyond StartDate and EndDate options when rendering MS Project documents
    • Release internal resources for methods which accept URL
    • GetDocumentInfo method’s page number depending on the type of ViewerHandler
    • Prevent setting malicious values for HtmlResourcePrefix
    • Improve setting PageSize and TimeScale for MS Project documents by default

    Bug Fixes

    Following issues are fixed in version 18.10 of GroupDocs.Viewer for .NET.

    • “Specified watermark font not found” exception when calling GetPdfFile method
    • OutlookOptions.MaxItemsInFolder option not working properly for rendering into image and PDF
    • Incorrect rendering of PDF document into HTML
    • Duplicate link tag when rendering text documents with external resources
    • Exception when rendering PDF document as HTML
    • Images are missing when rendering PDF document into HTML or Image

    Related Links and Resources

    We have a few channels and resources for you to download, learn, try and get technical support on GroupDocs.Viewer.

    Feedback

    As always, if you have any questions or suggestions, feel free to write on our forum.

    Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn
    Posted in GroupDocs.Viewer Product Family | Tagged , , , , , , , | Leave a comment

    Set Target File Format using GroupDocs.Assembly for Java 18.9

    Document Assembly APIWe are excitedly announcing a new feature in the monthly release of GroupDocs.Assembly for Java 18.9.  Using the latest version,  you can now change the target file format of an assembled document using file extension or explicit specification. You can change the target file format when assembling Word Processing, Spreadsheet, Presentation, Email and Text file formats. We recommend you to install the latest version of the API for a better user experience.

    Features Introduced

    Since version 18.9, you can change the format of the assembled document either by specification of the file extension or using LoadSaveOptions as shown in the following code snippets.

    Changing the target file format using the file extension

    DataSourceInfo dataSourceInfo = new DataSourceInfo(...);
    DocumentAssembler assembler = new DocumentAssembler();
      
    assembler.assembleDocument("template.docx", "result.pdf", dataSourceInfo);

    Changing target file format using explicit specification

    InputStream sourceStream = ...;
    OutputStream targetStream = ...;
      
    DataSourceInfo dataSourceInfo = new DataSourceInfo(...);
    DocumentAssembler assembler = new DocumentAssembler();
      
    assembler.assembleDocument(sourceStream, targetStream, new LoadSaveOptions(FileFormat.PDF), dataSourceInfo);

    For more details on this feature, please visit this documentation article.

    At the moment, GroupDocs.Assembly API provides the ability to change target file format when assembling the following file formats:

    • Word Processing documents
    • Spreadsheet documents
    • Presentation documents
    • Email documents
    • Text documents

    Supported output file formats depending on input file formats can be found at this page.

    API Changes

    Newly Added Types

    Following types are added in the latest version.

    public class DataSourceInfo
    public enum FileFormat
    public class LoadSaveOptions
    

    Newly Added Members of DocumentAssembler

    Following members of DocumentAssembler are added in the latest version.

    public void assembleDocument(String sourcePath, String targetPath, DataSourceInfo... dataSourceInfos) throws Exception
    public void assembleDocument(String sourcePath, String targetPath, LoadSaveOptions loadSaveOptions, DataSourceInfo... dataSourceInfos) throws Exception
    public void assembleDocument(InputStream sourceStream, OutputStream targetStream, DataSourceInfo... dataSourceInfos) throws Exception
    public void assembleDocument(InputStream sourceStream, OutputStream targetStream, LoadSaveOptions loadSaveOptions, DataSourceInfo... dataSourceInfos) throws Exception
    

    Removed Members of DocumentAssembler

    Following members of DocumentAssembler are removed in the latest version.

    public void assembleDocument(String sourcePath, String targetPath, Object dataSource)
    public void assembleDocument(String sourcePath, String targetPath, Object dataSource, String dataSourceName)
    public void assembleDocument(String sourcePath, String targetPath, Object[] dataSources, String[] dataSourceNames)
    public void assembleDocument(InputStream sourceStream, OutputStream targetStream, Object dataSource)
    public void assembleDocument(InputStream sourceStream, OutputStream targetStream, Object dataSource, String dataSourceName)
    public void assembleDocument(InputStream sourceStream, OutputStream targetStream, Object[] dataSources, String[] dataSourceNames)

    Breaking Change

    Removed members of DocumentAssembler were replaced with new ones. Removed members were not marked as obsolete (deprecated) before removal as usual, because this would complicate migration to new members of DocumentAssembler in Java. Thus, we have introduced a breaking change and customers need to migrate their code from removed members of DocumentAssembler to newly added ones when upgrading to the new version of GroupDocs.Assembly.
    For more details, please visit this documentation article.

    Since version 18.9, the Metered licensing security has been improved. Metered licensing is now applicable only in Java runtime version 8u101 or above. Please use other types of licensing if you are using v18.9 or greater in Java 7.

    Available Channels and Resources

    Here are a few channels and resources for you to download, try, learn and get technical support on GroupDocs.Assembly for Java:

    Feedback

    We always love to hear your valuable feedback. Share your suggestions, questions, or queries related to GroupDocs.Assembly for Java at our forum.

    Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn
    Posted in GroupDocs.Assembly Product Family | Tagged , , | Leave a comment

    Change Target File Format using GroupDocs.Assembly for .NET 18.9

    We are delighted to announce a powerful new feature in the monthly release of GroupDocs.Assembly for .NET 18.9. Using the latest version,  you can now change the target file format of an assembled document using file extension or explicit specification. You can change the target file format when assembling Word Processing, Spreadsheet, Presentation, Email and Text file formats. We recommend you to install and use the latest version of the API.

    Features Introduced

    Since version 18.9, you can change the format of the assembled document either by specification of the file extension or using LoadSaveOptions as shown in the following code snippets.

    Changing the target file format using the file extension

    DataSourceInfo dataSourceInfo = new DataSourceInfo(...);
    DocumentAssembler assembler = new DocumentAssembler();
      
    assembler.AssembleDocument("template.docx", "result.pdf", dataSourceInfo);

    Changing target file format using explicit specification

    Stream sourceStream = ...;
    Stream targetStream = ...;
      
    DataSourceInfo dataSourceInfo = new DataSourceInfo(...);
    DocumentAssembler assembler = new DocumentAssembler();
      
    assembler.AssembleDocument(sourceStream, targetStream, 
    new LoadSaveOptions(FileFormat.Pdf), dataSourceInfo);

    For more details on this feature, please visit this documentation article.

    At the moment, GroupDocs.Assembly API provides the ability to change target file format when assembling the following file formats:

    • Word Processing documents
    • Spreadsheet documents
    • Presentation documents
    • Email documents
    • Text documents

    Supported output file formats depending on input file formats can be found at this page.

    API Changes

    Newly Added Types

    Following types are added in the latest version.

    public class DataSourceInfo
    public enum FileFormat
    public class LoadSaveOptions
    

    Newly Added Members of DocumentAssembler

    Following members of DocumentAssembler are added in the latest version.

    public void AssembleDocument(string sourcePath, string targetPath, params DataSourceInfo[] dataSourceInfos)
    public void AssembleDocument(string sourcePath, string targetPath, LoadSaveOptions loadSaveOptions, params DataSourceInfo[] dataSourceInfos)
    public void AssembleDocument(Stream sourceStream, Stream targetStream, params DataSourceInfo[] dataSourceInfos)
    public void AssembleDocument(Stream sourceStream, Stream targetStream, LoadSaveOptions loadSaveOptions, params DataSourceInfo[] dataSourceInfos)

    Removed Members of DocumentAssembler

    Following members of DocumentAssembler are removed in the latest version.

    public void AssembleDocument(string sourcePath, string targetPath, object dataSource)
    public void AssembleDocument(string sourcePath, string targetPath, object dataSource, string dataSourceName)
    public void AssembleDocument(string sourcePath, string targetPath, object[] dataSources, string[] dataSourceNames)
    public void AssembleDocument(Stream sourceStream, Stream targetStream, object dataSource)
    public void AssembleDocument(Stream sourceStream, Stream targetStream, object dataSource, string dataSourceName)
    public void AssembleDocument(Stream sourceStream, Stream targetStream, object[] dataSources, string[] dataSourceNames)

    Breaking Changes

    Removed members of DocumentAssembler are replaced with new ones. Removed members were not marked as obsolete (deprecated) before removal as usual, because this would complicate migration to new members of DocumentAssembler in Java. Thus, we have introduced a breaking change and customers need to migrate their code from removed members of DocumentAssembler to newly added ones when upgrading to the new version of GroupDocs.Assembly.
    For more details, please visit this documentation article.

    Available Channels and Resources

    Here are a few channels and resources for you to download, learn, try and get technical support on GroupDocs.Assembly for .NET.

    Feedback

    As always, if you have some questions, queries or suggestions about GroupDocs.Assembly for .NET API,  just share with us by creating a forum thread.

    Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn
    Posted in GroupDocs.Assembly Product Family | Tagged , , | Leave a comment

    Conversion from PLT Format is Introduced in GroupDocs.Conversion for .NET 18.9

    GroupDocs.Conversion

    GroupDocs.Conversion for .NET 18.9 covers some new features, improvements and major bug fixes. Conversion from PLT and LGS formats is introduced. Aside this, Word, Image and HTML conversion options are improved. Excel to SVG conversion issue is fixed. Please refer to GroupDocs.Conversion for .NET 18.9 release notes for further reference. We’d recommend you to integrate latest version of the API in your applications and share your feedback.

    Features

    • Implement conversion from PLT, LGS and CGM
    • Password protection when converting to ODS
    • Support converting password protected ODS document

    Improvements

    • Pdf to Cells improvement
    • Improve Words, Slides, Image, HTML, PDF and Cells conversion options

    Bug Fixes

    • XLS to HTML output is too small
    • Excel to SVG conversion issue
    • Xps to Pdf conversion issue

    API Resources

    Here are a few channels and resources for you to download, learn, try and get technical support on GroupDocs.Conversion:

    Feedback

    We always welcome you to share your feedback to improve this product. We will be happy to know your thoughts. Just create a forum thread and our dedicated support team will be there to respond.

    Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn
    Posted in GroupDocs.Conversion Product Family | Tagged | Leave a comment