Category Archive: Aspose.Words Product Family

Please welcome our new product Aspose.Words for Reporting Services!

Aspose.Words for Reporting Services is the only solution on the market that makes possible generating true DOC, RTF and WordprocessingML reports in Microsoft SQL Server 2005 Reporting Services. All RDL report features, including tables, matrices, charts and images are converted with the highest degree of precision to Microsoft Word documents.

Aspose.Words for Reporting Services works as a rendering extension for Microsoft SQL Server 2005 Reporting Services.

To download: http://www.aspose.com/Downloads/Aspose.Words.Reporting.Services/Default.aspx

The zip … Continue Reading

This is a maintenance release. Here is what’s been fixed:

• 1539 Load image from same URL only once when importing HTML.
• 1537 Document looks not correct when exported to DOC.
• 1534 Support PageBorderArt in import and export WordML.
• 1533 ‘Unknown line style’ exception when converting from DOC to WordML.
• 1527 Add support for loading images from different URIs.
• 1526 Document throws “Unable to read beyond the end of the stream” on saving.
• 1525 Document throws “Cannot get field part because at

Crystal Reports have long been able to produce reports in RTF format (giving them the .DOC extension by default which always created confusion).

Using Aspose.Words you can quickly and easily convert from RTF to real DOC. Either on the server or on the client.

The code to convert any RTF to DOC is as simple as this:

Aspose.Words.Document doc = new Document("C:\\MyFolder\\MyFile.rtf");
doc.Save("C:\\MyFolder\\MyFile.doc");

Conversions in any direction between Microsoft Word formats (DOC, RTF and WordML) in Aspose.Words are high-fidelity (very … Continue Reading

What to do if you need to remove bookmark and its entire content from the document altogether. The only method existing in API for that is setting Bookmark.Text to an empty string. But that will work only for the simplest of bookmarks. For bookmark spanning multiple nodes with mixed content, like paragraph, tables, it will fail with a dreaded “Start and end node should have the same grand parent” exception. It will also fail when bookmark spans several sections and … Continue Reading

There is a known issue of loss of formatting when setting form field text input value using Result property or SetTextInputValue method. For example, you have formatted your text form field as bold and it comes up as normal text when updated. For a workaround you can use the following wrapper method instead of using SetTextInputValue method directly:

Example

[C#]

private void SetFormFieldText(FormField formField, object value)
{
        if ((value == null) || (value is string) && ((string)value == “”))
        {
                

This releases introduces a great new feature – WordprocessingML import in Aspose.Words.

Now, the following formats are well supported in Aspose.Words for .NET:

• Open and save DOC – Microsoft Word 97 – 2007 Document
• Open and save RTF – Rich Text Format
• Open and save XML – WordprocessingML
• Open and save HTML/XHTML
• Save TXT
• Save PDF (when used with Aspose.Pdf)

New Features

• Import WordprocessingML documents.
• Updated demos to include WordprocessingML.
• Updated Aspose.Words Documentation.
• Made it possible to specify a password

Check out the new main page for the Aspose.Words Documentation!

This consolidated documentation now includes:

• Aspose.Words Getting Started

• Aspose.Words Programmer’s Guide

• Aspose.Words for .NET API Reference

• Aspose.Words for Java Reference

We have improved the process by which we develop and build documentation that means better documentation for you.

Getting Started and Programmer’s Guide used to live in Aspose.Wiki which did not have an easy to navigate tree. It was also quite difficult for us to write documentation in Wiki … Continue Reading

Please download the latest Aspose.Words 4.1.1 if you want to assess the result of the optimizations applied to RTF import within almost two weeks after release.

Let me boast a bit. Let’s take our old fellow for the testing: a document named Microsoft Office Word 2003 Rich Text Format (RTF) Specification converted to the format it describes, RTF. Why we commonly use it for testing our import/export modules is because it’s well balanced for that purpose: it’s large enough (~8 Mb RTF); … Continue Reading

This maintenance release includes a number of useful fixes: