EditorsAbout the SiteComes vs. MicrosoftUsing This Web SiteSite ArchivesCredibility IndexOOXMLOpenDocumentPatentsNovellNews DigestSite NewsRSS

06.19.08

Microsoft Office Says ODF Files Are Corrupt

Posted in Formats, FUD, Office Suites, Open XML, OpenDocument, Standard at 10:33 am by Dr. Roy Schestowitz

Steve Ballmer on ODFShades of DR-DOS FUD tactics

One day ago we wrote about ways in which Microsoft seems to be discouraging the use of ODF. It’s a must-read for background. We promised some screenshots and we finally have them thanks to Eruaran. Here is the portion of the IRC discussion which explains what you see at the bottom.

<Eruaran> The first one is what comes up if you try to open an .odt in MS Word 2007 (after I clicked ‘details’)
<schestowitz> Thanks!
<Eruaran> no problem
<Eruaran> so, you click ok and you get the second one
<schestowitz> And the third…?
<Eruaran> so, you click ‘yes’ to ‘recover the contents’ of this document and you get the third
<Eruaran> third shows after I clicked ‘details’
<Eruaran> click ‘ok’ and thats it
<schestowitz> “the file is corrupt,” eh? The last time I checked it’s Microsoft that corrupted Swedish folks for OOXML.
<Eruaran> try to open the same document back in OOo or KOffice and its perfect

[...]

<Eruaran> “Microsoft Office cannot open this file because some parts are missing or invalid” ~translation~ “Microsoft Office could open this file but wont because some parts are missing (you know, those binary blobs that keep you dependant upon us), so we’ve decided your choice of file formats is invalid”.

Dialogue 1:

ODF diagloe

Dialogue 2: (click to enlarge)

ODF error

Dialogue 3:

ODF FUD

Thoughts?

Share this post: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Reddit
  • co.mments
  • DZone
  • email
  • Google Bookmarks
  • LinkedIn
  • NewsVine
  • Print
  • Technorati
  • TwitThis
  • Facebook

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

12 Comments

  1. Shane Coyle said,

    June 19, 2008 at 12:50 pm

    Gravatar

    It looks like they fed Word an ODT file, but implied (or word assumed) that it was OOXML – Dialogue 3 says it’s a malformed OOXML file, which it likely is. It’s also likely a malformed mpeg file, if you try to feed it to mplayer as such.

    What ODF plugin is being used here? Word doesn’t support ODF natively, yet, right?

    When you had the open file dialog, what filter for file type was applied, or was it all files? Then, did it ask you to choose a file type because this format was unrecognized, or did it just assume it was OOXML?

    I know MS said that ODF support was coming, fulfilling the last of Stafford Masie’s prophecies, but it’s not here yet that I noticed – something about a service pack, I don’t use Office so I dunno. We’ll also have to wait and see on how well it is implemented, I suppose.

  2. Stephane Rodriguez said,

    June 19, 2008 at 3:39 pm

    Gravatar

    The dialog boxes show that Word 2007 tries to open a Word 2007 file, and does not find the parts it expects. This is not conclusive, other than the fact that Word 2007 does not support .ODT natively.

    Is that worth a blog post? Who said Word 2007 natively supports .ODT ?

  3. Roy Schestowitz said,

    June 19, 2008 at 3:50 pm

    Gravatar

    The reader expressed his concerns about the textual contents of the dialogue/message.

    I’m not sure if you read the previous post. We show here only the fairly intimidating dialugues that discourage ODF use or at least introduce doubt (even for future use). We also mentioned how this relates to the fiasco around DR-DOS in this IRC Chat (full logs posted this morning)

    A reader wrote to tell me about another example a couple of hours ago (E-mail):


    In regards to this one ( or another on the same topic )
    http://boycottnovell.com/2008/06/19/microsoft-mso-mocks-odf/

    I’ve noticed, second hand, that MSIE gives a ‘security’ warning when accessing Gmail.


    See those ‘smoking gun’ from DR-DDS again. This may not be deliberate this time around, but it does not help, either.

  4. Roy Bixler said,

    June 19, 2008 at 3:56 pm

    Gravatar

    You could say that the error message is deceptive because MSO is interpreting a format that it does not support as if it does support it. That would certainly confuse someone who is not technically savvy or who is unaware of ODF and that it is a distinct format from OOXML. It’s not as if ODF was unknown when MSO 2007 was released. At best, I would say that Microsoft was negligent and made a bad assumption that every XML file must be an OOXML file. More likely is that, given Microsoft’s history, they would regard it as “not a problem” or even desirable if their error message caused confusion, all while giving them plausible deniability.

  5. Victor Soliz said,

    June 19, 2008 at 5:34 pm

    Gravatar

    It looks to me that they are just assuming any “unknown” (to them) XML file is OOXML that needs to be repaired, well the way to prove would be to feed it a random XML file and see what happens. I hope some of the readers actually have office 2007…

  6. Roy Schestowitz said,

    June 19, 2008 at 5:37 pm

    Gravatar

    I hope some of the readers actually have office 2007…

    I’m not sure about the word “hope”. :-)

    Either way, about half of the visitors of this Web site use GNU/Linux.

  7. Victor Soliz said,

    June 19, 2008 at 6:28 pm

    Gravatar

    Well, they could try WINE, wonder if anyone would actually bother try to run THAT.

  8. Roy Schestowitz said,

    June 19, 2008 at 6:51 pm

    Gravatar

    It’s possible. Wine Reviews showed it some months ago.

  9. Eruaran said,

    June 19, 2008 at 8:44 pm

    Gravatar

    @ Shane Coyle

    “It looks like they fed Word an ODT file” – Yes I did.

    “but implied (or word assumed) that it was OOXML” – Microsoft knows what an ODT is. Word could simply report that the format is unsupported, but it doesn’t do that.

    “Dialogue 3 says it’s a malformed OOXML file, which it likely is.” – It was a simple text document that was not malformed at all. This supports my point – Microsoft’s dialogues have made an impression on you.

    “It’s also likely a malformed mpeg file” – I don’t know why you think that.

    No ODF plugin was used. Office assumes it is OOXML.

    You can also choose “recover text from any file”, and Word will spit out some revealing information: It correctly identifies the document type as an OASIS open document, it can output all of the meta data, it knows what version it is, but it absolutely will not at any time output the single line of text that the document contained.

    The purpose of this exercise was simply to show that Office will give the user information that is misleading in response to a perfectly good ODT file. It is easy enough to replicate.

  10. Eruaran said,

    June 19, 2008 at 9:01 pm

    Gravatar

    @ Stephane Rodriguez

    The purpose is to show that Microsoft Word is deliberately misleading.

    This is what Word will give you if you try to “recover text from any file”:

    mimetypeapplication/vnd.oasis.opendocument.textPK
    Configurations2/statusbar/PK
    Configurations2/accelerator/current.xml
    Configurations2/floater/PK
    Configurations2/popupmenu/PK
    Configurations2/progressbar/PK
    Configurations2/menubar/PK
    Configurations2/toolbar/PK
    Configurations2/images/Bitmaps/PK
    content.xml½–MoÛ0
    7Uz{oª±V`[Oô
    8i“#xyt4
    h
    styles.xmlÍZ[oÛ6
    D[\%R )_úëw
    ;˜±ÂÈ{"K×ã-[æP:Ut?V
    >èœl$IdQR
    ;(
    5S£]C
    =‹ªÞmGgÄn;àš$£jtnXæ
    RAm+Ã!ÉqÒ­tFS¹’ _3C
    UÁÜØH‡HóÏ€4^”Æ®åTl+º…%&ìB”+a
    SYé¬ÃòŒ2±•²°›å,Ì wi[K…U)
    M
    9Øjk_ñ^
    :yB
    OpenOffice.org/2.4$Win32 OpenOffice.org_project/680m12$Build-9286Agent Smith2008-06-20T11:32:54Agent Smith2008-06-20T11:33:141PT25SPK
    Thumbnails/thumbnail.pngë
    &+KV]i
    /ÝÙó´lþõyÇvÍÿ\5ãrfÌúã…ök’uNGðï~k ÷¹Tâùñs;ìïçÙÚÊ/8n=ßn]muŒ
    settings.xmlµYQWâ:
    -d*R-ÁbP-
    7ÞBë¤U¯/—ËÓåù)Êy½yuuU•o7C
    Y>k^6.
    qÂéoGy2d H
    g
    &__WtÜ‚ñ>íÈIEà’ _?*
    N]¥¡Ï£¹ ðŽ5&CTÑGn*
    -
    P5o¶æk-MQEM]
    META-INF/manifest.xmlµ•KjÃ0
    ‘Ú@,ƒ
    ¥Ð`žú(UŠq:bÎbqW
    *긓ý½_PrSõ4I7
    Z
    bþK|0H³c-2
    mimetypePK
    Configurations2/statusbar/PK
    Configurations2/accelerator/current.xmlPK
    Configurations2/floater/PK
    Configurations2/popupmenu/PK
    Configurations2/progressbar/PK
    Configurations2/menubar/PK
    Configurations2/toolbar/PK
    Configurations2/images/Bitmaps/PK
    content.xmlPK
    styles.xmlPK
    meta.xmlPK
    Thumbnails/thumbnail.pngPK
    settings.xmlPK
    META-INF/manifest.xmlPK

  11. Eruaran said,

    June 19, 2008 at 9:08 pm

    Gravatar

    Actually not all the info displayed correctly when I submitted it… but meh, you get the idea…

  12. Jose_X said,

    August 12, 2008 at 4:04 pm

    Gravatar

    >> The dialog boxes show that Word 2007 tries to open a Word 2007 file, and does not find the parts it expects. This is not conclusive, other than the fact that Word 2007 does not support .ODT natively.

    These diagrams seem to indicate Word doesn’t support ODF yet, but consider the following.

    That is the problem with a monopoly. When most businesses and users use a specific product, the vendor calls the shots. What the user sees is “an illegal …blah blah….” They know next time if they want to “preserve” their work to use Monopolyware and not take chances with other products. This is FUD that helps keep the monopoly together to be leveraged another day.

    The user also eventually will recognize the .odt ending and avoid it like the plague.. so much that those advocating it will have another hurdle to overcome to get their legitimate message across or sell their product.

    [Hypothetical] Without a monopoly, it would be much clearer to many users that this product was badly designed in assuming OOXML formatting and in not adequately supporting ODF by this time. Rather than to hold the monopoly fort, in such a hypothetical case, this product would rightly lose marketshare. Thus, even this “innocent” error interaction serves to strengthen the monopoly, and few would claim Monopolysoft was playing dirty. Most would attribute this to incompetency, sloppiness, negligence… point is, all of these natural human failings help support the monopoly automatically.

    Better formats and products get marginalized severely as long as you have a monopoly. It pressures vendors of new products and those contemplating format changes to do so on the monopolist’s terms and timeline. This defeats major advantages of innovators.

    And who can outmarket a Monopolysoft backed by its cashcows and controlled marketing venues (your *desktop* and the many partners kept in line through fear and NDA secrecy).

    Monopolysoft has numerous interlocking monopolies not just one.

    [IMO] Monopolysoft will fight ODF by helping to create the appearances of ODF products and documents that “don’t work”. This is a major facet of what they mean by “supporting” ODF today but “OOXML is the future”. They will partake in the poisoning of the ODF well until they have “fixed” ISO OOXML and changed their software to “match” it.

What Else is New


  1. Links 30/10/2014: GNOME 3.15.1, Red Hat Software Collections 1.2

    Links for the day



  2. Links 29/10/2014: Ubuntu Touch Tablet, Puppy Linux 6.0

    Links for the day



  3. Links 28/10/2014: SUSE Linux Enterprise 12, Canonical OpenStack Distro

    Links for the day



  4. Links 28/10/2014: PiFxOS, The Document Foundation in OSBA

    Links for the day



  5. Microsoft is Bricking Devices With Linux (Yet Again!), So a Microsoft Booster Spins/Paints Linux Devices as 'Fakes'

    Microsoft delivers rogue drivers through Windows Update and they brick Arduino microcontrollers



  6. How Bill Gates Continues to Pass Wealth From the Public to His Own Bank Account

    Having put a universal tax on many things (not just computers) and evaded tax using the classic 'charity' trick, Gates is now buying the media, the schools, politicians etc. and earns as much as 10 billion dollars per year while the public is taught that Gates is a giver, not a hoarder of the worst kind



  7. Links 27/10/2014: Lenovo Unbundling, Linux 3.18 RC2

    Links for the day



  8. IRC Proceedings: September 14th, 2014 – October 25th, 2014

    Many IRC logs



  9. Links 25/10/2014: KDE Mockups, Update on GNOME Outreach Program for Women

    Links for the day



  10. After Infecting Unity -- Successfully -- Microsoft's Partner Xamarin Wants to Infect Unreal Engine With .NET

    Xamarin continues to spread dependence on Microsoft to more gaming frameworks, not just platforms such as GNU/Linux, Android, and even permanent-state devices



  11. Taking Microsoft Windows Off the Grid for Damage to Businesses, the Internet, and Banking Systems

    Microsoft's insecure-by-design software is causing massive damages ([cref 27802 possibly trillions] of [cref 13992 dollars in damages to date]) and yet the corporate press does not ask the right questions, let alone suggest a ban on Microsoft software



  12. City of Berlin Does Not Abandon Free Software, It's Only Tax Authorities

    A Softpedia report that says the City of Berlin is moving to Microsoft Office is flawed and may be based on a poor translation



  13. Nadella a Liar in Chief at Microsoft, Pretending That His Anti-Competitive Practices Are Unfortunately Imposed on Microsoft

    The nastiness of Microsoft knows no bounds as even its assault on GNU/Linux and dirty tricks against Free software adoption are characterised as the fault of 'pirates'



  14. Reuters Writes About the Demise of Software Patents, But Focuses on 'Trolls' and Quotes Lawyers

    How the corporate media chooses to cover the invalidity of many software patents and the effect of that



  15. Links 24/10/2014: Microsoft Tax Axed in Italy, Google's Linux (ChromeOS/Android) Leader Promoted

    Links for the day



  16. Links 24/10/2014: GNU/Linux History, Fedora Delay

    Links for the day



  17. Links 23/10/2014: New *buntu, Benchmarks

    Links for the day



  18. Links 22/10/2014: Chromebooks Surge, NSA Android Endorsement

    Links for the day



  19. Links 21/10/2014: Debian Fork Debate, New GNU IceCat

    Links for the day



  20. Criminal Microsoft is Censoring the Web and Breaks Laws to Do So; the Web Should Censor (Remove) Microsoft

    Microsoft is still breaking the Internet using completely bogus takedown requests (an abuse of DMCA) and why Microsoft Windows, which contains weaponised back doors (shared with the NSA), should be banned from the Internet, not just from the Web



  21. Microsoft 'Loving' GNU/Linux and Other Corporate Media Fiction

    Microsoft has bullied or cleverly bribed enough technology-centric media sites to have them characterise Microsoft as a friend of Free/Open Source software (FOSS) that also "loves Linux"



  22. India May be Taking Bill Gates to Court for Misusing His So-called 'Charity' to Conduct Clinical Trials Without Consent on Behalf of Companies He Invests in

    Bill Gates may finally be pulled into the courtroom again, having been identified for large-scale abuses that he commits in the name of profit (not "charity")



  23. The Problems With Legal Workarounds, Patent Scope, and Expansion of Patent Trolls to the East

    Patent trolls are in the news again and it's rather important, albeit for various different reasons, more relevant than the ones covered here in the past



  24. Links 20/10/2014: Cloudera and Red Hat, Debian 7.7, and Vivid Vervet

    Links for the day



  25. Links 20/10/2014: 10 Years Since First Ubuntu Release

    Links for the day



  26. How Patent Lawyers Analyze Alice v. CLS Bank

    Breaking down a patent lawyer's analysis of a Supreme Court's decision that seemingly invalidated hundreds of thousands of software patents



  27. Is It Google's Turn to Head the USPTO Corporation?

    The industry-led USPTO continues to be coordinated by some of its biggest clients, despite issues associated with conflicting interests



  28. The EPO's Public Relations Disaster Amid Distrust From Within (and EPO Communications Chief Leaves): Part VII

    Amid unrest and suspicion of misconduct in the EPO's management (ongoing for months if not years), Transparency International steps in, but the EPO's management completely ignores Transparency International, refusing to collaborate; the PR chief of the EPO is apparently being pushed out in the mean time



  29. Links 18/10/2014: Debian Plans for Init Systems, Tails 1.2

    Links for the day



  30. Links 18/10/2014: New ELive, Android Expansion

    Links for the day


CoPilotCo

RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

CoPilotCo

Recent Posts