Berlin is already a Windows shop and it’s not window-shopping
Summary: A Softpedia report that says the City of Berlin is moving to Microsoft Office is flawed and may be based on a poor translation
Last year we wrote about Berlin's reluctance to follow the lead of Munich, which happily uses Free software and GNU/Linux, despite the FUD from Microsoft (including some of the latest, not just last year's). It has been over a year since a formal investigation was launched into Microsoft’s bribery of officials in many countries. We are not aware of any progress on it, but all we can say is that Microsoft did try ‘soft’ bribes in derailing Munich’s efforts. There is a lot of rogue stuff going on and we covered it in past years.
According to this one report in English, “City of Berlin Going from OpenOffice Back to Microsoft Office”. The problem is, we are not aware of Berlin ever moving to OpenOffice. I spoke to an old friend in Berlin (he works on LibreOffice) as this report continued to seem a little suspicious. I followed through to the source, assuming it either shows that once again Microsoft bribes have paid off or that Microsoft is spreading lies and FUD. As it turns out, a poor translation by Silviu Stahie may be the issue.
“As it turns out, a poor translation by Silviu Stahie may be the issue.”According to this report, Microsoft OOXML is again interfering with adoption of Free software in government. To quote: “It’s difficult to say what the steps that prompted the city officials to make this decision were. It might just as well be the fact that documents created with OpenOffice 3.2 can’t be opened by people with newer or proprietary software, or vice versa.
“The fact of the matter is that LibreOffice, a much newer and modern office suite open source solution, can do all these things. It’s already used in cities around the world, so others don’t seem to have the same problems as Berlin. From what we can gather from the Golem.de report, the switch to Microsoft Office is already happening and it should be finished by the end of 2015.
“A much bigger issue is the lack of intervention from the German government, which has yet to implement or regulate the use of open source formats in its own branches. Things would be much simpler if everyone used a single kind of file format that can be read by both proprietary and open source software.”
The original article (in German) basically says that it’s about the tax authorities, not the City of Berlin. The article also blames it squarely on OOXML, stating at the end (now translating into English) that a requirement that one should use open formats for the government of a state is possible, as shown in the United Kingdom, which established in July of this year PDF and ODF as the standards for documents. █
Send this to a friend
Summary: Having attacked the industry’s document standard OpenDocument Format (ODF) while pretending to have ‘embraced’ ODF Microsoft is now pretending that it is eager to support OpenGL
MICROSOFT just won’t leave anything alone, not even its rivals (or especially its rivals). Microsoft is a maestro of “embrace and extend” strategies. In the case of ODF, Microsoft insists on openwashing so as to stop Free software and open standards. When Microsoft pretended to ‘embrace’ ODF it actually attacked it, and it continues to attack ODF to this day (2014). It tries to do it secretly, via proxies like the BSA. It is very hard to find out who is doing what because the whole affair is shrouded in secrecy. This secrecy is part of the design.
Dr. Glyn Moody tried using the law to impose transparency on Microsoft’s actions. He failed, but in the process he did manage to reveal that Microsoft was up to no good. Here's the latest:
This is really one of the most ridiculous get-out clauses, because it is so wide. The whole point of the FOI system is so that we can see precisely what is being said in these discussions, and to find out what companies are saying behind closed doors – and what ministers are replying. Although it’s laudable that the Department for Business Innovation and Skills got in touch to correct its response to me, it’s rather rich to do so and then simply refuse point-blank to release any of the information it has just found.
The only consolation is that whatever Microsoft whispered in the corridors of power to de-rail the move to ODF – since I hardly imagine it was a fervent supporter of the idea – it didn’t work. However, there are doubtless many other occasions when it did, but we will never know. That’s just unacceptable in a modern democracy.
What we have here is a clear reminder that Microsoft is attacking open standards in the UK. Microsoft bribed people to rig balloting processes all around the world and it tried hard to confuse the public by calling a proprietary format “Open XML”, using a lot of abuses to also put some stamps on it. Microsoft is basically diluting the brand of Open Source, just as with Nokia at the moment Microsoft is naming Windows “Debian”. To quote a mystifying new report: “When Linux users hear about Debian they know instantly that it’s one of the best and most popular operating systems out there. Nobody thinks that it might be a new firmware for a Windows-powered Nokia phone.”
Is that not a trademark infringement? Debbie and Ian would almost certainly not approve.
Going back to standards, what Microsoft has been trying with ODF, as we have demonstrated repeatedly, is an “embrace and extend” manoeuvre. It’s like “the ‘other’ Java” from Microsoft, to name just one example where Microsoft destroys rivals by ‘embracing’ them and then distorting them.
After Microsoft’s many attacks on OpenGL (there is no “Microsoft OpenGL”, but Microsoft did contribute to harming of OpenGL as a standard and even derailed gaming under GNU/Linux this way) we learn about this disturbing (but rather predictable) move:
Neil Trevett, the VP of the Mobile Developer Ecosystem at NVIDIA and also serves as the President of the Khronos Group, confirmed that Microsoft has joined the Khronos Group’s WebGL working group. Microsoft in past years has generally distanced itself from “GL” in favor of their own Direct3D API. Microsoft was originally a member of the OpenGL Architecture Review Board, but they’ve been out of that position for more than one decade with just pushing DirectX on Windows and leaving Windows OpenGL support as a bastard child.
Microsoft is hoping to dip its fingers in OpenGL so that it can better control it. Khronos oughtn’t allow the Microsoft moles in, assuming it remembers the history of what Microsoft did to OpenGL. There are promising new features in the latest OpenGL and OpenCL [1,2,3], so to let a dying platform like Windows show the way would be rather unwise. Microsoft wants to do to OpenGL (OGL) what it did to Open Document Format (ODF). Microsoft wants and needs lock-in in order to survive. Since it’s WebGL we are dealing with here, just recall all the damage Microsoft caused to and brought upon the Web. █
Related/contextual items from the news:
Khronos announced a call for participation in a next-generation OpenGL initiative. The announcement reads, “Khronos announced a call for participation today in a project to define a future open standard for high-efficiency access to graphics and compute on modern GPUs. Key directions for the new ground-up design include explicit application control over GPU and CPU workloads for performance and predictability, a multithreading-friendly API with greatly reduced overhead, a common shader program intermediate language, and a strengthened ecosystem focus that includes rigorous conformance testing. Fast-paced work on detailed proposals and designs are already underway, and any company interested to participate is strongly encouraged to join Khronos for a voice and a vote in the development process.”
Well, the next-gen OpenGL didn’t end up being OpenGL 5.0 but is being billed as OpenGL 4.5. Regardless, the OpenGL 4.5 specification is out now.
Besides OpenGL 4.5, the Khronos Group announced from SIGGRAPH 2014 in Vancouver today the release of the provisional specification for SPIR 2.0.
Send this to a friend
Summary: Microsoft continues to distort the office suites market and impede interoperability using the OOXML pseudo ‘standard’, essentially by branching out into “Strict” and “Transitional”, making it exceedingly hard for developers to deal with files generated by Microsoft Office and vice versa
TRYING to work with Microsoft is misguided. Just look and see what has happened to many companies, including — to name a recent example — Nokia. Microsoft has no honour for anyone but Microsoft itself. Microsoft was bribing officials and abusing sceptics in order to get its way when it comes to document formats. Nobody should forget the crimes that Microsoft committed in order to keep the world stuck with Microsoft Office. We reminded the British government of these crimes and very recently the UK adopted ODF. This was a very smart and timely move because based on people from The Document Foundation (TDF), the bogus ‘standard’ which is basically just an ‘open’-looking gown for Microsoft Office (proprietary) formats is now being further distorted in order to cause trouble for people who are not Microsoft customers. These abuses are even worse than before and Microsoft thinks it can get away with them because it bribed people to put an ECMA and ISO stamp on OOXML (no matters what happens to it later on).
As Charles from The Document Foundation put it the other day:
Regular readers of this blog will remember these glorious days, just before the big financial crisis, where Microsoft had created the so-called OpenXML standard that was supposed to be totally not competing against the OpenDocument Format, managed to have pretty much the entire standards community swallow it in the most creative ways possible, then fell short of actually implementing it in its own products. A good summary of the whole -technical- story is available here. The irony of life has the uncanny ability to devise ways to enchant us. Well, sort of. The format called “OOXML – Strict”, by comparison to “OOXML-Transitional” was the readable open part of the ISO 29500 standard, known as OOXML. For years, it was obvious that Microsoft Office implemented OOXML-Transitional (the heap of the more or less documented parts of the format alongside undocumented blurbs) and nothing else, creating a situation where one standard, OOXML was existing, and another format, OOXML, was fully implemented and spread all around, yet was an undocumented, proprietary specification. That’s the .docx, pptx, and .xlsx you see everywhere, and the one LibreOffice was busy reverse-engineering for all these years.
This unfortunate situation, we were told, was about to change soon, with the full adoption of OOXML-Strict by Microsoft Office. Helas, if you open a purely OOXML-Strict compliant file with Microsoft Office 2013, the file will be declared corrupt. If you open the same one with LibreOffice 4.3, the file will open and you will be able to edit its contents just like with any other format supported by LibreOffice. In other words, LibreOffice can claim to have a better support of OOXML than Microsoft Office, despite years of unfulfilled promises, pledges, and never met expectations by Redmond. I guess that, just like the old saying goes, promises only commit the ones who actually believe them.
IBM’s Rob Weir has just released another piece about document formats  and a new interview with Italo Vignoli of The Document Foundation  sheds more light on what Charles spoke about. To quote Vignoli: “MS Office locks-in the user not only with proprietary formats but also with the OOXML pseudo-standard format. This is due to the way the supposedly standard format is handled by MS Office.
“In fact, each version of MS Office since 2007 has a different and non standard implementation of OOXML, which is defined as “transitional” because it contains elements which are supposed to be deprecated at standard level, but are still there for compatibility reasons.
“Although LibreOffice manages to read and write OOXML in a fairly appropriate way, it will be impossible to achieve a perfect interoperability because of these different non standard versions.
“In addition to format incompatibilities, Microsoft – with OOXML – has introduced elements which may lead the user into producing a non interoperable document, such as the C-Fonts (for instance, Calibri and Cambria).”
When Microsoft speaks about following standards what it means to say is that “Microsoft is the standard” and everyone must just follow Microsoft. Only a fool would choose OOXML over ODF, especially now. Korea and China seem to be moving away from Office quite rapidly. █
Related/contextual items from the news:
And then there is a document as the record of what we did. This is implied by the verb “to document”. This use of documents is still critical, since it is ingrained in various regulatory, legal and business processes. Sometimes you need “a document.” It won’t do to have your business contract on a wiki. You can’t prove conformance to a regulation via a Twitter stream. We may no longer print and file our “hard” documents, but there is a need to have a durable, persistable, portable, signable form of a document. PDF serves well for some instances, but not in others. What does PDF do with a spreadsheet, for example? All the formulas are lost.
The UK government recently announced that they would use ISO approved document standard ODF for viewing and sharing government documents. It’s a very important move because it breaks Microsoft’s vendor lock where single US-based company ‘owns’ and ‘controls’ all the documents created on Earth. Microsoft is infamous for using unethical means to make it harder for other players to offer any kind of interoperability with their products which can threaten Microsoft’s market share.
So we reached out to Italo Vignoli of The Document Foundation, the organization responsible for developing LibreOffice which is a fork of OpenOffice, to understand the risks of using OOXML…
Send this to a friend
Summary: Only “Microsoft as the standard” is the ‘standard’ Microsoft is willing to accept, as its response to the Cabinet Office’s judgment reveals
AT THE BEGINNING of this week we learned that the British (UK) Cabinet Office, a highly influential department with technology imperatives, did the correct thing by no longer requiring British citizens to become clients of Microsoft (and users of expensive spyware) to merely communicate with their government. The Cabinet Office “goes open source” is how one news site put it, but ODF, the OpenDocument Format, is not necessarily about Free/Open Source software. ODF is about many applications working together, not via formats that are designed around a single application and its various versions (that’s what OOXML is).
Techrights did not break this news. It was Andy Updegrove who did, along with Cabinet Office. Quoting Updegrove:
The U.K. Cabinet Office accomplished today what the Commonwealth of Massachusetts set out (unsuccessfully) to achieve ten years ago: it formally required compliance with the Open Document Format (ODF) by software to be purchased in the future across all government bodies. Compliance with any of the existing versions of OOXML, the competing document format championed by Microsoft, is neither required nor relevant. The announcement was made today by The Minister for the Cabinet Office, Francis Maude.
The Cabinet Office stated:
The open standards selected for sharing and viewing government documents have been announced by the Minister for the Cabinet Office, Francis Maude.
Not too shockingly, as one ought to expect, the following day Microsoft attacked this decision. despite claiming to have ‘embraced’ ODF. “Microsoft attacks UK government decision to adopt ODF for document formats” said one headline, stating: “Microsoft has attacked the UK government’s decision to adopt ODF as its standard document format, saying it is “unclear” how UK citizens will benefit.
“The Cabinet Office announced its new policy yesterday, whereby Open Document Format (ODF) is immediately established as the standard for sharing documents across the public sector, with PDF and HTML also acceptable when viewing documents.”
“Turning its back on Microsoft Office’s native formats, the UK government has adopted the Open Document Format for all its sharable documents,”
writes Steven J. Vaughan-Nichols, but if Microsoft is really all about openness, then Microsoft should welcome this decision, not attack it. It is quite revealing that Microsoft is not really interested in fair competition, interoperability, and openness.
“UK government makes “big step forward” on open document standards,” said the headline from Opensource.com (Red Hat).
We already wrote so much about it and warmed the Cabinet Office about Microsoft’s abusive responses, which include trying to get people fired, bribing some other people, using (or exploiting) disabled people to attack people’s rational decisions, and so on.
Dr. Glyn Moody wrote about “Massachusetts ODF fiasco a decade ago” and said about this important milestone: “Let’s Not Mess it up””
While celebrating this great news, I really want to emphasise Bracken’s point about managing the switch properly. We can be absolutely certain that Microsoft will fight this decision in every way possible. It will certainly seize on any problems that arise during the implementation as “proof” that it was the wrong choice. That makes it crucial that the open source community do everything in its power to aid the Cabinet Office here.
One particular area that concerns me is cross-compatibility. I’m hearing stories about difficulty in transferring ODF files from LibreOffice to Apache OpenOffice, with formatting of things like tables being messed up in the process. This is completely unacceptable: one of the benefits of adopting an open standard is the ability to swap in and out different applications. If that theory proves impossible in reality, we have a huge problem.
I would therefore like to entreat all the open source projects and communities that work on ODF to get together and sort this out. In the wake of the fantastic – and brave – move by the Cabinet Office, providing full interoperability among open source implementations must be a priority.
Yesterday’s news is truly a unique opportunity to show the power of open standards, to promote the benefits of open source, and to bring about its wider dissemination both in government, and among home users. The price of failure here would be extremely high: yet more years in the wilderness, as happened after the Massachusetts ODF fiasco a decade ago. So let’s not mess it up.
The Mukt, which covered this important development. delivered yet another call for Google to adopt ODF as the default document format, ending Google’s cowardly approach towards document formats.
We feel as though we played some role in the above (being among hundreds of people who wrote to the Cabinet Office). We not only wrote a lot about it and also wrote to the Office itself almost a dozen times, engaging in a discussion with members of staff. █
Send this to a friend
Summary: Another step in the long struggle to cast proprietary as ‘open’, especially when it comes to Microsoft’s last remaining cash cow and Facebook’s core business of mass surveillance
Openwashing has been a key ingredient of Microsoft’s strategy as of late, pretending that its privacy violations and patent racketeering are somehow outweighted by some kind of goodwill. This is something that not only Microsoft does but also the (partly) Microsoft-owned Facebook is doing quite a lot these days. It is truly disturbing.
Angus Kidman said that “Open [sic] XML is the format which Microsoft Office has used to store Office documents since Office 2007″ even though it is untrue. Almost nobody used it at the time, so Microsoft bribed and corrupted so many people and organisations, hoping to universally impose OOXML on people, pretending it was “open” even though it was all about proprietary Office. Nobody was going to use something so unnecessary, so Microsoft bribed many people for this, including large companies, as compatibility with existing formats had improved and the goalposts needed to be moved. Here is LibreOffice’s Meeks, who was surrendering to Microsoft’s proprietary OOXML rather than adhering to standards like ODF, probably because he was paid by Novell at the time (and Novell was bribed by Microsoft specifically — as per the contractual agreement — to promote and openwash OOXML).
“When the press is trying to insinuate that Microsoft (Office) and Facebook are open there is clearly something wrong with the press.”So once again they are using “Open Source” to promote proprietary lock-in. This is not a novel concept, Microsoft did this with Novell (converter). Phoronix says: “This work may benefit some open-source document editors / office suite software, with more commentary being available from Michael Meeks’ blog.”
How is being reliant on OOXML beneficial to anyone but Microsoft shareholders? This is a trap. We need to reject this format. Google too should stop its unhelpful backing of OOXML, which is getting more detrimental by the day (more of it in the company’s latest event was disclosed, affirming Google’s lack of commitement to document standards).
As noted by some bloggers and writers for the European Commission’s Web site: “To ensure preservation of digital assets, it is essential that specific file formats are implementable in open source software, concludes Björn Lundell, associate professor at the University of Skövde in Sweden. He recommends this should be made a requirement for digital asset strategies of public administrations, thus minimising the risk of losing control over these assets.”
Well, there are patents in OOXML and complexity which shows that it’s really just designed around one implementation in a proprietary form (Office). OOXML should be rejected, especially in the public sector. There is nothing open about it. It’s a massive lie.
Nicholas Miller from VentureBeat and others play a role in a similarly-disturbing campaign that seeks to paint Facebook as “open”. With press release-oriented ‘journalists’ out there it has been quite easy. The Facebook openwashing that we recently wrote about is further promoted by pro-Facebook sites that use semantic jokes to get across this illusion.
When the press is trying to insinuate that Microsoft (Office) and Facebook are open there is clearly something wrong with the press. These are systematic and very persistent (especially this year) openwashing campaigns that everyone should push back against because these deceive and help derail real Free software. █
Send this to a friend
OOXML: When crime pays off
Summary: Reports from the European Commission’s Web site reveal the degree to which OOXML is successfully derailing migrations to Free/libre software in the public sector
SOME of the criminals involved in the OOXML festival of corruption have already left Microsoft (e.g. Oliver Bell, who joined a Gates-funded Gates grooming operation) or joined Microsoft (e.g. Peter O’Kelly), so holding them accountable would be hard, especially now that years have passed and conditions have changed. Microsoft got away with a lot of crime, including bribery. Nobody was sent to jail or even put on trial. Microsoft is above the law, no doubt. It’s an international problem that we find also in the case of large banks, not just software companies with strong ties to the NSA for example.
According to this new report from the European Commission’s Web site, “Open source [is] hindered by OOXML incompatibilities” (as intended and planned by Microsoft). To qoute: “The mixing of outdated and incompatible versions of OOXML, an XML document format, is hindering implementation in open source office alternatives, according to a study published on the Open Source Observatory and Repository (OSOR) today. The different OOXML versions also pose difficulties for public administrations that use different proprietary office suite versions, and the inconsistencies are causing problems with older documents. The OOXML document format is hindering the interoperability of suites of office productivity tools.”
There is also this accompanying report titled “Complex singularity versus openness”.
“Does not even mention ODF,” pointed out one of our readers about this article. “When M$ forced it’s XML file-format on the world for office suites it deliberately created lock-in,” wrote Pogson.
This once again reminds us why Microsoft went as far as criminal activities. It sought to prevent people all around the world from taking their data to better platforms or even create new data in formats that would continue to make the data accessible. To us at Techrights is has always been somewhat of an outrageous mystery that nobody was sent to jail for it. It shows that the system which purports to uphold justice is very arbitrary and unjust, with Microsoft positioned on the side of immunity while it helps secret agencies illegally violate rights of citizens. █
Send this to a friend
Image from the 10 Downing Street Web site
Summary: A roundup of resistance to OpenDocument Format (ODF) and Free/Open Source software (FOSS) in the British public sector
AS ONE ought to expect, especially based on past experiences, a migration to FOSS won’t happen without resistance from an old generation of Microsoft proponents. Just watch how Microsoft rallied its partners to object to a pro-ODF consultation (we explained Microsoft's very dirty tactics to the Cabinet Office). It didn’t quite end there.
Despite the fact that a foreign government is cracking PCs with Windows on them (and seeking to make this practice legal), some people in suits here in Britain insist that Windows in the public sector is an acceptable risk. It’s not. It should be banned. Well, some government departments quietly move towards FOSS (I work with them) and numerous keep quiet about it for fear of retribution from Microsoft and/or its partners, who view FOSS like it’s some kind of Communism that’s spreading.
Continued resistance from Luddites and “tribe elders” of technology (who grew up in another type of world and dined with executives of proprietary software vendors) was expected all along. The ODF consultation showed just one portion of it (publicly-visible, unlike some stories I know of but cannot share).
One reader asked me yesterday: “what became of that government consultation?”
Well, nothing so far, as far as we know. This new article that this reader sent us states: “if you blithely email someone a .docx file you are effectively condemning them to pay rent to Microsoft for ever.”
Indeed, and this too is a reason to shun Microsoft, not just the back doors. The author continues by stating: “One way to loosen the corporate stranglehold would be for everyone to adopt the set of standards called Open Document Format, designed so the files work the same whatever software or computer type you use.”
Yes, indeed, but there are people who stand in the way of implementing national (top-down) policy.
Earlier this month there were a bunch of Microsoft-friendly British articles (at least 3), the latest of which is this one. They all cite Jos Creese (the original/seminal article was this, but it led to some more, even overseas), relaying claims that “Microsoft is cheaper” (than FOSS).
This is wrong on so many levels. It very much depends on what’s calculated and how. OOXML is massively dangerous lock-in. Microsoft had to corrupt the world’s standards bodies to get it where it is today. The bribery for Windows-only formats was documented here half a decade (or more) ago and it was coupled by patent extortion, bribing of companies, and all sorts of other criminal acts. To say that Microsoft is cheaper is almost like saying that robbing a bank is cheaper than working (labour) for the same money. To use a better analogy, to get oneself locked into one vendor is not “cheap”. It has been reported that the British government pays ~$10,000 per Windows desktop per year. Cheap, eh? It’s more like extortion. There is a monopoly on support.
Concurrently, Adrian Bridgwater offers some convenient hogwash that ‘vanishes’ Microsoft’s criminal activities against GNU/Linux, pretending that there is something inherently wrong with FOSS and/or GNU/Linux and that this is the reason it does not (yet) dominate the desktop. Never mind OOXML abuses, bribes against GNU/Linux (we documented some), and many other forms of manipulation. This is the type of revisionism that Microsoft requires right now, creating the illusion that FOSS is inadequate for desktop use, even though Chromebooks are taking off (they run GNU/Linux), defying Microsoft’s vicious attack ads.
One commentator at IDG alluded to the above people as “clueless CIOs” in his headline, stating that “companies are using open source to bring their legacy apps up to code, but all too many CIOs are still clueless about how often open source is being used in their own organizations.”
It wasn’t just clueless CIOs like Jos Creese who offered Microsoft lip service in the British press earlier this month, proposing lock-in rather than freedom because lock-in is supposedly “cheaper”. Another article, citing another bunch, speaks about LibreOffice/OpenOffice, focusing on Microsoft macros lock-in and OOXML lock-in to make FOSS seem inadequate. Titled “Open source ‘fails to excite councils’”, the article makes arguments like the following:
It added that open source software is seen to be difficult to replicate automated interfaces to Microsoft Office products which connect with council systems.
This is precisely the reason to dump Microsoft, not to avoid dumping Microsoft. This is evidence of lock-in and the better one gets out of the lock-in, the better.
On a brighter note, there is a new article from Ireland titled “open source is where I think the future is headed in local government…”
It is not a formal article, but it shows that people — influential people even — do in fact promote FOSS. To quote:
So, I’m in Dublin tomorrow for the OGP Europe Regional conference in Dublin in advance of next week’s Digital Lunch asking if Northern Ireland is ready for an open government partnership? If you are interesting in the subject, do keep an eye on Twitter throughout the day, and I’ll update with a blog report on Friday morning before I leave again.
It is expected that in the coming months or even years some vassals of Microsoft will go public (to the press) bashing FOSS with FUD, misdirection, miscalculations and stereotypes, sometimes criticising FOSS for not being sufficiently Microsofty (e.g. dealing with OOXML). Their arguments often insinuate that abandoning Microsoft would be wise (the opposite of what they mean to say); the British public sector got caught up in expensive and dangerous (back doors for starters) dependence. Free software would give Britain back its sovereignty. Technical autonomy is priceless; it is invaluable. █
Send this to a friend
Preservation a priority
Summary: The Document Liberation Project makes the press and software such as LibreOffice plays a role while other players, such as Open-Xchange, are also hopping on the ODF bandwagon
IN THE MONTHS of February and March we revisited ODF because of a policy that had been promoted in the UK — one which favours disseminating government documents not just to customers of Microsoft (who purchased proprietary software like Microsoft Office).
The problems caused by OOXML are explained again by one whom we interviewed in episode 74 of TechBytes. His name is Charles-H. Schulz and he is from LibreOffice. He says that “Microsoft Office had been released and with it an undocument format called OOXML which, as far as experts were concerned, had little to do with the ISO 29500 (aka OOXML) standard. While Europe and Brazil were struggling to migrate their public sector’s documents to ODF, any company or government, let alone any individual acquiring Microsoft Office 2010 migrated to the new and shiny OOXML, officially without remorse or complaint. The ODF advocacy groups here and there were launching all sorts of events and meetings to guide and assist migrations to ODF. Results were mixed. We had victories. We had defeats. At the end of the day what was at stake was fear of failure and change from CIOs and IT services. That’s still the case today. But while these are mostly human factors, there is one thing we hadn’t tried yet, or at least hadn’t been tried enough: turning the hundreds of thousands of files that are out there and locked up in various proprietary file formats to ODF documents.”
Another advocate of ODF, Andrew Updegrove, tells the story of Microsoft’s attacks on officials who ‘dared’ to promote ODF. Updegrove recalls: “By the end of December 2005, I had been blogging on ODF developments in Massachusetts for about four months, providing interviews, legal analysis and news as it happened. In those early days, not many bloggers were covering the ODF story, and email began to come my way from people that I had never met before, from as far away as Australia, and as near as the State House in Boston. Some began with, “This seems really important – what can I do to help?” Others contained important information that someone wanted to share, and that I was happy to receive.”
We are not going to go about a decade into the past again, but the point worth making is that OOXML remains a huge issue. Microsoft’s worldwide bribery was not in vain. My wife reports that OOXML crashes LibreOffice (on GNU/Linux) for her, sometimes even freezing the entire operating system.
Making the news these days is the Document Liberation Project [1-3], which even Updegrove wrote about . For those who think that ODF is old news, be aware that Open-Xchange is entering the online office suites business [5,6] and “support for the Open Document Format (ODF) is forthcoming, probably within the next three months, a company spokesman said.” (source: IDG)
Later this year we are going to see if the British government, owing to Cabinet Office, goes ahead with plans of making ODF the default format for editable document exchanges. This could set an important precedence for other nations to follow, ensuring that their documents down fall down the digital ashtray with Microsoft’s proprietary formats. █
Related/contextual items from the news:
Ever been in a situation when no maintained software reads your old files? During Libre Graphics Meeting 2014, Document Foundation announced a new project called Document Liberation.
This project unites developers who help users to access data in file formats that are locked to proprietary and even abandoned software.
Essentially it’s a new face of the existing joined team from LibreOffice and re-lab that is already “responsible” for libraries to read and convert Corel DRAW, Microsoft Visio and Publisher, Apple Keynote and Pages files. Implementations in end-user software include (but are not limited to) LibreOffice, Inkscape, Scribus, and Calligra Suite.
New open source developer consortium promises to end upgrade arms race, enabling users to reclaim orphaned documents
You’ll recall that I noted above Document Freedom Day awareness is limited in the U.S. So is participation in DFD activities, as you can see from the image at left, which shows where they are being held this year. That’s a shame, because document freedom is a universal, and not a regional or national concern.
Open source collaboration software vendor Open-Xchange has added a spreadsheet function to its open-source, web-based productivity suite, allowing the online editing and sharing of Microsoft Excel documents.
Send this to a friend
« Previous entries Next Page » Next Page »