posted by Adam S on Mon 26th Sep 2005 20:31 UTC

"StarOffice 8, Page 2"

After the initial discussion, I had an oppotunity to ask a few questions. Please remember that the answers are all paraphrased.

OSNews: What are the OEM opportunties associated with StarOffice? Are you targetting the Dells and HPs of the industry?
Certainly, we are aiming for OEMs as well as existing commercial settings. So far, we've had much greater success in Europe, Japan, and other areas of Asia than in the USA. We are currently looking into the so-called "whitebox" space.

OSNews: What about OpenDocument is more compelling than StarOffice 6 and 7's SXW formats which were also XML based?
The main plus is compliance. As seen in Massachusettes, across Europe, and in many other areas, standards are becoming more important. Previously, the StarOffice file format was authored and controlled by Sun. With OpenDocument, there is no one vendor that controls its destiny.

OSNews: Can OpenDocument do anything than StarOffice files can't, or vice versa?
No. Certainly, the formats are virtually interchangeable. StarOffice 8 can read and write StarOffice 7 files, and a plugin that is either forthcoming or already released will allow StarOffice 7 to write OpenDocument files. The conversion from one to the other is largely trivial, but goes a long way to satisfying the goal of application independence.

OSNews: Does Sun see the popularity of as a threat to its own StarOffice business?
No, is not a threat, but rather a nice complement. Some want, some prefer pure open source software, some want a productivity suite and simply don't want to pay for it. Others want support, additional features, and the conversion compatibility improvements that StarOffice offers. We recognize that there is a market for both. We also believe that users are likely to prefer StarOffice at work.

OSNews: Many free software supports are upset that parts of OO.o depend on Java, which is not currently considered "free software" by the current definition. Has Sun spent anytime addressing this, or is extracting Java dependence - a Sun technology, I'd note - not considered a priority?
Certainly, today, StarOffice requires a JRE to function properly. I know Sun has taken steps to make Java more open source friendly. But somebody on the team with specific knowledge about Java plans would have to address that more specifically.

OSNews: One of the largest complaints about StarOffice/OO.o is the load time. Recent articles have suggested that without kernel level access, there is only "so much" that can be done to improve load time? Is this true? If not, what is StarOffice doing to improve load time, and is it any different that what we currently see with
StarOffice load time should not be much different than what you currently see with 2. Load time will continue to improve, however, and has with each successive version of StarOffice. There will likely be 3-4 or more updates to StarOffice 8 over the course of its lifetime, and during that span, we expect to see load time continue to improve.

OSNews: Why is not able to ship alongside StarOffice 8? Will it contain features, bug fixes, or stability enhancements not found in StarOffice?
The 2 release is based on a schedule set forth by the community. The Sun release process is different, but you will see no major differences from one product to another in those regards. The OOCon conference is this week. I would expect to see some announcement there about a release date for 2.

OSNews: Do you believe that the OASIS format will eventually be adopted by Microsoft, if only in the form of a custom filter? And if not, will StarOffice be able to eventually support Microsoft's "Office 12" XML, whose XSDs were recently published?
Of course, I can only speculate on this point, but I would suspect that Microsoft will eventually have to support OASIS, if only in an import/export fashion. The world market has already dictated that there will be a migration towards standards.
StarOffice will eventually read/write Office 12. It's way too early to really discuss this in detail, to be fair. We know that new products take about 2 years to really permeate the landscape, and "Office 12" is still well over a year away. When the formats are finalized, StarOffice will support them - the first specs are out and we've already seen them. However, right now, we're most concerned with best supporting existing documents through Microsoft Office 2003.

OSNews: Thanks for your time!
Thank you.

Table of contents
  1. "StarOffice 8, Page 1"
  2. "StarOffice 8, Page 2"
e p (0)    37 Comment(s)

Technology White Papers

See More