"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."
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-01-02
Have you seen Stephane Rodriguez's comments?? He's not exaclty an unbiased or particularly polite commenter. He goes around calling people "bitches."
What you've shown is that there are features in Office which do not fall under the purview of the OOXML standard. So what? If you want to interchange documents, then don't use those features. 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. Can you explain why you think the BIN parts are a problem?
Member since:2005-07-06
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
"This is my NeXTstation Turbo Color booting the Mac System 7.1 Operating System using a hardware add-on called 'Daydream'. The Daydream has a Mac ROM and a few custom ICs in it and hooked up to the NeXTs DSP port. Turns your NeXT into a full fledged 68k powered Mac." So cool.
"The NetBSD Project is pleased to announce NetBSD 6.1, the first feature update of the NetBSD 6 release branch. It represents a selected subset of fixes deemed important for security or stability reasons, as well as new features and enhancements. Please note that all fixes in the prior security/bugfix updates (NetBSD 6.0.1 and 6.0.2) are also in 6.1."
"At the end of a week in which Electronic Arts confirmed it wasn't developing a thing for the Wii U, one of the software engineers in EA Sports' Canada studio, in a series of since-deleted tweets, disparaged the console as 'crap' and suggested Nintendo should give up on hardware altogether. 'The Wii U is crap. Less powerful than an Xbox 360. Poor online/store. Weird tablet', tweeted Bob Summerwill, listed as a senior software engineer at EA Canada, in a reply to a tweet posting a link about EA's no-Wii U news. 'Nintendo are walking dead at this point'." The Wii U is turning into the 21st century's Virtual Boy.
"In NixOS, the entire operating system - the kernel, applications, system packages, configuration files, and so on - is built by the Nix package manager from a description in a purely functional build language. The fact that it's purely functional essentially means that building a new configuration cannot overwrite previous configurations. Most of the other features follow from this." Interesting approach. A Linux distribution, sure, but with some very refreshing ideas about system configuration.
Appfour added, among other features, C/C++ support to its new version of AIDE. From Android-IDE, "Now you can write parts of your app or your whole app in C/C++ on your device. AIDE supports the Standard Android NDK toolchain (GCC 4.6 + Bionic, STL, ...). No changes are necessary if you want to build an app developed on a PC with Eclipse. C/C++ development is fully integrated: Build errors appear in the error list and files can easily be navigated to with Go to file. The editor supports C/C++ syntax highlighting."
Ars nails it: "The answer is that Google did announce what amounts to a fairly substantial Android update yesterday. They simply did it without adding to the update fragmentation problems that continue to plague the platform. By focusing on these changes and not the apparently-waiting-in-the-wings update to the core software, Google is showing us one of the ways in which it's trying to fix the update problem."
"It is good for programmers to understand what goes on inside a processor. The CPU is at the heart of our career. What goes on inside the CPU? How long does it take for one instruction to run? What does it mean when a new CPU has a 12-stage pipeline, or 18-stage pipeline, or even a 'deep' 31-stage pipeline? Programs generally treat the CPU as a black box. Instructions go into the box in order, instructions come out of the box in order, and some processing magic happens inside. As a programmer, it is useful to learn what happens inside the box. This is especially true if you will be working on tasks like program optimization. If you don't know what is going on inside the CPU, how can you optimize for it? This article is about what goes on inside the x86 processor's deep pipeline."
"It was the only moment I heard regret slip into Otellini's voice during the several hours of conversations I had with him. 'The lesson I took away from that was, while we like to speak with data around here, so many times in my career I've ended up making decisions with my gut, and I should have followed my gut,' he said. 'My gut told me to say yes.'" The world would've been a much different place - Apple would have been less dependant on Samsung for its chips, which probably would've meant less money for Samsung to develop its Galaxy business.Glass is getting some love at Google I/O as well. New applications have been released - Facebook, Twitter, Evernote, Elle, Tumblr, and CNN. Perhaps more interesting: the newly announced Google Glass Developer Kit will allow offline applications and direct hardware access - great for hacking and expanding Glass' potential. This kit will really allow hackers to put Glass through its paces."But Beck and Merrill decided that simply banning toxic players wasn't an acceptable solution for their game. Riot Games began experimenting with more constructive modes of player management through a formal player behavior initiative that actually conducts controlled experiments on its player base to see what helps reduce bad behavior. The results of that initiative have been shared at a lecture at the Massachusetts Institute of Technology and on panels at the Penny Arcade Expo East and the Game Developers Conference." Absolutely fascinating stuff. I'm a League of Legends player, and to be honest, the community isn't nearly as bad as some make it out to be. I'm happy Riot games has the guts to employ science to address the issue.
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.