Category Archive: Roman Korchagin

Did you know that in Aspose.Words 4.0 you can turn an option on to pretty format output to HTML, RTF and WordML files?

This could be very useful for you when looking at these files in a text editor trying to figure out what happens with certain document elements or formatting.

doc.SaveOptions.ExportPrettyFormat = true;
doc.Save(@”C:\MyFile.html”, SaveFormat.FormatHtml);
doc.Save(@”C:\MyFile.xml”, SaveFormat.FormatWordML);
doc.Save(@”C:\MyFile.rtf”, SaveFormat.FormatRtf);

The above code will produce human-readable documents with line breaks and indentation. This option is turned off by default.

 … Continue Reading

Before Aspose.Words 4.0 we worked in VS.NET 2003 and built Aspose.Words.dll for .NET Framework 1.1 only. It worked on the different .NET version as follows:

• .NET 1.0 – you had to add some entries in the application configuration file so Aspose.Words.dll targets .NET 1.0 runtime.
• .NET 1.1 – built for it.
• .NET 2.0 – worked, thanks to .NET forward compatibility (assemblies built for .NET 1.1 usually work fine in .NET 2.0). A few issues were reported, especially when running on 64-bit Windows.

We listened to you and now Aspose.Words is almost ready for a next big step forward in the Word document processing technology.

Important New Features

·         Full support for drawing objects and textboxes in documents.

·         New public API for drawing objects in the Aspose.Words.Drawing namespace.

·         High-Fidelity export to Rich Text Format 1.8 (RTF).

·         High-Fidelity export to WordprocessingML (WordML).

·         Export to XHTML 1.0 Transitional.

·         Improved HTML import.

·         … Continue Reading

I’ve recently seen a new component from a respectable vendor that copied a lot from what we invented and successfully used in the Aspose.Words mail merge engine.

The copying struck me because it was so exact and apparent. They borrowed the exact syntax for mail merge regions, mail merge events etc.

We don’t have anything against someome copying someone else’s API. In fact, I hope it is perfectly legal since Aspose.Words itself tries to be friendly and familiar to all .NET and MS Office developers by … Continue Reading

Anybody using bool Node.HasInnerText? Let me know if you are.

We are planning to extend the public API with auto shapes soon and we cannot go without critically looking at the existing API. The Node.HasInnerText property is just one of the few members that now seem like not adding much value to the API and we consider removing it.

Also, let us know (here or in the forums) if you have any questions or suggestions about the public API. Something you would … Continue Reading

Just two fixes in this release:

• Digital signature for VBA projects is lost.
• End of header/footer is out of sync exception.

I’m happy to announce we’ve extended the public API of Aspose.Words to include classes that allow you to fully control list formatting in your documents. This feature has been requested by many customers a long time ago, so we think its time.

Here is what you can do now (what we’ve been designing the API for):

• Create bulleted and numbered lists based on any of the Microsoft Word’s list templates (there is 21 template in Microsoft Word, they include bulleted,

New Features

This release brings Aspose.Words for Java codebase, features and fixes into sync with Aspose.Words for .NET 3.6.2. Previous (Aspose.Words for Java 1.0.2) codebase was corresponding to Aspose.Words for .NET 3.3. All fixes and new features that were made in Aspose.Words for .NET since 3.3 till 3.6.2 have been incorporated into this Aspose.Words for Java 1.0.3 release.

To summarize:

-was-

Aspose.Words for Java 1.0.2  == codebase == Aspose.Words for .NET 3.3

-now-

Aspose.Words for Java 1.0.3 == codebase == Aspose.Words for … Continue Reading