Author Archives: Romank

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

Lots of customers have been waiting to get their hands on Aspose.Words that does not lose DrawingML and Structured Document Tags (SDT, content controls) when processing DOCX documents.

Finally, it is here. The release page with full details is here http://www.aspose.com/community/files/51/.net-components/aspose.words-for-.net/entry258045.aspx

I can only add that in this release you can only expect DrawingML and SDT to be preserved during DOCX open/save and also during document assembly (copying nodes between documents, joining documents together etc). You will be able to see … Continue Reading

In my previous post about our autoporting project I told that we achieved compile and started running unit tests on our internal Aspose.Foundation library.

Today I am happy to tell that our completely autoported Java code is now able to generate PDF and XPS documents. The documents generated by the Java version pass the same verification, compliance and rasterization tests as the ones generated by our .NET product.

The number of unit tests that pass today in Aspose.Foundation is 76% … Continue Reading

Aspose.Words for .NET 9.4. is our next release that is likely to be available early next week.

Another great feature that I can confirm is making into this release is support for Structured Document Tags (Content Controls) in your OOXML documents.

Earlier versions of Aspose.Words would just lose Content Controls if you open/save a DOCX document.

The upcoming version fully preserves Content Controls in your documents during DOCX open/save operations.

There will be a new public class StructuredDocumentTag (derives from … Continue Reading

Compiles okay = 72.1% (up only 0.4%) from last week.

Does not compile = 27.8%

Although the increase in the number of Aspose.Words autoportable C# to Java source files is rather small this week, we have great news.

Aspose.Words internally consists of two libraries/modules: Aspose.Foundation and Aspose.Words. Aspose.Foundation contains a lot of “common” code such as utility classes, platform abstraction layer, structured storage module, zip library, true type fonts module, rendering (the Aspose Paper Specification), parsing and rendering of metafiles, PDF and … Continue Reading

In my earlier post http://www.aspose.com/community/blogs/aspose.words-product-family/archive/2010/08/12/when-conversion-to-pdf-in-aspose-words-for-java-will-be-fully-available.aspx I offered to post regular updates on our internal progress towards releasing a fully up-to-date (with field update, Table of Contents, footnotes etc) Word to PDF conversion in Aspose.Words for Java.

Here is an update for this week.

Compiles okay = 71.7% (up 1.7% from 70% last week)

Does not compile = 28.2%

While from this numbers you could estimate there are about 16 weeks to go to get to 100%, I think we are going to deliver much sooner. … Continue Reading

When rendering documents to PDF and XPS formats, Aspose.Words currently supports the following fonts:

• TrueType Fonts
• TrueType Font Collections
• OpenType fonts with TrueType outlines

A number of customers have reported problems that Aspose.Words cannot render some of their documents to PDF and fails with errors like “cannot find the ‘loca’ table” or changes a font to Times New Roman or to MS Sans Serif.

We have traced many of these errors to a single problem – these documents use OpenType … Continue Reading