Category Archive: Aspose.Words Product Family

Yes, parent/child (nested mail merge regions) is one of those highly demanded features that is available in Aspose.Words for .NET and not yet available in Aspose.Words for Java. And yes, this feature is going to be available for Java very soon, when our autoporting project is complete.

BTW, there are only 16 files remain to be made autoportable.

Today a small technical article that describes challenges and solutions we came across when making the Aspose.Words MailMerge autoportable to Java.

Overview

Did you know you can use use XPath queries to find nodes in the Aspose.Words document tree?

Here is the API topic with some code examples http://www.aspose.com/documentation/.net-components/aspose.words-for-.net/aspose.words.compositenode.selectnodes.html

On the surface it looks like a pretty cool feature. Aspose.Words loads a document (a document in almost any wordprocessing format) into a tree-like model in memory. The model resembles OOXML, but is more “refined’ meaning you don’t have to deal with relationships to other parts and other raw stuff. Then you can … Continue Reading

If you are not sure what we are talking about, here is the previous post in this series.

Today’s Aspose.Words for Java stats are:

• Total source files 2533
• 42 files have autoporting problems
• All other files – we automatically convert them from C# to Java using our porting tool.

What’s next:

1. We are going to sort out the remaining 42 files in the next week or so. There is basically one major porting problem now – use of ADO.NET class … Continue Reading

Here is a screenshot of the new feature we have. You can now convert any Word document to SWF. The produced SWF embeds a little viewer that displays the document.

For the full list of features find the Aspose.Words for .NET 9.5 release page in the downloads section.

 … Continue Reading

DrawingML is used to represent the rich shapes, colors, diagrams and charts in OOXML documents.

I am happy to tell that we have a big project underway to make sure Aspose.Words can render all DrawingML into its fixed-page outputs including PDF, XPS, graphics and printing.

At the moment Aspose.Words can only preserve DrawingML during DOCX open/save cycles and not much else. Aspose.Words can render DrawingML pictures, but cannot render other DrawingML shapes.

We will be releasing DrawingML functionality in iterations, every … Continue Reading

It’s been only five days since my previous report, but I cannot wait to say what a great progress we had.

Today’s Aspose.Words for Java stats are:

• Total source files 2413
• Only 214 have autoporting problems = 8.8%
• The rest 2199 of the C# source files are totally automatically convertable to Java.

In these five days we managed to review and make portable 311 files. Almost all document conversions modules are now portable. With all of the other supported formats, we are finally going … Continue Reading

Today’s stats are:

• Total source files 2413
• 1888 compiles on Java okay = 78.2%
• 525 has autoporting problems = 21.7%

Comparing to the previous report we have made 47 C# files autoportable. That’s 8% of the previous 572 files still to fix. This allows to make some estimates. If we keep this pace, then we need about 12 weeks more to make all files compile in Java. That’s only all compile. We will need time to get all unit tests going, … Continue Reading