Microsoft is "working hard" to enable Lion-specific features in Office, according to a post on the Office for Mac blog.
Yes, we are working hard with Apple to enable versioning, auto save, and full-screen for Office for Mac 2011. I know your next question will be “when?”, and unfortunately I can’t answer that – but it’s likely measured in months not days – just to set expectations.
Pat Fox, the author of the post, also reminds users that Office for Mac 2004 will never work under Lion, because it is a PowerPC application and Apple has dropped support for PPC apps with the end of Rosetta support.
Also, Microsoft has fixed a nasty bug in Microsoft Communicator that caused a crash whenever an instant message was sent. It promises that update in the "next day or so."
Top Rated Comments
I know it's hip to 'dis Microsoft around here, but Office:mac is the reason I can have a PC-free household. The Mac BU is a good group of people that don't get enough credit for the work they do, IMO.
So I give Microsoft credit in this case: at least they’re not waiting for the next big paid version, nor playing “wait and see.” I wonder how Adobe’s handling these features....
(And there’s a difference between a compatibility/fix update, which should get the maximum rush, vs. a feature update. It sounds like Office is already compatible with Lion, but if there are serious bugs, I’d expect them squashed sooner than “months.”)
How do we know that work on these features isn’t partly done, and has long since been in progress? Yes, it’s amazing to think that changing one part of a software program could impact other parts, and that it could take months and months. But that is in fact the case sometimes. Is it the case here, or is the Mac BU just being slow and not caring? The latter might be true, I won’t deny--but I don’t think we have the evidence to accuse them yet.
P.S. I’m not biased: I use OpenOffice :)
I don't know why people bash the OSX division of microsoft so much. 2011 is a great product, easier to use than 2010 and a huge improvement over 2008.
Also, if you've read any of the developer documentation you would know that this is a pretty substantial change to an extremely critical part of their product that will require a lot of work and even more testing given how extremely critical the process of saving is.
I know with certainty that Fullscreen isn't hard to implement now, in fact, that's the whole point of OS-wide support. Same with versions and autosave.
Completely unrelated, but I just found this picture of steve jobs from the recent keynote at moscone west:
How sweet.