06.19.08

Gemini version available ♊︎

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 in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

Decor ᶃ Gemini Space

Below is a Web proxy. We recommend getting a Gemini client/browser.

Black/white/grey bullet button This post is also available in Gemini over at this address (requires a Gemini client/browser to open).

Decor ✐ Cross-references

Black/white/grey bullet button Pages that cross-reference this one, if any exist, are listed below or will be listed below over time.

Decor ▢ Respond and Discuss

Black/white/grey bullet button If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

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.

DecorWhat Else is New


  1. Microsoft Thought Police

    Reprinted with permission from Ryan



  2. Links 08/02/2023: GNOME Smoother Scrolling of Text Views

    Links for the day



  3. Links 08/02/2023: Transmission 4.0.0 Released and Mass Layoffs at Zoom

    Links for the day



  4. IRC Proceedings: Tuesday, February 07, 2023

    IRC logs for Tuesday, February 07, 2023



  5. When the Pension Vanishes

    Today we commenced a multi-part mini-series about pensions and what happens when they suddenly vanish and nobody is willing to explain where all the money went



  6. Sirius 'Open Source' Pensiongate: An Introduction

    The Sirius ‘Open Source’ series continues in the form of a mini-series about pensions; it’s part of an ongoing investigation of a deep mystery that impacts people who left the company quite a long time ago and some of the lessons herein are applicable to any worker with a pension (at times of financial uncertainties)



  7. Links 07/02/2023: Endless OS 5.0 and Voice.AI GPL Violations

    Links for the day



  8. No Doubt Microsoft Unleashed Another 'Tay', Spreading Bigotry Under the Guise of Hey Hi (AI)

    Reprinted with permission from Ryan



  9. Links 07/02/2023: Fedora 39 Development Plans Outlines

    Links for the day



  10. IRC Proceedings: Monday, February 06, 2023

    IRC logs for Monday, February 06, 2023



  11. Links 06/02/2023: Escuelas Linux 8.0 and Many Political Issues

    Links for the day



  12. Links 06/02/2023: Sparky 6.6 and IPFire 2.27 – Core Update 173

    Links for the day



  13. Taking Back Control or Seizing Autonomy Over the News Cycle (Informing People, Culling the Marketing)





  14. Reality Versus Fiction: EPO Insiders Versus EPO Web Site and UPC 'Churnalists'

    The "official" sources of the European Patent Office (EPO), as well as the sedated "media" that the EPO is bribing for further bias, cannot tell the truth about this very large institution; for proper examination of Europe's largest patent office one must pursue the interpretation by longtime veterans and insiders, who are increasingly upset and abused (they're being pressured to grant patents in violation of the charter of the EPO)



  15. Links 06/02/2023: Linux 6.2 RC7 and Fatal Earthquake

    Links for the day



  16. IRC Proceedings: Sunday, February 05, 2023

    IRC logs for Sunday, February 05, 2023



  17. Links 05/02/2023: Wayland in Bookworm and xvidtune 1.0.4

    Links for the day



  18. Links 05/02/2023: Pakistan Blocks Wikipedia, Musharraf Dies

    Links for the day



  19. IRC Proceedings: Saturday, February 04, 2023

    IRC logs for Saturday, February 04, 2023



  20. Links 04/02/2023: FOSDEM Happening and Ken Thompson in SoCal Linux Expo

    Links for the day



  21. 2023 is the Year Taxpayers' Money Goes to War and Energy Subsidies, Not Tech

    Now that a lot of powerful and omnipresent ‘tech’ (spying and policing) companies are rotting away we have golden opportunities to bring about positive change and maybe even recruit technical people for good causes



  22. Getting Back to Productive Computer Systems Would Benefit Public Health and Not Just Boost Productivity

    “Smartphoneshame” (shaming an unhealthy culture of obsession with “apps”) would potentially bring about a better, more sociable society with fewer mental health crises and higher productivity levels



  23. Links 04/02/2023: This Week in KDE and Many More Tech Layoffs

    Links for the day



  24. Dotcom Boom and Bust, Round 2

    The age of technology giants/monopolies devouring everything or military-funded (i.e. taxpayers-subsidised) surveillance/censorship tentacles, in effect privatised eyes of the state, may be ending; the United States can barely sustain that anymore and raising the debt ceiling won't solve that (buying time isn't the solution)



  25. Society Would Benefit From a Smartphoneshame Movement

    In a society plagued by blackmail, surveillance and frivolous lawsuits it is important to reconsider the notion of “smart” phone ownership; these devices give potentially authoritarian companies and governments far too much power over people (in the EU they want to introduce new legislation that would, in effect, ban Free software if it enables true privacy)



  26. IRC Proceedings: Friday, February 03, 2023

    IRC logs for Friday, February 03, 2023



  27. IRC Proceedings: Thursday, February 02, 2023

    IRC logs for Thursday, February 02, 2023



  28. Links 03/02/2023: Proton 7.0-6 Released, ScummVM 2.7 Testing

    Links for the day



  29. Links 03/02/2023: OpenSSH 9.2 and OBS Studio 29.0.1

    Links for the day



  30. Links 03/02/2023: GNU C Library 2.37

    Links for the day


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

Recent Posts