Linked by Thom Holwerda on Thu 27th Sep 2007 07:55 UTC, submitted by Augusto
Novell and Ximian "Two months ago, the Brazilian Linux community gathered around BR-Linux invited Novell to answer 10 questions sent and selected by the users, about the company's stance on Linux, open source, licenses, document formats and other subjects." "Novell has been very consistent on this issue and we have publicly stated that we do not believe that Linux infringes on any Microsoft patents. That being said, our agreement with Microsoft takes the patent issue off the table for customers. We have simply made the patent issue a non-event as part of a customer buying decision."
Permalink for comment 274821
To read all comments associated with this story, please click here.
RE[5]: A good interview
by segedunum on Thu 27th Sep 2007 16:30 UTC in reply to "RE[4]: A good interview"
segedunum
Member since:
2005-07-06

Others are easily fixable (typos) or revisable (eliminating VML from the next version of the spec).

If Office 2007 produces documents with VML in it (as a result of legacy Office documents being opened and saved) then on a practical level, this is absolutely meaningless.

Regardless of whether you allow KParts or Bonobo or anything else, you still need a viewer for that embedded element and the document wouldn't work on the alternate platform anyway. The same is true of ODF or any other format which allows embedding data and rendering instructions from outside apps.

The difference is that ODF references standards that have largely been implemented elsewhere in the open source world, such as SVG. Anyone implementing OOXML will need to recreate large amounts of technology that only runs on Windows.

This doesn't make an actual difference for interoperability, because one would only presume docs to be interoperable if they stay within the standard and are produced solely by the standardized implementation...

Errrrr, right, yer. Take a look at what Office 2007 produces:

http://www.codeproject.com/cs/library/office2007bin.asp

What was that about interoperability again?

Do you have something specific here from these comments, or is there some set of specific complaints that you think will make OOXML unimplementable by outsiders?

I would suggest some serious reading before asking that question, because it has been done to death.

(Incidentally, check out Jody Goldberg's post on dealing with SpreadsheetML for Gnumeric:

Have you seen how utterly basic that example file is? People have macros, charts, formulas etc. etc. in the real world. Jody also tells us this:

"Brianís example of Numbers reading an OOX file written by Gnumeric could just as easily been an XLS file.....In contrast XLSX may be ugly, but itíís concepts were very familiar from XLS. We already had much of the code required to handle it."

So in order to handle a naively simple spreadsheet file, they already largely had what they needed to implement it having mucked about with XLS for several years? Well that's just brilliant, and not exactly a ringing endorsement for OOXML.

I would advise reading Stephane Rodriguez's comments in that article for a fuller picture.

Reply Parent Score: 4