{"id":44,"date":"2006-12-05T23:06:00","date_gmt":"2006-12-06T04:06:00","guid":{"rendered":"http:\/\/2d823b65bb.nxcli.io\/2006\/12\/the-worm-in-the-apple.html"},"modified":"2010-01-16T10:20:26","modified_gmt":"2010-01-16T15:20:26","slug":"worm-in-apple","status":"publish","type":"post","link":"https:\/\/www.robweir.com\/blog\/2006\/12\/worm-in-apple.html","title":{"rendered":"The worm in the apple"},"content":{"rendered":"<p>Via <a href=\"http:\/\/crunchgear.com\/2006\/12\/05\/use-ms-office-on-a-mac-you%E2%80%99re-about-to-get-screwed\/\">CrunchGear<\/a>, <a href=\"http:\/\/www.macworld.co.uk\/procreative\/news\/index.cfm?newsid=16666&amp;pagtype=allchandate\">MacWorld UK<\/a>,  and <a href=\"http:\/\/apcmag.com\/node\/4755\">APC Magazine<\/a> &#8212; Mac Office users seem to have no way of reading the new OOXML files which Office 2007 for Windows writes by default.  APC quotes a Microsoft Mac Business Unit spokeperson as saying, &#8220;Unfortunately it is still to early for us to say when the converters will be available&#8221;.<\/p>\n<p>Whoops.<\/p>\n<p>As a public service I note two alternatives:  the <a href=\"http:\/\/porting.openoffice.org\/mac\/\">Mac port<\/a> in OpenOffice.org and  <a href=\"http:\/\/www.neooffice.org\/\">NeoOffice<\/a>.<\/p>\n<hr \/>\n<p>9 December 2006 Update:  Interesting analysis from from Andrew Shebanow over at <a href=\"http:\/\/blogs.adobe.com\/shebanation\/2006\/12\/open_xml_one-way.html\">Shebanation<\/a>:  How adding OOXML support to the Mac is likely 150 person-year effort.  And Mary Jo Foley&#8217;s <a href=\"http:\/\/blogs.zdnet.com\/microsoft\/?p=137\">Unblinking Eye<\/a> points out that the problem is not just with the Mac support.  Windows Mobile 5.0 will lack OOXML support until mid-2007.<\/p>\n<p>Is it just me, or does this seem like something less than a coordinated roll-out?  The clean, hassle-free way of doing this, with the least suffering for users and admins, would have been like this:  Ship Office 2007 with OOXML support, but not as the default.  Then over the next year get the rest of the Office ecosystem working with OOXML:  the Mac, Mobile, Sharepoint, Excel Live, etc.  Get all of the support out there, but don&#8217;t force it on people yet as a default.  When all the pieces are ready then, via a service pack or version upgrade, change the defaults.  Everything goes smoothly from there.<\/p>\n<p>The fact that they didn&#8217;t follow this roll-out model suggests that someone at Microsoft really, really, really wanted to get OOXML out fast, even if it wasn&#8217;t pretty.<\/p>\n<p>Luckily admins do have the ability to perform a more orderly roll-out in their organizations if they wish.  The default format for Office applications can be changed via a registry entry.  For example, for Excel the registry entry is:<\/p>\n<p>HKCU\\Software\\Microsoft\\Office\\12.0\\Excel\\Options\\DefaultFormat<\/p>\n<p>By default it isn&#8217;t there, but you can create an entry of type REG_DWORD and assign it the value of 56 (38 hexadecimal).  Once you&#8217;ve made that change, Excel documents will be saved in the legacy binary formats by default.  Similar registry settings for Word and PowerPoint are:<\/p>\n<p>HKCU\\Software\\Microsoft\\Office\\12.0\\Word\\Options\\DefaultFormat<\/p>\n<p>create REG_SZ with value of &#8220;Doc&#8221;<\/p>\n<p>and<\/p>\n<p>HKCU\\Software\\Microsoft\\Office\\12.0\\PowerPoint\\Options\\DefaultFormat<\/p>\n<p>create REG_DWORD with value of 0<\/p>\n<p>It should be trivial for someone with a Windows compiler to create a simple application to accomplish this same task.  Ideally it would also allow the default to be changed to any other format of the admin&#8217;s choice, including turning it back to OOXML if\/when admins desire to deploy that way, or changing it to ODF when a good Plugin is available.<\/p>\n<p>10 December 2006 Update:  My attention has been drawn to an <a rel=\"nofollow\" href=\"http:\/\/www.schwieb.com\/blog\/2006\/08\/08\/saying-goodbye-to-visual-basic\/\">earlier post<\/a> from a lead in Microsoft&#8217;s Mac Business Unit, where the removal of support for Visual Basic macros is discussed.  Damn, that&#8217;s cold.  Ever get the feeling you&#8217;ve been marked for extermination?<\/p>\n<p>17 May 2007 Update:  From News.com &#8220;<a href=\"http:\/\/news.com.com\/Microsoft+delays+Office+converters+for+Mac\/2100-1012_3-6183588.html?tag=nefd.top\">Microsoft delays Office convertors for Mac<\/a>&#8221; and some great follow-up analysis by Andrew Shebanow over at <a href=\"http:\/\/shebanation.com\/2007\/05\/16\/ooxml-and-the-mac-more-bad-news-from-microsoft\/\">Shebanation<\/a>.<\/p>\n<p>30 May 2007 Update:  More analysis and <a href=\"http:\/\/www.microsoft-watch.com\/content\/business_applications\/the_pointless_office_converter_delay.html?kc=MWRSS02129TX1K0000535\">commentary<\/a> on this ongoing issue from Joe Wilcox over at <a href=\"http:\/\/www.microsoft-watch.com\/\">Microsoft Watch<\/a>:<\/p>\n<blockquote><p>Meanwhile, Microsoft makes big noise about interoperability. What kind of example does Microsoft set when the formats for its Mac and Windows Office suites aren&#8217;t interoperable? Irreconcilable is the position of increased Microsoft-and-other platform interoperability and the decreased interoperability between Office file formats across two platforms.<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>Via CrunchGear, MacWorld UK, and APC Magazine &#8212; Mac Office users seem to have no way of reading the new OOXML files which Office 2007 for Windows writes by default. APC quotes a Microsoft Mac Business Unit spokeperson as saying, &#8220;Unfortunately it is still to early for us to say when the converters will be [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"categories":[6],"tags":[],"class_list":{"0":"post-44","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-ooxml","7":"entry"},"_links":{"self":[{"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/posts\/44","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/comments?post=44"}],"version-history":[{"count":4,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/posts\/44\/revisions"}],"predecessor-version":[{"id":287,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/posts\/44\/revisions\/287"}],"wp:attachment":[{"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/media?parent=44"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/categories?post=44"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/tags?post=44"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}