Category Archive: Aspose.Words Product Family

In the previous post we celebrated all unit tests passed for a completely autoportable Aspose.Foundation (or internal library).

Now we are back to making the remainder of Aspose.Words C# source autoportable.

I used to treat the actual number of classes in Aspose.Words as confidential and disclosed the progress as percentage only e.g. 73% done. But I just remembered that anyone can easily count the number of classes in any .NET assembly in ildasm or Reflector so I don’t think it makes sense … Continue Reading

Just yesterday we had only 86% unit tests passing in our internal Aspose.Foundation for Java library. Today I am happy to say it is 100% green.

Just to remind you we are trying to make Aspose.Words for Java by automatically converting Aspose.Words for .NET written in C# to Java using our own tool.

Aspose.Foundation is an internal library, a part of Aspose.Words. We first achieved compile on the generated Java source code on 27th August. We then spent this month getting all unit … Continue Reading

Just uploaded a video about how we are automatically converting tons of Aspose.Words C# code to Java in matter of seconds.

Every developer working in C# can straight away test his new feature or a fix works in Java in exactly the same way like in .NET.

See http://www.aspose.com/community/files/51/.net-components/aspose.words-for-.net/entry260350.aspx

 … Continue Reading

In my previous post I delivered no good news about when Aspose.Words for Java with PDF rendering will be avaialble.

I want to correct the situation today.

We are still working on making sure that all unit tests pass for Aspose.Foundation (our internal library that contains the PDF and XPS renderers, platform independent graphics, imaging, font utilities etc).

Currently Aspose.Foundation, the autoported to Java version happily produces PDF and XPS output that matches our .NET product output very very closely.

The … Continue Reading

It’s been a bit more than a week since I posted the last “weekly progress”.

Today’s news is that because me (the project tracker) was busy attending for the Aspose.Words for .NET 9.4 release and also reviewing and integrating new features onto our trunk (I posted about these) – there is no measurable progress on the Autoporting to Java project to report today.

This is not to say there was no progress done on the Java project. We have been reviewing … Continue Reading

Microsoft Word allows specifying different paper trays in a document for each section, for the first and all further pages of each section.

We have corresponding Aspose.Words.PaperTray enum, which is used by the Section.PageSetup.FirstPageTray and OtherPagesTray properties. The PaperTray enum has values like AutomaticSheetFeed, LargeFormatBin, ManualFeed and so on.

We thought we had it working! We thought we tested printing a document using Aspose.Words will take paper from the correct trays as specified in the document. Our AsposeWordsPrintDocument class that … Continue Reading

You can use Aspose.Words for .NET to easily convert any document to EPUB.

Document doc = new Document(@"E:\MyDoc26.doc");
doc.Save(@"E:\MyDoc26.epub");

Then upload this document to your iPod, iPhone or iPad. I have Apple iBooks installed on mine and it can display EPUB documents pretty well.

Simple Test

Here is a sample I used to check non-English characters and images are displayed alright. I am holding iPod with the document I generated using Aspose.Words against the backdrop of the original document opened … Continue Reading

If yes, let us know. Please let us know how do you want to use the generated XAML and any other requirements about it.

Current XAML support in Aspose.Words is like this:

1. Fixed Page. Internal (not visible in the public API) export of each page of the document into fixed page XAML format. Aspose.Words reuses its own XPS output engine for this. We are not quite sure how you would want to use individual XAML pages hence not made … Continue Reading