Language Selection

English French German Italian Portuguese Spanish

OOo

French Government IT directorate stands its ground : ODF supported, OOXML rejected

Filed under
LibO
OOo

The final draft version of the RGI (general interoperability framework), still awaiting final validation, maintains ODF as the recommended format for office documents within French administrations. This new version of the RGI provides substantiated criticism of the OOXML Microsoft format. April thanks the DISIC (French Inter-ministerial IT directorate) for not giving in to pressure and acting in the long-term interest of all French citizens and their administrations.

Read more

Discussion: French Government IT Directorate Supports ODF, Rejects OOXML

Apache OpenOffice versus LibreOffice

Filed under
LibO
OOo
-s

Following yesterday's LibreOffice report for 2014, comes another interesting report from Document Foundation members Barend Jonkers and Cor Nouws comparing the features of LibreOffice and OpenOffice. The 60-page report "focuses on areas as feasibility, smart use, quality and improvements, localization and more." It makes clear that LibreOffice has undergone massive improvements as compared to OpenOffice.

Read more

Proprietary OOXML document format makes you more vulnerable to attacks

Filed under
LibO
Security
OOo

Using the proprietary OOXML document format, i.e. docx, pptx and xlsx, makes you more vulnerable to phishing and other attacks. Earlier this month, the Japanese anti-virus company Trend Micro published a blog post describing how the attack group "Operation Pawn Storm" uses spear-phishing mail messages with malicious Office documents to target the military, governments, defense industries and the media.

Four years ago, Thomas Caspers and Oliver Zendel from the German Federal Office for Information Security (BSI) already presented research results stating that most spear-phishing attacks targeting specific persons or a small group of victims are using "launch actions" in Office and PDF documents to have their malicious code executed.

Read more

When enthusiasm for free software turns ugly

Filed under
LibO
OOo

In theory, maybe some way exists to encourage the enthusiasm that free software inspires while discouraging the ugliness of insularity. The idealism of free software has shaped my life so thoroughly that I wince when it is twisted.

Read more

What's Next for Apache's Open Source Office Suite, OpenOffice?

Filed under
OOo

Still, as one of the longest-standing open source productivity apps, and one that played a major role in making desktop Linux viable, OpenOffice is a venerable project. Indeed, its history stretches all the way back to 1985 (when I was still merely an idea!), and it has been open source since 2000. If it folds, it will be one of the first big-name open source apps to do so—even if few people notice as they continue happily chugging along on LibreOffice.

Read more

Is OpenOffice Dying?

Filed under
LibO
OOo

In September 2014, rumors were flying that Apache OpenOffice was floundering and might soon merge with LibreOffice. The rumors were denied, but revived in March 2015 when Jonathan Corbett used development activity statistics to show that OpenOffice was seriously short of developers, and had corporate support only from IBM. Now, OpenOffice's most recent report to the Apache Foundation appears to reinforce these previous reports, and then some.

To be fair, the report is listed as "a working copy and not to be quoted." However, I am discussing it anyway for two reasons. First, much of the report was mentioned in earlier reports, which suggests that its information is accurate. Second, when I contacted Jan Iversen, the new OpenOffice Chair, three weeks ago, he gave the same warning even more strongly. Since then the contents has gone through at least one more draft, but with little change of content, which makes me suspect that the excuse is an effort to delay discussion of the content. If I am mistaken, the fact will eventually become obvious, since the report is, after all, a public document.

Read more

ODF in the age of Big Data

Filed under
LibO
OOo

One may notice that the points listed above loosely match the main points usually mentioned when discussing the benefits of ODF in the more standard settings of the desktop. This is not surprising, but it was not necessarily intended; if anything this is a testimony to the value of a standard like ODF and its importance. The key point here is that when it comes to the cloud and big data, ODF is both a factor of transparency and innovation. This is something worth promoting and is a potential path to renewed success of ODF in the future.

Read more

UK Government Now Main Driver of ODF Advance: Kudos

Filed under
LibO
OOo

Back in July last year, I wrote about an incredible opportunity for the open source world. After years of disappointments, and despite the usual lobbying/threats by a certain large US software company against the move, the Cabinet Office announced that it was officially adopting the Open Document Format (ODF) for sharing or collaborating on government documents. At the time I exhorted everyone involved to do their utmost to make this work, since it was the biggest chance to show that open standards and open source were not just viable as a government solution, but actually better than the alternatives.

Read more

Development activity in LibreOffice and OpenOffice

Filed under
LibO
OOo

The LibreOffice project was announced with great fanfare in September 2010. Nearly one year later, the OpenOffice.org project (from which LibreOffice was forked) was cut loose from Oracle and found a new home as an Apache project. It is fair to say that the rivalry between the two projects in the time since then has been strong. Predictions that one project or the other would fail have not been borne out, but that does not mean that the two projects are equally successful. A look at the two projects' development communities reveals some interesting differences.

Read more

What will it take to merge LibreOffice and OpenOffice?

Filed under
LibO
OOo

Ordinarily, I'm all for diversity in free software projects. However, I make an exception in the case of LibreOffice and OpenOffice. The sooner they become a single project, the better.

In other cases, I'm slow to accept arguments against duplication of projects. Combining projects does not automatically make for greater efficiency or quicker development; especially in the beginning, personalities can sabotage or even reverse any gains.

Read more

Syndicate content

More in Tux Machines

FreeBSD Quarterly Status Report

We also provide some up to date information about the status of our IRC channels Read more Also: FreeBSD In Q2'2019 Saw Updated Graphics Drivers, Continued Linux Compatibility Layer

DragonFlyBSD Pulls In AMD Radeon Graphics Code From Linux The 4.7 Kernel

It was just last month that DragonFlyBSD pulled in Radeon's Linux 4.4 kernel driver code as an upgrade from the Linux 3.19 era code they had been using for their open-source AMD graphics support. This week that's now up to a Linux 4.7 era port. François Tigeot who continues doing amazing work on pulling in updates to DragonFlyBSD's graphics driver now upgraded the Radeon DRM code to match that of what is found in the upstream Linux 4.7.10 kernel. Read more

Android Leftovers

TenFourFox FPR16b1 available

FPR16 got delayed because I really tried very hard to make some progress on our two biggest JavaScript deficiencies, the infamous issues 521 (async and await) and 533 (this is undefined). Unfortunately, not only did I make little progress on either, but the speculative fix I tried for issue 533 turned out to be the patch that unsettled the optimized build and had to be backed out. There is some partial work on issue 521, though, including a fully working parser patch. The problem is plumbing this into the browser runtime which is ripe for all kinds of regressions and is not currently implemented (instead, for compatibility, async functions get turned into a bytecode of null throw null return, essentially making any call to an async function throw an exception because it wouldn't have worked in the first place). This wouldn't seem very useful except that effectively what the whole shebang does is convert a compile-time error into a runtime warning, such that other functions that previously might not have been able to load because of the error can now be parsed and hopefully run. With luck this should improve the functionality of sites using these functions even if everything still doesn't fully work, as a down payment hopefully on a future implementation. It may not be technically possible but it's a start. Read more