Yearly Archives: 2005

There’ve been several requests from the customers for Aspose.Word to support processing of Word documents with embedded true type fonts. I’ve looked into the issue and there are actually two feature requests around embedded fonts:

1. Be able to embed fonts in Word documents.
2. Be able to process (open, modify and save) Word documents with embedded fonts already there.

It looks like True Type fonts are embedded in Word files using some Agfa MicroType Express compression technology. Apparently this compression technology … Continue Reading

Not sure about the exact date, but it should be around now. Here are some statistics to entertain you on our birthday (I hope I’m not giving away too much trade secrets):

• We’ve been working non-stop for 2 years, too many hours to count.
• Aspose.Word source code is getting close to 100K lines.
• The number of classes is around 600.
• There are only 4 classes bigger than 1,000 lines of code. The biggest class is around 1,200 lines of

This question is a brain teaser for me at the moment. Maybe it is easy for you, let me know. Still I hope it could be interesting for you because it is directly from Aspose.Word source code.

I have a “package” that contains classes of the document model, let’s call it Model and “packages” that are responsible for reading or writing the Model in a specific format, for example DocWriter, PdfWriter, HtmlWriter, HtmlReader and so on. I call them packages (UML packages) because … Continue Reading

After about 15 years of programming I begin to stumble on some basic object-oriented concepts and I can’t sleep well because I can’t find a reasonable answer.

Here is the question I’m dealing with now:

When to use an instance field versus a local variable (and pass it as a parameter) if two or more methods in a class need to share that data?

For example, MyClass has a public method called ReadTheThing and “the thing“ has a header and a body. I … Continue Reading

Our initial plans were to develop an API that is similar, if not compatible with Microsoft Word Object Model so any solution that utilizes Microsoft Word Automation could be easily migrated to Aspose.Word and the learning curve for developers who a familiar with MS Word Automation will be short. That was the original plan going back almost 2 years ago when we started working on Aspose.Word and we were exposing classes with interfaces that looked like the ones you would … Continue Reading