Support of Rendering Document to PCL, Changed Importing Behavior of Lists, and Improved Removing Unused Resources from Document in Aspose.Words for .NET 17.7

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

Aspose.Words for .NET logoWe are pleased to announce our next version Aspose.Words for .NET 17.7. This month’s release contains over 82 useful new features, enhancements and bug fixes. Please see the release notes for more detail. If you are planning to upgrade from older version of Aspose.Words to the current version, we would strongly suggest you to check the Public API and Backward Incompatible Changes section to know what APIs are changed so far.


Here is a look at just a few of the biggest features and API changes in this month’s release.

  • Rendering into PCL format (Printer Command Language) has implemented. New saving format introduced – “SaveFormat.Pcl”. Please note that custom fonts is not yet supported.
  • The proper algorithm for rendering of shapes with automatic size textboxes (i.e. closest to MS Word output) implemented.
  • The rendered PDF documents can now show the document title in the title bar of the viewer. This is controlled by “PdfSaveOptions.DisplayDocTitle” property.
  • Improved font rendering in PDF documents for Adobe Illustrator limitations.
  • Improved rendering of fonts with simulated bold style.
  • Vertical text rendering in DrawingML textboxes improved.
  • Problem with rendering of numbers on horizontal axis in DrawingML Charts fixed.
  • Implemented support for “Wrap trailing spaces to next line” option.
  • Implemented support for footnote continuation notices.
  • Improved text wrapping logic for “2013 and later” documents.
  • Improved non-breaking space width calculation.
  • Improved Asian text justification logic.

Rendering Word Document to PCL format Supported

We have introduced new saving format – PCL (Printer Command Language) in Aspose.Words for .NET 17.7. Aspose.Words can save documents to PCL 6 (PCL 6 Enhanced or PCL XL) format. There is one major feature of PCL that is unsupported in current version of Aspose.Words i.e. custom fonts. It is rather big and complex problem, but we will implement this feature in future. We have added new value to enum SaveFormat:

SaveFormat.Pcl

Please check the code example from here: 
Save Document to PCL

PclSaveOptions has following public options and methods:


/// <summary>
/// Gets or sets a value determining whether or not complex transformed elements
/// should be rasterized before saving to PCL document.
/// Default is <c>true</c>.
/// </summary>
/// <remarks>
/// PCL doesn't support some kind of transformations that are used by Aspose Words.
/// E.g. rotated, skewed images and texture brushes. To properly render such elements
/// rasterization process is used, i.e. saving to image and clipping.
/// This process can take additional time and memory.
/// If flag is set to <c>false</c>, some content in output may be different
/// as compared with the source document.
/// </remarks>
public bool RasterizeTransformedElements
{  get; set; }
 
/// <summary>
/// Adds information about font that is uploaded to the printer by manufacturer.
/// </summary>
/// <param name="fontFullName">Full name of the font (e.g. "Times New Roman Bold Italic").</param>
/// <param name="fontPclName">Name of the font that is used in Pcl document.</param>
/// <remarks>
/// There are 52 fonts that are to be built in any printer according to Pcl specification.
/// However manufactures can add some other fonts to their devices.
/// </remarks>
public void AddPrinterFont(string fontFullName, string fontPclName);
 
/// <summary>
/// Name of the font that will be used
/// if no expected font is found in printer and built-in fonts collections.
/// </summary>
/// <remarks>
/// If no fallback is found, warning is generated and "Arial" font is used.
/// </remarks>
public string FalllbackFontName
{  get; set; }

Added Public Property PdfSaveOptions.DisplayDocTitle

We have added new feature in Aspose.Words for .NET 17.7 to control behavior of how document’s title is presented in output PDF document. The PdfSaveOptions.DisplayDocTitle property is added in this version. This property is used to specify whether window’s title bar should display the document title taken from the Title entry of the document information dictionary. Please refer to the following article for more detail:
Display the Document’s Title in Window’s Title bar

/// <summary>
/// A flag specifying whether the window’s title bar should display the document title taken from
/// the Title entry of the document information dictionary.
/// </summary>
/// <remarks>
/// If <c>false</c>, the title bar should instead display the name
/// of the PDF file containing the document.
///
/// <para>The default value is <c>false</c>.</para>
/// </remarks>
public bool DisplayDocTitle
{
    get { return mDisplayDocTitle; }
    set { mDisplayDocTitle = value; }
}

Improved Removing Unused Resources From Document

Document.RemoveUnusedResources method is now obsolete. We have added new method Document.Cleanup in Aspose.Words for .NET 17.7 to remove unused styles and lists from the document. Now you can remove only lists or styles or both from document. Please refer to the following article for more detail.
Remove Unused Styles and Lists from Document

Changed Importing Behavior of Lists

Previously, list definitions were copied with a new identifier while importing. Now Aspose.Words reuses identical list definitions in the destination. Equality of list definitions in the source and destination is determined by their identifiers. Also Aspose.Words preserves list definition identifiers from the source when equal list definition cannot be found in the destination. This is how MS Word behaves.

Shape.AspectRatioLocked Default Value was Changed for Shapes Inserted through the DocumentBuilder.InsertImage Method

Shape.AspectRatioLocked default value was changed for shapes inserted through the DocumentBuilder.InsertImage method. Now, to mimic MS Word behavior this value is “true” for ShapeType.Image upon inserting image through the DocumentBuilder or through the Model. Please check the code example from here:

Lock Aspect Ratio of Image


/// Specifies whether the shape's aspect ratio is locked.
/// </summary>
/// <remarks>
/// <p>The default value depends on the <see cref="ShapeType"/>, for the ShapeType.Image it is <b>true</b>
/// but for the other shape types it is <b>false</b>.</p>
/// <p>Has effect for top level shapes only.</p>
/// </remarks>
public bool AspectRatioLocked
{
  get { return GraphicData.AspectRatioLocked; }
  set { GraphicData.AspectRatioLocked = value; }
}

Aspose.Words for .NET Resources

The following resources will help you work with Aspose.Words for .NET:

 


To keep up with our news, you can follow us on Twitter or follow our Facebook page.

Leave a Reply