i cant think of anything else to say on this topic.

Maybe if they gave us something worth celebrating, people would be into it. Who wants to share media about an old app that runs poorly on current hardware and is missing half the productivity of the PC suite? Give us Mac Visio, Universal Binary versions and visual basic support and then we'll talk.

My first reaction was "Other than self-promotion freaks, who would waste their time on this?"

ill use a multitude of CS3 products maybe throw in some lightwave, take the finished image and import it into a word doc. like what a lot of people are doing on this site........

wha-la. there you go.

thanks M$ for being there, couldn't get this done with out your great package of office programs.

How about getting your Mac BU development asses into gear and produce a decent version of Office that is less buggy than every released version so far, instead of wasting time on inane projects like this before the actual '08 Office product ships.

Fix what's broke first a*******, then do the artsy / frivolous c*** latter. Jeez.

This is just another attempt to distract us from their incompetancy in producing an MS product on time and with few bugs. They just don't get it... or... maybe they do? Hmmm...

How are the Mac version of Office missing "half the productivity" of the PC version? I thought people really liked Word on the Mac.

This isnt just immature MS bashing is it?

You guys are whiners. First, I like this new file sharing site. It is a good idea even if it is Microsoft. Second, Office on Intel Macs runs just fine in Rosette. In some instance, depending on how old your Power PC machine is, it runs quite a bit faster. Third, Microsoft killed Visual Basic support on the Mac version of Office because it will likely kill it in the next version of Office for Windows as well. As such, it doesn't really make sense to include it in this version of Office, as it would have taken a lot of work. People forget that because of Apple's move to Intel, Microsoft had to pretty much go through every line of code in the old version of Office and change it. This is largely because it had to change from using Code Weaver to Apple's developer tools. Keep in mind it is hard changing tools you are accustomed to, and especially so when the tools you are changing to does not yet support all the same features.

Now with all that said, it is unacceptable that Microsoft has delayed providing Mac users with acceptable conversion tools for the new formats.

I'd have t agree with dahlbryn --if that's the kind of 'call to action' we can expect from the new 'leadership' of the MacBU, then we are bound to get entertained...