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

    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

    Advanced Documents Conversion APIs for .NET and Java – GroupDocs Newsletter October 2018

    LinkedIn Google+ Twitter Facebook
    Share this issue:

    Monthly Newsletter

    October 2018

    Business Documents Conversion APIs for .NET and Java
    Convert between 50+ Document and Image File Formats
    Securely Sign Official Documents with Stamp Signatures

    GroupDocs.Conversion Product Family combines .NET and Java APIs suite for faster and accurate conversion of business documents and image file formats between Word, Excel, PowerPoint, PDF, Visio, Project, Outlook, HTML, Photoshop, AutoCAD and image formats. Using the document converter API is very simple as it uses just one method with set of options to convert between different formats.

    Explore NOWDownload FREE 30-Days Trial

    Available for: .NETJava

    Product News

    Product News

    Product News

    From the Library

    From the Library

    From the Library

    Feedback

    Feedback

    Feedback
    GroupDocs for .NETGroupDocs for JavaGroupDocs for Cloud APIs
    Product Releases and Updates

    Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn
    Posted in Customer Newsletters | Leave a comment

    Get List of Indexed Documents using GroupDocs.Search for .NET 18.9

    GroupDocs.Search for .NETWe are pleased to announce the monthly release of GroupDocs.Search for .NET 18.9.  Using the latest version, you can now get the list of indexed documents and document’s text from the index archive. Moreover, you can now save encodings automatically which were used to extract text from TXT files.  We would recommend you to install and use the latest version of the API.

    Enhancements

    Following are the enhancements introduced in the latest version:

    Get List of Indexed Documents

    Using GroupDocs.Search API you can get a list of indexed documents and items from container documents like ZIP archives, OST and PST files. This example shows how to get a list of indexed documents from an index:

    
    string indexFolder = @"c:\MyIndex";
      
    // Creating index from existing folder
    Index index = new Index(indexFolder);
      
    // Getting list of indexed documents
    DocumentInfo[] documents = index.GetIndexedDocuments();
      
    // Getting items of container document
    DocumentInfo[] items = index.GetIndexedDocumentItems(documents[0]);

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

    Extract Document Text

    Using the latest verion, you can now extract document text from the index archive or from a document directly if archiving is not used. An extracted text can be used to check an encoding that is used for indexing text documents. Also, it can be used for quick manual checking of the presence or absence of any words in documents. This example shows how to extract document text from the index:

    
    string indexFolder = @"c:\MyIndex";
       
    // Creating index from existing folder
    Index index = new Index(indexFolder);
       
    // Getting list of indexed documents
    DocumentInfo[] documents = index.GetIndexedDocuments();
      
    // Extracting HTML formatted document text
    string htmlText = index.ExtractDocumentText(documents[0], null);

    This example shows how to extract document text to a file:

    
    string indexFolder = @"c:\MyIndex";
       
    // Creating index from existing folder
    Index index = new Index(indexFolder);
       
    // Getting list of indexed documents
    DocumentInfo[] documents = index.GetIndexedDocuments();
      
    // Extracting HTML formatted document text to a file
    index.ExtractDocumentText(@"c:\DocumentText.html", documents[0], null);

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

    Save Encodings Automatically

    GroupDocs.Search for .NET 18.9 implements automatic saving of encodings which were used to extract text from TXT files. In practice, this means that there is no longer any need to provide an encoding when generating document text with highlighted found words. This example shows how to generate HTML formatted text with highlighted found words:

    
    string indexFolder = @"c:\MyIndex";
    string documentFolder = @"c:\MyDocuments";
      
    // Creating index
    Index index = new Index(indexFolder);
      
    // Subscribing to file indexing event
    index.FileIndexing += (sender, args) =>
    {
        // Setting encoding for each text file during indexing
        args.Encoding = Encodings.windows_1251;
    };
      
    // Adding text documents encoded in windows-1251 to index
    index.AddToIndex(documentFolder);
      
    // Searching for word 'человеческий'
    SearchResults results = index.Search("человеческий");
      
    // Generating HTML formatted text with highlighted found words
    // There is no need to provide the encoding again - it is saved in the index
    string htmlText = index.HighlightInText(results[0]);

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

    Available Channels and Resources

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

    Feedback

    If you have any suggestions, questions, or queries related to the GroupDocs.Search for .NET API, we will be happy to hear from you. Just create a forum thread to share your thoughts.

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

    Announcing Hotfix release of GroupDocs Signature for .NET 18.9.1

    GroupDocs.Signature

    This blog post covers the hotfix introduced in GroupDocs.Signature for .NET 18.9.1. In previous version of the API there was a issue while signing PDF with Metadata Signatures. But now this issue has been fixed. We therefore, recommend you to download the new release and enhance document e-signing experience.

    Bug Fix

    • Exception is thrown while signing PDF with Metadata Signatures

    Available Channels and Resources

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

    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.

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