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 274898
To read all comments associated with this story, please click here.
RE[7]: A good interview
by segedunum on Thu 27th Sep 2007 19:48 UTC in reply to "RE[6]: A good interview"
Member since:

Have you seen Stephane Rodriguez's comments?? He's not exaclty an unbiased or particularly polite commenter. He goes around calling people "bitches."

I haven't seen him call anyone that, but I daresay that everyone calls somebody something at some point. I'd rather just focus on the content of what he's saying to be perfectly honest, rather than this idiotic name calling when people have nothing left to say.

What you've shown is that there are features in Office which do not fall under the purview of the OOXML standard. So what?

Because Office 2007 is the only test container anyone has for testing OOXML compliance, since Microsoft hasn't provided anything else.

If you want to interchange documents, then don't use those features.

Then you'll end up with practically nothing that you can implement, and nothing that you can work with from people sending you documents produced in Office 2007. No interoperability, in other words.

If you're writing an app which has special processing instructions (say, for instance AppleScript from iWork), you can include your stuff in the container as well without any problems.

Yer, and that can be done with ODF as well in the instances where you really need to do that. However, it kills interoperability because it depends on all the various applications being able to understand what is there.

Extensions like that have absolutely no place in a completely new format that Microsoft has come up with to supposedly open the innards of Office in the name of interoperability. It's a contradiction in terms. There's no reason for them to be there.

Can you explain why you think the BIN parts are a problem?

That should be obvious. Because no application apart from Office can feasibly do anything about them (we now have BIFF12. Yay!). The average cross section of Excel documents are an awful lot more complex than a couple of columns of numbers, and are full of embedded objects and macros. The workbook, styles and other parts are also BIN parts as opposed to XML parts as well.

Whichever way that you cut this, on a practical level interoperability is just a sad joke.

Edited 2007-09-27 19:55

Reply Parent Score: 4