Group items tagged

In this interview with Microsoft's Chris Capossela, he admits that OOXML is not an interoperable format - that using OOXML will result in a loss of productivity.   excerpt: "The collaboration experience end users are going to have with Office 2010 and the Web applications in the browser and Office on the phone is far superior to anything out there, whether it's from Google or anybody else. And the increase in costs to do what they're suggesting and the decrease in productivity that's going to result is something that customers will see, and then they'll choose Microsoft. The best example of that is just sharing a document. Just taking an Office document that was built in the rich client that has a piece of smart art and a watermark or a header or a footer, and then when I share that with you and you open it in the Office Web app, it looks absolutely identical to what I created. When you make edits to it and save it and I open it back up, I see exactly the edits you made and all the stuff I had in there originally. If you do that exact same thing with Google or Zoho or OpenOffice, you lose stuff. And that means loss of productivity."

Good stuff!  Be sure to watch the YouTube video.  There is a demo of how a Google Docs and MSWord collaborative document gets synchronized.  Notice the layout mismatch.  They do however seem to understand the problems of the advanced formatting common to compound documents and "in-process" workgroup documents. excerpt:  OffiSync is launching an all-new version of its Microsoft Office to Google Docs synchronization tool, a plugin that's a "must-have" for anyone still straddling the two worlds of office suites: that is, the desktop-based world of Microsoft software and the web-based world of Google Docs. In the updated version of OffiSync, set to arrive minutes from now, you'll be able to co-author documents in real-time between Microsoft Office and Google Docs, no matter what version of the Office software you use. There are a few other new features too, including improvements to search, added Google Sites support and the ability to store any file type, but it's the co-authoring feature that's today's biggest reveal.

With Office 2010 already available to corporations, documents you can't quite open in Office 2007 are soon to appear in your inbox. If you're not upgrading, or never use Office anyways, TextMaker Viewer is a light, snappy document viewing option. TextMaker Viewer actually opens a huge range of word processing files, including Office, OpenOffice.org, the TextMaker app this viewer derives from, and all the standard low-tech formats like HTML, TXT, and RTF. Microsoft offers its own viewers, but only the PowerPoint Viewer has made it up to 2010 compatibility so far. Beyond that, TextMaker is a very lightweight application, so opening huge files likely won't choke up your system as thoroughly. TextMaker Viewer 2010 is a free download for Windows systems only. There does seem to be an issue with registering the free version to turn off the "nag" screen on launching, but after a few starts, a checkbox to hide that screen does appear.

Another good article form Michael Hickins, this time linking the success of Google Wave to the success of Microsoft OOXML. Rob Weir jumps in to defend , well, i'm not sure. I did however respond. Excerpt: Developers hoping to hitch a ride on Google's Wave have discovered that Microsoft may have unwittingly helped them resolve the single greatest problem they needed to overcome in order to challenge the dominance of Office. When Microsoft set out to create Office 2007 using a brand new code base - Office Open XML (OOXML) - it needed to accomplish two goals: make it compatible with all previous versions of Office, and have it accepted as a standard file format for productivity tools so that governments could continue using it while complying with rules forcing them to use standards-based software. ..... Depending on your perspective, either Microsoft has sowed the seeds of its own undoing, or international standards bodies succeeded in forcing Microsoft to open itself up. Either way, Microsoft has given away the key to compatibility with Office documents, allowing all comers to overcome the one barrier that has heretofore prevented customers from dumping Microsoft's Office suite.

Content controls are bounded and potentially labeled regions in a document that serve as containers for specific types of content. Individual content controls can contain content such as dates, lists, or paragraphs of formatted text. In some cases, content controls might remind you of forms. However, they are much more powerful, flexible, and useful because they enable you to create rich, structured blocks of content. Content controls also build on the custom XML support introduced in Microsoft Office Word 2003. Content controls enable you to author templates that insert well-defined blocks into your documents. Content controls enable you to: * Specify structured regions in a template. Each structured region has its own unique ID so that you can read from and write to it. Examples of types of structured regions (or content controls) are combo boxes, pictures, text blocks, and calendars. * Determine the behavior of content controls. Each content control takes up a portion of a document and, as the template author, you can specify what each region does. For example, if you want a region of your template to be a calendar, you insert a calendar content control in that area of the document, which automatically determines what that block of content does. Similarly, if you want a section of a template to display an image, create a picture content control in that area. In this way, you can build a template with predefined block types. * Restrict the content of content controls. Each content control can be restricted, so that it cannot be deleted or edited. This is useful if, for example, you have copyright information in a template that the user should be able to read but not edit. You can also lock a template's content so that a user does not accidentally delete portions of it. This makes templates more robust than in previous versions. * Map the contents of a content control to data in a custom XML part that is stored with the document. For example, if you i

wikiWORD and SPoint get the go ahead!