Yearly Archives: 2006

Class Design: Which is the Best?

Posted on September 7, 2006 by DmitryV

What class design do you prefer? I assume most of you follow Microsoft guidelines, and it’s reasonable. However, practice shows that not all the recommendations should be blindly obeyed. I don’t imply here fundamental rules like “never make instance fields public” (yet this also might be broken in some rare cases – imagine you have an internal class representing a low-level data structure with several hundred fields!). I’m rather speaking of naming conventions, order of members, and some other stuff related … Continue Reading

Posted in Dmitry Vorobyev |

A Bit More About Nemerle and Functions

Posted on September 7, 2006 by DmitryV

After posting my first impression about Nemerle I noticed that I had been criticized by some community members for my superficial knowledge of the language and related concepts. I like constructive criticism and I do accept it; so I’m thankful to those guys for pointing me to that.

However, I’d like to note I didn’t try to pose as an expert. I only expressed my current understanding of the language and I advisedly highlighted that in the post. So I … Continue Reading

Posted in Dmitry Vorobyev |

AWesome!

Posted on September 6, 2006 by DmitryV

So we have almost finished another major release of Aspose.Words. We’re happy to note how greatly the component evolves and improves despite it’s still pretty young by the standards of software industry. It’s less than 3 years old but it’s already the subject to imitate

Among other cool features, two highly requested formats have been added to the component’s arsenal, Rich Text Format (RTF) and WordprocessingML (WordML). One of the areas I’m responsible for is RTF export (will start working on import … Continue Reading

Posted in Dmitry Vorobyev |

Going Transitional (exporting to XHTML)

Posted on September 5, 2006 by Romank

A number of customers asked for Aspose.Words to produce XHTML compliant HTML when exporting and I’m happy to tell you that we did it.

Aspose.Words used to output some unclosed tags, for example <meta …> that were okay from HTML point of view, but precluded customers from using those as XML files.

Starting from Aspose.Words 4.0, we always output well-formed XML when exporting to HTML format. It is the main point that we addressed. We also validate almost all produced test … Continue Reading

Posted in Roman Korchagin |

Happy Import of HTML Tables and CSS Length Units

Posted on September 5, 2006 by Romank

There’s been a public outcry for Aspose.Words inability to import CSS length units other than points. A related issue was about Aspose.Words throwing exceptions when encountering HTML that it cannot recognize. Yet another popular support issue was about HTML tables, that when imported, had cell and table widths quite different from the original.

We are happy to announce all of these issues were addressed in Aspose.Words 4.0.

All CSS length units (except em and ex at this stage) are now supported. … Continue Reading

Posted in Roman Korchagin |

Pretty Format HTML, RTF and WordML Output

Posted on September 5, 2006 by Romank

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.

Posted in Roman Korchagin |

Aspose.Words for .NET 1.0, 1.1 and 2.0, How it Works

Posted on September 5, 2006 by Romank

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.

Posted in Roman Korchagin |