Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
United Kingdom Microsoft

UK Forces Microsoft To Adopt Open Document Standards 178

First time accepted submitter Barsteward writes Microsoft has confirmed it will start supporting the Open Documents Format (ODF) in the next update to Office 365, following a lengthy battle against the UK government. In 2014, Microsoft went against the government's request to support ODF, claiming its own XML format was more heavily adopted. The UK government refutes the claim, stating that ODF allows users to not be boxed into one ecosystem.
This discussion has been archived. No new comments can be posted.

UK Forces Microsoft To Adopt Open Document Standards

Comments Filter:
  • My God! (Score:5, Funny)

    by serviscope_minor ( 664417 ) on Thursday April 02, 2015 @02:17AM (#49389943) Journal

    Who are you and what have you done with the UK government?

    They were (a) right, (b) stuck to their guns and (c) have a technical solution which didn't simply involve shovelling heaps of money at microsoft in exchange for a brutal lock in. Very out of character, not that I'm complaining!

    • Re:My God! (Score:5, Funny)

      by Darinbob ( 1142669 ) on Thursday April 02, 2015 @03:11AM (#49390047)

      I also seem to recall that Microsoft caving in to a government was one of the signs of the apocalypse.

      • Re:My God! (Score:4, Informative)

        by jklovanc ( 1603149 ) on Thursday April 02, 2015 @04:14AM (#49390183)

        Microsoft has caved many times. Remember the browser wars and unbundling IE?

        • Last time I looked, IE was still "an integral part of Windows".

          • Re: (Score:2, Interesting)

            by jones_supa ( 887896 )

            Yes, last time when you looked in 1998.

            Now you only have to do Control Panel -> Uninstall a program -> Turn Windows features on or off -> [ ] Internet Explorer.

            It asks to reboot, and at the same time IE is nuked from the orbit.

            There is no proof that IE would be needed for any kind of operating system functionality anymore.

            • Re: (Score:3, Informative)

              by Anonymous Coward

              It is still there.

              Only the top level "application" got removed. The actual application is in the DLLs that are still on disk.

              Windows won't run if you actually did delete it.

              • I hear that every time when the issue comes up, but no one still has undisputably proven what those DLLs are and what applications actually need them.
              • Precisely. My definition of "unbundling" doesn't extend to "turn off". If it's TRULY unbundled, the application isn't installed AT ALL.

                • What shouldn't be installed? The actual application (which isn't very big) or the HTML rendering engine? Having the latter is (a) very useful, and (b) a huge part of the former.

                  • The point of unbundling Internet Explorer was to allow fair competition. That is, Microsoft's position as a monopoly with the OS should not give an adantage to IE or a disadvantage to other browsers. Thre are other applications that use Microsoft's HTML and rendering DLLs that can't use alternative Chrome or Mozilla DLLs for example. So there's still a built in prejudice, as Microsoft completely controls the rendering and parsing of any HTML used by those other applications; there's still no incentive to

                • Should you uninstall all dlls that explorer uses? What about the C runtime?
                  • by haruchai ( 17472 )

                    Yes and the kernel & NTFS driver.
                    And then install Linux. Permanent solution to the IE problem. :-)

                    Except for those people still stuck on IE6-dependent apps.

          • That's a semantic argument. There are applications that depend on the libraries used by IE in order to render HTML. But nothing about Windows requires IE be your web browser. Most OSes have a built-in HTML rendering library these days.

            To put it another way, a built-in library to render HTML from within applications would not have killed Netscape.

            • But the built in library discourages the creation of more portable HTML web pages which ultimately harms alternative browsers. You're still stuck in a world where things appear to work better with IE because sites are written that only work with Microsoft's quirks, or sites that use ActiveX, etc.

              • I don't follow. How would a built-in HTML library have taken away from Netscape as a standalone web browser? I could see it taking away from some theoretical Netscape libraries meant for application development, but if such a product existed it was not very prevalent.

                Or are you saying that competing web browsers were using the IE libraries? That may have been the case, but my recollection of the time was that everyone was using home-grown code.

          • There are also special editions of Windows for the EU that do not include Windows Media Player. There are a dozen versions for the Windows installation media for the different target countries.

            People often forget how complicated being big can get when dealing globally.

    • Re:My God! (Score:5, Interesting)

      by dominux ( 731134 ) on Thursday April 02, 2015 @04:25AM (#49390207) Homepage

      it is a result of quite a few years of lobbying by organisations such as Open Forum Europe and internal pressure from certain folk within the civil service. The government is reasonably receptive to well made arguments. They have a big love-hate thing going on with Microsoft. They know they are being screwed over by an American company that doesn't pay it's full share of UK taxes, so they like to kick back a bit now and then.

      • by dcw3 ( 649211 )

        So, would they do this if MS were a British company? To my knowledge the U.S. hasn't done anything like that to a British company, with maybe the exception of BP after they blackened the Gulf of Mexico.

        And just for the record, MS can die in a fire for all I care.

        • Yes, they probably would. And as for BP, they're a publically-traded multinational company, and were in a commercial relationship with various US companies for the operations in the Gulf of Mexico. The guys most responsible for the leak were US companies, but your media loved the narrative of punishing bad foreigners....
      • by mvdwege ( 243851 )

        The other possibility is of course that Microsoft was very much in bed with the Blair government, so in the good old UK tradition of "do the exact opposite of the other guys" the Cameron government is deciding to put the thumbscrews to 'em.

    • Re:My God! (Score:4, Interesting)

      by petermgreen ( 876956 ) <plugwash@p[ ]ink.net ['10l' in gap]> on Thursday April 02, 2015 @08:47AM (#49391085) Homepage

      IMO File formats are not the real problem. Microsoft's binary word processor and spreadsheet formats were reverse engineered years ago and have been pretty stable since 2000. OOXML is XML based and even has some documentation available on how to read it.

      The real problem is that office documents blur the line between input and output and this makes them fundamentally fragile. An office document is input to a layout (in the case of a word processor) or calculation (in the case of a spreadsheet) engine but the user always looks at the output of that engine. Especially with word processors since the user is always looking at the output they aren't thinking about the structure of the input, they just bash things arround (holding down the space bar or enter key for example or dragging boxes around with no idea if their position is text-relative or page-relative)

      So I don't think this will solve anything, even if MS implements ODF and even if the UK government gets it's employees to start using it as their main format for storing files (good luck) I would expect loading a document from office into libreoffice to still have similar results to today. The input (text typed, pictures included, user-specified values in spreadsheet cells) will probablly carry across fine but in some cases it will result in noticably different output (different and possiblly unreadable layout for word processed documents, different rounding of results for spreadsheets). Especially for large badly structure docuements.

      • by Rob Y. ( 110975 )

        That might be true, but MS-specific interpretations of ODF's XML should be a lot easier to reverse-engineer than the weird, undocumentable junk that's supported by DOCX. ODF was designed to be open and implemented by multiple products, DOCX was designed to be implementable correctly only by MSWord.

  • Cue ... (Score:5, Interesting)

    by Anonymous Coward on Thursday April 02, 2015 @02:20AM (#49389951)

    10% effort into actually implementing this, and
    90% effort into examination how to creatively misunderstand OPF, extend ODF with "open" binary extensions, denigrate users of ODF, or just plain break ODF

    Or maybe it's 1% vs 99%, I don't know.

    • And limit the implementation to specific UK release versions that cost more than ordinary versions.

    • by gsslay ( 807818 )

      The cynic in me suspects this might just be Microsoft's next step. Implement OPF capability, but make it so awkward to use, with such poor results, that users avoid it.

    • by Bonzoli ( 932939 )
      Expect it to screw all on screen formatting for the rest of its existence. Loading it vs making it look correct are 2 different things.
    • 10% effort into actually implementing this, and
      90% effort into examination how to creatively misunderstand OPF, extend ODF with "open" binary extensions, denigrate users of ODF, or just plain break ODF

      Or maybe it's 1% vs 99%, I don't know.

      Knowing Microsoft, it will be 0% and 100%.

    • Aren't they trying to get users to use Office365 now, though? Subscriptoin based service and all that? So maybe interoperability with file formats is now to their benefit, just as making things like OneDrive or Outlook.com work better on multiple mobile device OSes.
  • by hcs_$reboot ( 1536101 ) on Thursday April 02, 2015 @02:22AM (#49389953)
    Seriously, the only reason I'm obliged to use MS Office is when a company sends a Word (xl...) doc that uses some features that Libre/Open Office don't support (well, or at all). That's basically any of the "comfort" feature. I'm lucky there is a version of MS Office for the Mac, but unfortunately it is badly supported and there are compatibility issues (the MS folks did a fork of MSOffice to develop the Mac version independently of the Windows version. That's severely retarded, but we've got no choice).
    If only ODF could be adopted everywhere...
    • by Anonymous Coward

      Ditch the Mac, use Windows and buy Office like all the normal people.

      Why are you troubling the people at Microsoft with the self-imposed problems you have created for yourself just because you are trying to be "different"?

      You decided to be "different" and but you keep depending on others to fix your problems now that things have gone south. At what point are you going to be a positive member contributing back to society instead of siphoning resources away from the productive members of soci

    • Re:That makes sense (Score:5, Informative)

      by ledow ( 319597 ) on Thursday April 02, 2015 @04:28AM (#49390211) Homepage

      Have you seen OOXML?

      The reason they had to fork is because the format is SO binary and tied into the old legacy codebase that - even masquerading behind an XML front - there's no illusion of portability whatsoever.

      They were forced to document it, by the EU, and all they did was describe every hack, binary fudge and kludge that went into it so that it was almost impossible to make a compatible format.

      When you're talking Office on Mac, it's not a question of just adding Mac UI code and incorporating another platform into the build process. It's replicating all those stupid bit-wise assumptions made throughout the format. It's like WMF used to be - literally just a description of the Windows GDI commands required to replicate the object on the screen (which is why WMFs were capable of containing executable code!). That's pretty much the best analogue to something like MS's "open" XML formats.

      I'm not surprised that the Mac versions are staggered by several years and not entirely compatible. That's how long it takes to emulate the Windows-specific fudges in the format.

      What MS are scared of is a format that works across all platforms because, then, what's to say you'll bother to buy Office?

      • What MS are scared of is a format that works across all platforms because, then, what's to say you'll bother to buy Office?

        Definitely. I bless the day it's gotta happen.

  • by Burz ( 138833 ) on Thursday April 02, 2015 @02:28AM (#49389959) Homepage Journal

    And that makes them hostile to open software in my book. They insist on treating Linux-formatted disks as essentially blank and have Windows tell the user the volume must be formatted to be used; fixing this would be simple in the extreme and would not even require an ability to read an Ext* volume. They stonewall AV formats like Vorbis when they could be added easily to existing apps. Really, the list goes on. The place where they have capitulated is formats that are intrinsic to the web (while parading their proprietary stuff as "open" hoping enough people will take the bait).

    MS still promotes lock-in. And from what I gather even their new .NET licensing terms are designed to leave you on the hook. [slashdot.org]

    • by cmurf ( 2833651 ) on Thursday April 02, 2015 @03:17AM (#49390063)
      If the partition type is set to Linux, Windows won't offer to format it. Problem is the common parted tool wrongly uses the Microsoft partition type GUID, thinking it was a generic "basic data" type rather than a Microsoft specific one. Windows assumes such partitions aren't properly formatted if it can't read them. Patches took forever to be merged upstream and another forever for downstream distros to use. It's still being done wrong today. OS X will only ignore unrecognized partition type codes on disks containing recognized ones. Otherwise it too actively encourages the user to format, of course resulting in data loss.
      • This is interesting to me, I've never heard this. Are you saying that parted, as in the Linux partitioning tool, uses the Microsoft partition type GUID incorrectly... and that is what Windows is reading, and thus sees it as not being formatted correctly?

        • by cmurf ( 2833651 )
          Correct. This [gnu.org] is the commit that fixes the problem. The patch actually goes back farther than it was merged, and then after merge it was two years until another stable release that had it appeared. And still many distros use a version of parted that predates this patch including RHEL 7 and openSUSE 13.2. The only distro I know off hand that uses the correct GUID is Fedora.

          I don't know why it took so long. My soapbox version is I think there's a history of partition types being unreliable and pointless be
    • by gweihir ( 88907 )

      The difference is that MS believes the purpose of "software" is to extract your money and give it to them. Any value they give back is pure coincidence or the minimum that cannot be avoided. On the other hand, FOSS projects believe that software is there to solve problems and to help people and making money is just an unavoidable and to be minimized side-task.

    • by ljw1004 ( 764174 ) on Thursday April 02, 2015 @06:36AM (#49390471)

      And from what I gather even their new .NET licensing terms are designed to leave you on the hook. [slashdot.org]

      Chinese whispers...

      (1) Microsoft adopts MIT license for .NET, a perfectly standard OSS license. Many people leave it at this, but MS additionally makes a "patent promise".

      (2) Blog site reads the patent promise, notes that for most use of the .NET OSS you're covered by the patent promise, but there's apparently one particular case (where you write your own alternative .NET runtime/fx that's incomplete) that doesn't appear to be covered by the patent promise.

      (3) Slashdot summary makes the leap to say that MS is "undecided about suing" users of its OSS.

      (4) Burz makes the leap to say that this is actually "designed to leave you on the hook".

      There are quite a few unjustified leaps in there. Burz, I wonder if you'd say the same about all OSS software that's licensed under MIT or BSD but which lacks a patent promise? Because such software would be in an even weaker state from your perspective than Microsoft's OSS .NET.

      (disclaimer: I do work for Microsoft, and I did generate some patents for them, and I'm an engineer not a lawyer).

    • I doubt it is trivial to add EXT2/3/4 support to the windows stack. Consider that ZFS has barely moved in linux space, even though it is fully BSD compatible, opensource, and awesome. Apparently it makes more sense to develop BTRFS.
      • by Burz ( 138833 )

        I doubt it is trivial to add EXT2/3/4 support to the windows stack. Consider that ZFS has barely moved in linux space, even though it is fully BSD compatible, opensource, and awesome. Apparently it makes more sense to develop BTRFS.

        Its trivial to get Windows to recognize a Linux partition and refrain from telling people to format those volumes.

      • ZFS has a terrible license that was intentionally designed to be incompatible with GPL. So don't expect integration nor even good support, especially out of the box. People at zfsonlinux are trying hard, but without much success. And all of that could be avoided if the sole copyright holder (Oracle) decided to relicense.

    • That's is the one thing I have always despised about working with MS products. I hope the new leadership is as open as they appear to be. If not, the saga will continue and I don't think they will survive it much longer.

  • Lotus (Score:5, Insightful)

    by cmurf ( 2833651 ) on Thursday April 02, 2015 @03:23AM (#49390071)
    Microsoft remembers how they took over Lotus' market share for spreadsheets. Lotus had no obscurity with their file format. Excel could read and write it perfectly. Open formats means the product must be as good or better for the price or users can jump ship. Closed formats are a buffer for mistakes or resting on laurels.
    • by niks42 ( 768188 )
      Excel succeeded because it worked better in Windows than Lotus 1-2-3.

      It worked better because Windows (286, 386, 3.1) Graphical Device Interface was designed for Excel, and other programs couldn't get the same performance out of Windows that Excel could.
      • Re:Lotus (Score:5, Informative)

        by Dr_Barnowl ( 709838 ) on Thursday April 02, 2015 @04:59AM (#49390293)

        Excel also succeeded because it had no format lock-in. Because it could WRITE Lotus 1-2-3 just as well as it read it, there was no risk to using Excel and finding that it didn't perform as well as Lotus.

        Lotus was the incumbent at the time. 1-2-3 was the killer app that drove adoption of the PC. Yes, Excel worked in pretty graphics mode. Yes, Excel was better than 1-2-3. But you've seen management clinging like limpets to older solutions to things just because of their elevated perception of risk. If Excel hadn't been able to read 1-2-3 files perfectly, it would never have happened.

        It's exactly the same reason why people won't migrate from MS Office to LibreOffice - because it's not entirely compatible, and everyone else uses it. It's all but impossible to make an entirely compatible program though - because even the MOO-XML formats are just a serialization of binary structs and even *puke* Windows API calls. Office isn't a standalone program - it only works on Windows.

    • Closed formats are a buffer for mistakes or resting on laurels.

      Maybe, but "closed formats" is what ensured Microsoft a quasi-monopoly for the past 25 years.

  • I always wondered why Microsoft weren't terminally ashamed that they were the only company in the world that could

    1. produce a very good web based email/calendar client
    and
    2. yet have it not work properly on any browser other than MSIE

    surely that fact hurt them when bidding for contracts?

    But I don't doubt that their ODF implementation will be equally poor.

    • 2. yet have it not work properly on any browser other than MSIE

      What? My wife uses Firefox and Chrome with outlook.com every day. What doesn't work properly, exactly?

  • What is this rubbish? Didn't we have these talks a long time ago already?

    - Office 2007 and Office 2010 support ODF 1.1
    - Office 2013 also supports ODF 1.2

    Go open your Microsoft Office, and the option to save in OpenDocument is right there in the Save As dialog.

    Whether anyone actually uses it, is the real question.

    • What is this rubbish?

      This rubbish is Office 365.

      Didn't we have these talks a long time ago already?

      No. This is about Office 365, not about Office for Windows.

      • So what? People here are still talking like it's a new thing being introduced to Office, while the support has been there for well over half a decade. Here is even a Slashdot announcement from 2009 [slashdot.org].
    • by samjam ( 256347 )

      What is this rubbish? Didn't we have these talks a long time ago already?

      - Office 2007 and Office 2010 support ODF 1.1

      - Office 2013 also supports ODF 1.2

      Go open your Microsoft Office, and the option to save in OpenDocument is right there in the Save As dialog.

      Whether anyone actually uses it, is the real question.

      http://lmgtfy.com/?q=what+is+o... [lmgtfy.com]

      "Office 365" refers to subscription plans that include access to Office applications plus other productivity services that are enabled over the Internet (cloud services), such as Lync web conferencing and Exchange Online hosted email for business, and additional online storage with OneDrive and Skype world ...

      It doesn't seem to be the same as Office 2007 or Office 2010 or Office 2013.

      There was a bit of a clue in the name, but we don't read articles and we don't even read th

  • first of all, I get annoyed every time that Word bugs me with the question of whether I'd rather use ODF or OOXML... I always choose Microsoft's format as it doesn't really give me anything I didn't have before to use ODF.

    Second, ODF is a dog with flees. Unless two or more word processors actually support the same feature sets, it doesn't actually support a standard format beyond very very basic functionality. Different word processors (or other office products) regularly differentiate themselves from each

Beware of all enterprises that require new clothes, and not rather a new wearer of clothes. -- Henry David Thoreau

Working...