The Document Foundation Planet

 

May 28, 2016

Andreas Mantke

New Release For The Extension Part Add-On

Despite the sunny weather I found some time and created and published a new release of the Plone add for the extension part of the new LibreOffice extensions and templates website. The add-on is available in the ‚Cheeseshop‘ (https://pypi.python.org/pypi) yet.

by andreasma at May 28, 2016 03:18 PM

May 27, 2016

Andreas Mantke

AddOns For The New Extension-Template-Website

Although I had to diversify my focus for various reasons in the last weeks I managed to work through some smaller remaining topics of the Plone add-ons for the new LibreOffice extensions and templates website. I already created a new release for the templates part and uploaded it to the ‚Cheeseshop‘. A new release for the extension part will follow soon.
Besides this I created a new theming add-on for the website based on the default Plone 5 theme, Barceloneta, that could be improved later.
I also worked with the user/contributor of the current site, started the preparation of the site stuff for the migration to the newer framework. I did some work on the buildout environment for an upgrade to the latest Plone 4.3 version. I’ll run this upgrade during the next days, once all tests are completed.

by andreasma at May 27, 2016 08:00 PM

Jan Iversen

Computer student? Enhance your job changes this summer

image

Why not use this summer to enhance your job chances ?

When you apply for a development position in one of the bigger companies, changes are high that they will look at your opensource involvement. They expect to see something in your CV, and might also have a look at openhub.net.

The LibreOffice project is one of the biggest opensource projects and very well known, with a multi million user base around the world. The libreoffice community is a vibrant set of volunteers who welcomes new people.

We have people dedicated to help you get started (I am one of those), and we have furthermore identified simple problems to be solved easyhacks together with a recipe for success getInvolved

If you decide to join our community, you will be able to write in your CV, that you have worked on a project with more then 7 million lines of code. If you are active in our community  and need references we can help with that.

Let us together make the world just a little bit better and you get an extra point on your CV.

Feel free to contact me if you have questions or comments.

Have a nice summer.

Jan Iversen

 


by jan at May 27, 2016 10:29 AM

May 26, 2016

>Marius Popa Adrian

Tensorflow and why i love it

I work for my paper for master degree (Artistic style Implementation with Tensor Flow) and i love Tensorflow Here are a few reasons why : It's python also i can use it quite easily with my gpus (gtx) also it's distributed across servers using gRPC Tensor Flow has a clean, modular architecture with multiple frontends and execution platforms. Details are in the white paper.

by Adrian Marius Popa (noreply@blogger.com) at May 26, 2016 01:11 PM

Official TDF Blog

Behind the Scenes at TDF: Marketing in Q1 2016

Before going into the details of the marketing activities, The Document Foundation (TDF) is proud to announce that Mike Saunders was hired as Marketing Assistant in mid-February. Mike is known for the famous feature videos he made for LibreOffice 5.1, and he has kicked off the Month of LibreOffice Contribution in May, amongst many other projects. Welcome on board, Mike!

italo-cecchignolaParaphrasing a famous song, marketing at The Document Foundation is “the activity that never sleeps…”. The first quarter is one of the busiest, as we have FOSDEM and one major release happening between the end of January and mid February, followed by several minor releases – to keep up momentum – and a few events, including CeBIT in Germany.

FOSDEM 2016 was a large success for LibreOffice, thanks to the strategic positioning of the booth in the main lobby of building K, where most of the large projects are represented. It was the first time for TDF in the “kernel” of the exhibition, and it showed up. On Saturday, January 30, the project registered more visitors than during the entire FOSDEM 2015 (and almost as many on Sunday, January 31).

On Saturday, January 30, TDF developers were also on stage during the Open Document Editors DevRoom, with over 20 different talks about the upcoming LibreOffice 5.1 release, and related topics.

During FOSDEM, the certification committee also hosted several sessions, mostly via remote connections, to evaluate five candidates: one from Spain: Pasqual Milvaques, one from Taiwan: Frankling Weng, and 3 from Italy: Paolo Dongilli, Antonio Faccioli and Diego Maniacco.

One week after FOSDEM, the marketing team coordinated the announcement of LibreOffice 5.1 on Wednesday, February 10. During Monday and Tuesday, I hosted five different conference calls, with journalists from Europe and the United States. Thanks to this effort, the media coverage has been excellent, with hundreds of positive articles worldwide.

One year later, the improvements to the distribution of press releases based on specific features of phpList are showing up, with an average hit rate often higher than 30%. Thanks to phpList for offering us a free account.

In March, the marketing team has focused on two different projects: CeBIT in Hannover, the largest high tech trade show in Germany, and TDF 2015 Annual Report, which is the most important document produced by the project during the year.

CeBIT is the largest German trade show, and most visitors already know the office suite or even use it. Even if the interest has been lower than in the past, several project members – Thorsten Behrens, Thomas Krumbein and myself – have had the opportunity to present LibreOffice at the open source area, thanks to the collaboration with CIB.

TDF’s 2015 Annual Report will be released during the second quarter, and will provide an overview of what has been achieved by the project at large – i.e. including native language projects at local level – in each area.

Starting from May, we will be organizing a monthly PR call, to involve native language communities in marketing activities. In addition, starting from July, we will also organize online webinars to share competences in marketing and communications with local communities. During these webinars, we will also cover the LibreOffice migration protocol.

by Italo Vignoli at May 26, 2016 09:49 AM

May 24, 2016

Official TDF Blog

Keeping track of LibreOffice activity

noun_27464LibreOffice is a big project, with over 7 million lines of source code and hundreds of developers, testers, translators and other contributors spread across the globe. With so much activity going on, it can be difficult to keep track of recent developments – so here are a few pointers to keep you in the loop.

Upcoming releases

The current supported release of LibreOffice is 5.1, and the latest bug-fix version is 5.1.3. There are three more bug-fix updates due this year, so see this wiki page for information on the release schedule. The last planned update will be 5.1.6, due in October.

Meanwhile, the development team is working hard on LibreOffice 5.2, which is scheduled to be released in the first week of August. A beta version (for testing) is due very soon – keep an eye on this blog for more information. You can also see a mid-development list of new features in 5.2, but bear in mind that everything is subject to change!

Team calls

Many teams inside the LibreOffice project have regular audio or video calls to catch up, share ideas and ask questions. These teams also share minutes (notes) from the meetings afterwards, so that others can keep track of news and developments.

For instance, the Engineering Steering Committee (ESC) usually has a call every Thursday to discuss technical aspects of the project: release engineering, new features, quality assurance, mentoring new developers, and other matters. Minutes from these are posted on the projects mailing list – see the archive here (search for “minutes of ESC” for recent calls).

Similarly, the Design Team holds regular Hangouts to discuss user interface changes and usability enhancements. Then there’s the Infrastructure Team, which has calls to talk about the hardware and software that’s used by LibreOffice contributors, and the Documentation Team, which has just started regular calls to coordinate content and bring in new writers. Minutes from all of these teams are also posted on the projects list.

Finally, The Document Foundation’s Board of Directors has regular meetings to discuss organisational aspects: finances, budget requests, the yearly conference and so forth. Minutes from these meetings are available on the wiki.

Annual Report

A good summary of last year’s activity in the LibreOffice project is provided in the Annual Report. This is currently being worked on, and will have detailed updates from the native language projects, hackfests, development and QA teams, plus information on donations received throughout 2015 and other aspects of the project.

We’ll post an update on this blog when the 2015 Annual Report is available – meanwhile you can read about what happened in LibreOffice during 2014 in the previous report.

by Mike Saunders at May 24, 2016 12:44 PM

May 23, 2016

Official TDF Blog

The Document Liberation Project: What we do

While The Document Foundation is best known for LibreOffice, it also backs the Document Liberation Project. But what exactly is that? We’ve made a short video to explain all…

<iframe allowfullscreen="true" class="youtube-player" height="570" src="https://www.youtube.com/embed/JSqU2Wp-neQ?version=3&amp;rel=1&amp;fs=1&amp;autohide=2&amp;showsearch=0&amp;showinfo=1&amp;iv_load_policy=1&amp;wmode=transparent" style="border:0;" type="text/html" width="960"></iframe>

by Mike Saunders at May 23, 2016 04:28 PM

May 22, 2016

TDF Infrastructure Status

Downtime of Pumbaa

Due to network restructuring at Hetzner, pumbaa will not be available during between 25 May 2016 23:00 hours (CEST) and 26 May 2016 05:00 hours (CEST) for a maximum of 5 minutes.

The following services are affected:

  • Redmine
  • @documentfoundation.org mail-adresses
  • private mailing lists

by The Document Foundation at May 22, 2016 10:00 PM

Charles Schulz

The Month of LibreOffice

This month of May is quite unique for the LibreOffice project. It has been decided that May would be a month dedicated to celebrate both LibreOffice and its community of volunteers. The project is awarding badges and barnstars matching several kinds of contributions and activities; volunteers will be able to harbor them on their own webpage, twitter handle and other social networks platforms. It’s important to understand that this isn’t a “feel good” operation. Volunteers, just like anybody else, want to feel appreciated, especially when nothing forces them to contribute to such a project. By doing so the community acknowledges the contributions of its members.

It also helps spread the word about LibreOffice. Remember, Free/Libre & Open Source Software does not directly produce products. Rather, it develops and releases software through community of contributors, that may then be monetized in one way or another – or perhaps not at all. In other words, this means that the distinction between outbound and inbound marketing that is commonly found in the corporate world is more blurry as any user is also a potential contributor. Marketing our community really means marketing LibreOffice itself. This is what we’re doing this month and it makes me happy. I’m excited at the stats and figures that we will draw from this experiment. If you happen to be a LibreOffice contributor, or just a fan of LibreOffice, you could get a badge. All you need is to contribute to the project in one of the several ways described here and it will be awarded to you: remember, we’re already at the end of the month!

by Charles at May 22, 2016 11:03 AM

May 18, 2016

Miklos Vajna

Recent undo/redo fixes in LibreOffice Impress

I’ve recently spent some time fixing a few bugs around undo/redo in Impress, in the area of table shapes. I’m mentioning these here as they’re all bugfixes, so they are backported to LibreOffice 5.1, and no major release notes will point them out. So if you are using Impress table shapes and you consider their usability suboptimal, then read on, I have some great news. :-)

The first problem is tdf#99396, where there were actually two problems:

  1. Vertical alignment is a cell property, but when setting that property, the undo code was simply missing.

  2. When editing cell text (the user is inside "text edit") the undo stack is in a special mode — and ending text edit made the cell property undo items go away. This wasn’t a problem for vertical alignment only, it was a problem for example when the background color of the cell was changed, too. These cell property changes are now added to the undo stack after finishing text edit, so you can still undo them later.

The second bugreport is tdf#99452 where resizing a table shape row separator and then undoing the resize didn’t restore the original state. See the commit for all the details, but the bottom line is: it isn’t a good idea to automatically re-layout the table when we’ve already resized the shape as part of undo, but the table rows were not yet resized to reflect their original sizes.

As usual, you can try this right now with a 5.2 daily build. :-) (Or even with an 5.1 one, actually.)

May 18, 2016 07:34 AM

May 17, 2016

Official TDF Blog

Month of LibreOffice: Half way there

Yes, we’re just over half way through the May 2016 Month of LibreOffice campaign, and a lot of activity has taken place. So far we’ve awarded over 230 badges for contributions to code, translations, documentation, AskLibreOffice and social media. Take a look at that page and if you spot your name, click one of the Share buttons to tell the world about your contribution!

Want to adorn your website or blog with one of these lovely badges? Just follow these steps and help to make LibreOffice even better than ever before. And, of course, if you want to give someone credit for their work in the LibreOffice project, award them a barnstar and show your thanks.

There’s still two weeks to go in the Month of LibreOffice, so get involved and see how may badges you can collect!

by Mike Saunders at May 17, 2016 12:56 PM

May 13, 2016

Stephan Bergmann

LibreOffice.flatpak

Flatpak is the new name of xdg-app. So following up on my previous LibreOffice in a Box post, here is some more technical detail on how an upcoming LibreOffice 5.2 will be available as a Flatpak bundle.

There is now a shell script demonstrating how to do all the downloading of sources, building, and bundling up. I decided against using flatpak-builder (nee xdg-app-builder) for that mostly out of convenience, mainly because the way LibreOffice fetches its external dependencies is so different from the typical way of building a Linux app. So I felt more comfortable doing these things manually, calling the raw xdg-app build steps from a script. But given enough pressure (e.g., to make the LibreOfficeKit widget buried within the LibreOffice installation set available to other Flatpak apps), this might get revisited.

The script proceeds in six steps (see the above link for details):

First, building LibreOffice requires an Archive-Zip Perl module not found in the org.gnome.Sdk we build against. The easiest solution (easier than to try and get rid of that Perl dependency in the LibreOffice build machinery, that is) is to download it and make it available to the build via the PERLLIB environment variable.

Second, we need the LibreOffice sources themselves. The current master branch has all the necessary changes needed for a Flatpak’ed LibreOffice (as will the coming libreoffice-5-2 branch).

Third, we need to fetch LibreOffice’s external dependencies. LibreOffice has a long list of external projects that it can either use from the underlying system or build/bundle itself. Those external projects covered by Flatpak’s org.gnome.Platform runtime are taken from there, but whatever remains is bundled with the LibreOffice app. The sources for these external projects are normally downloaded during the build, but an xdg-app build does not have network connectivity, so they need to be downloaded upfront. So bootstrap enough of a LibreOffice build here to execute the make fetch part.

Fourth, LibreOffice is built in xdg-app. The choice of building against the org.gnome.Platform 3.20 is somewhat arbitrarty, but it’s the latest revision available. And given LibreOffice’s strong GTK3 support (which e.g. also enables running on Wayland), this should make the resulting app more versatile than basing it on the more fundamental org.freedesktop.Platform. Building LibreOffice doesn’t exactly follow the make && make install mantra, but there happened to already be a make distro-pack-install target that produces the build artifacts in (almost) the right way for our purposes here.

Fifth, the build artifacts from the previous step are assembled in the way xdg-app expects them. Some of the metadata desktop and icon files need to be renamed, to match xdg-app’s expectation that metadata files belonging to the org.libreoffice.LibreOffice app have names actually starting with “org.libreoffice.LibreOffice”.

Finally, everything is bundled up into a LibreOffice.flatpak that can be distributed to users, who can then install it with xdg-app install --bundle LibreOffice.flatpak.

The bundle contains all the available LibreOffice localizations. It doesn’t make that much of a difference for the size of the resulting LibreOffice.flatpak, and should be easier to handle for both producers and consumers than to provide dedicated single-language apps. For reasons of size, the help content is not bundled, though; the intent is to (transparently) use the online help content. However, one caveat with the current state of xdg-app is that an app cannot reach out to other applications on the machine via xdg-open (a portal will be needed for that). When asked to process “external” URLs (e.g., when clicking on a hyperlink in a text document, but also when accessing the online help), LibreOffice tries to pass those URLs to xdg-open, but that doesn’t work yet in xdg-app.


by stbergmann at May 13, 2016 01:52 PM

May 12, 2016

Stephan Bergmann

Between an assert and a [[fallthrough]]

LibreOffice now has Clang -Wimplicit-fallthrough enabled to catch places where a break has been missing between cases in a switch statement. See “Re: clang -Wimplicit-fallthrough and missing breaks” for some further details.

Of course, a code base as large as LibreOffice has quite a number of places where such fall-through from one case to the next is intentional, and where warnings thus need to be suppressed. The solution is the [[clang::fallthrough]] annotation (which will be available as plain [[fallthrough]] in C++17), wrapped up as a SAL_FALLTHROUGH macro for now (so it doesn’t confuse other compilers).

All fine and dandy.

Until you realise that there is quite a number of places like the following in the code base:

Foo * p;
switch (kind) {
default:
    assert(false); // cannot happen
case Kind1:
    p = new Foo(1);
    break;
case Kind2:
    p = new Foo(2);
    break;
case Kind3:
    p = new Foo(3);
    break;
};
p->foo();

Maybe kind is of an enumeration type that can only legitimately take on one of the values Kind1Kind3 (see “”enum union” with set of values restricted to exactly its enumerators?” for a discussion how such a type cannot reasonably be modeled in C++), or it is a type that can take on a wider set of values, but some invariant guarantee is that it will only take on values Kind1Kind3 here. Regardless, some compilers will warn about unhandled cases, and/or about p being used uninitialized in some cases. So the default assert part got added at some point in time, logcially marking any unhandled cases as unreachable. If a compiler/NDEBUG-configuration combo is smart enough to conclude that the assert is non-returning, it will not emit a warning. If, on the other hand, the compiler/NDEBUG-configuration combo assumes fall-through to case Kind1, it will not emit a warning about p being used uninitialized, either.

All fine and dandy.

Except that, in the NDEBUG case, Clang will now warn about a missing [[fallthrough]] annotation between the default branch and case Kind1. Under non-NDEBUG configuration (i.e., assert actually expands to some code), it is smart enough to conclude that the assert(false) will never return, so it concludes that there will be no fall-through, so will not warn. But under NDEBUG configuration (i.e., the assert expands to nothing), it sees an empty statement in the default branch, causing fall-through, causing a -Wimplicit-fallthrough warning.

But when you add a [[fallthrough]] annotation to appease the NDEBUG configuration, the non-NDEBUG configuration will start to complain about an unreachable [[fallthrough]] annotation (as it considers the assert to be non-returning, see above).

Caught between a rock and a hard place.

One way out is to rewrite the code as follows:

Foo * p;
switch (kind) {
case Kind1:
    p = new Foo(1);
    break;
case Kind2:
    p = new Foo(2);
    break;
case Kind3:
    p = new Foo(3);
    break;
default:
    for (;;) std::abort(); // cannot happen
};
p->foo();

The std::abort marks the default branch as dead independent of NDEBUG. The infinite loop around it is there to make even the most lame compiler aware that that statement will not return, so it will refrain from emitting a warning about p being used uninitialized. (And the default branch can now go at the end, where it feels more naturally at home.)

And no, there should be no fears that the second variant will behave differently now in production NDEBUG builds. In the first variant, should kind ever take on an invalid value, it would silently treat it as Kind1, proceeding (though, of course, proceeding in the most unfortunate of “defensive programming” ways), not (immediately) crashing in the user’s face. In the second variant, it would abort outright (“crashing in the user’s face!”, one might fear). But that’s a red herring. The assert (and, similarly, the std::abort) codifies the invariant that kind must be one of Kind1Kind3 here. So if it ever did have a different value, all bets about the state of the program would be off, anyway. And it would better fail fast.


by stbergmann at May 12, 2016 08:20 PM

Jean Hollis Weber

2016 LibreOffice Conference

In 2016, LibreOffice Conference will be hosted by the Faculty of Information Technology at Brno University of Technology, Czech Republic, and organized by OpenAlt, from September 7 to 9.

Details of Call for Papers, open until July 15, 2016, are available at:
https://blog.documentfoundation.org/blog/2016/04/08/libreoffice-brno-conference-call-for-paper/.

Registration for the conference is open at:
http://conference.libreoffice.org/2016/registration/.

by Jean at May 12, 2016 08:16 PM

LibreOffice 5.1.3 released

The Document Foundation (TDF) announced LibreOffice 5.1.3, the third minor release of the LibreOffice 5.1 family, supporting Google Drive remote connectivity on GNU/Linux and MacOS X.

LibreOffice 5.1.3 is targeted at technology enthusiasts, early adopters
and power users. For more conservative users, and for enterprise
deployments, TDF suggests the “still” version: LibreOffice 5.0.6.

LibreOffice 5.1.3 is available for download from http://www.libreoffice.org/download/libreoffice-fresh/.

by Jean at May 12, 2016 08:13 PM

Rosemary Sebastian

About this blog

Hello, I’m Rosemary, aka roses in the IRC. This year, my project proposal with LibreOffice got accepted for GSoC. In this blog, I’ll be writing mainly about my work for the project, which is “Saving ODF XML of Change-tracking as a Sequence of Pre-defined Changes“.

 

 


by Rosemary Sebastian at May 12, 2016 07:16 PM

Official TDF Blog

LibreOffice 5.1.3 available for download

wall51smallBerlin, May 12, 2016 – The Document Foundation (TDF) announces LibreOffice 5.1.3, the third minor release of the LibreOffice 5.1 family, supporting Google Drive remote connectivity on GNU/Linux and MacOS X.

LibreOffice 5.1.3 is targeted at technology enthusiasts, early adopters and power users. For more conservative users, and for enterprise deployments, TDF suggests the “still” version: LibreOffice 5.0.6. For enterprise deployments, The Document Foundation suggests the backing of professional support by certified people (a list is available at: http://www.libreoffice.org/get-help/professional-support/).

People interested in technical details about the release can access the change log here: https://wiki.documentfoundation.org/Releases/5.1.3/RC1 (fixed in RC1) and https://wiki.documentfoundation.org/Releases/5.1.3/RC2 (fixed in RC2).

LibreOffice Conference

In 2016, LibreOffice Conference will be hosted by the Faculty of Information Technology at Brno University of Technology, and organized by OpenAlt, from September 7 to 9.

Details of Call for Papers, open until July 15, 2016, are available at: https://blog.documentfoundation.org/blog/2016/04/08/libreoffice-brno-conference-call-for-paper/. Registration for the conference is open at: http://conference.libreoffice.org/2016/registration/.

Download LibreOffice

LibreOffice 5.1.3 is immediately available for download from the following link: http://www.libreoffice.org/download/libreoffice-fresh/.

LibreOffice users, free software advocates and community members can support The Document Foundation with a donation at http://donate.libreoffice.org.

by Italo Vignoli at May 12, 2016 11:03 AM

May 10, 2016

Michael Meeks

2016-05-10 Tuesday.

  • Practices with babes in the morning, mail chew, sales calls, built ESC bug stats, admin; customer call.

May 10, 2016 09:00 PM

Andreas Mantke

Further Work On The New Extensions And Templates Website

I worked further on the Plone add-ons for the new LibreOffice extensions and templates website and made some changes to the view templates for projects and releases. It’s easier to theme them now. I’ll push a new release of the add-on for the templates part to the ‚cheeseshop‘ during the next days.

by andreasma at May 10, 2016 08:10 PM

May 09, 2016

Michael Meeks

2016-05-09 Monday.

  • Mail chew; project planning, two team calls, and more calls in between more mail chew.

May 09, 2016 09:00 PM

LibreOffice Design Blog

Welcome, GSoC students!

Every year Google runs a Summer of Code (GSoC) and as with every year, The Document Foundation is one of the major participating open source organizations. From a total of 91 proposals, 11 have been accepted this year and we …

by The LibreOffice Design Team at May 09, 2016 10:44 AM

May 08, 2016

Michael Meeks

2016-05-08 Sunday.

  • Tired; out to NCC; home, fine lunch, slugged non-vigorously in the garden. Watched David Copperfield in the afternoon;

May 08, 2016 09:00 PM

May 07, 2016

Michael Meeks

2016-05-07 Saturday.

  • A weekend - nice; drove to Leiston Abbey with M&D. for Bruce & Anne's anniversary. Got instruments unpacked, quick quarter practice.
  • A lovely family meal, lots of distant relatives, and new people, babes played three quartet pieces beautifully; a Polka & Fiesta from Shiela Nelson and, a simple Bartok piece.
  • Back to Bruce & Anne's in a car full of balloons for a relax, some tea etc.

May 07, 2016 09:00 PM

Charles Schulz

Not so fast, open standards!

My friend Andrew Updegrove wrote a surprising essay in his latest blog post about the irrelevance of open standards. More exactly his point, if I understood correctly, was that open standards were becoming irrelevant as a topic as everyone is using and relying on them, and the software industry can no longer afford to play the game of vendor lock-in towards customers, partners and competitors. If that’s Andy’s opinion I happen to disagree with it, but only partially. Let me explain.

Open Standards fading into oblivion as something that’s not interesting and yet so mundane because everyone would rely on them is somewhat of a good news I think. It is likely that some parts of the industry, such as cloud computing players, cannot afford to “invent” brand new proprietary platforms. Whatever you do, if this particular case is an example, is to design and develop a platform, an infrastructure or a service that is either OpenStack based, or at least fully capable of interfacing itself through Swift, AWS, Azure compatible or otherwise open APIs. While these are not all open standards, it’s a good thing: downstream players want to be compatible, but the upstream, major cloud technologies are open to some large extent as well as it is in their interest to be used and relied upon by the largest part of the market.

There are however some hiccups with vendor lock-in, in cloud computing or elsewhere. It just hasn’t disappeared. The lock-in still exists through proprietary or otherwise unimplementable file formats; through undocumented protocols and weak or non existent reversibility clauses. Vendor lock-in has not gone away, it has become more subtle by moving up the ladder. If your entire business processes are hosted and run by a cloud service provider there may be some good reasons for you to have made that choice; but the day the need for another provider or another platform is felt the real test will be to know if it is possible to back up your data and processes and rebuild them elsewhere and in a different way. That’s an area where open standards could really help and will play an increasing role. Another area where open standards are still contentious is multimedia: remember what happened to Mozilla in 2015 when they chose to embed proprietary, DRM-riddled codecs because of industry pressure.

Now Andrew suggests that the market is turning to FOSS the same way they first turned to open standards. True enough, FOSS has never been as popular as it is today, but I do not believe for a moment that it is because I.T. professionals or their clients understand what Free & Open Source Software is. That’s unfortunate of course, and we do need to keep in mind that open standards and FOSS, while being quite compatible, are two widely different things.

To come back to the original point, I believe something more incidental may explain his perception. ODF-logoFrom about 2006 to 2010, the world of open standards was full of exciting initiatives, global battles for market domination or liberation. Let’s mention a few of these: html5, microformats, RDF, ebXML and of course ODF, with the OOXML saga. That’s a lot in 4 to 5 years even for the tech industry. In some cases these standards have defined today’s state of the art, in others, they’re found anywhere on the Internet and the enterprise. After these years, open standards continued to grow of course; but the politics cooled down a bit and the bubble deflated.

Open standards are not going away, they still matter and I’m sure they will come back in the spotlight just like with pretty much everything in the I.T. industry. Look, we’re talking again about A.I. I can’t wait for the moment we’ll be bombarded by some paradigm shift in e-commerce or with the fat client as in, fat client and thin server in opposition to the thin client and the fat server where all the logic comes from the server. But I digress. Open standards help everyone who want to have a part to play in the game. Whether that standard ends up being used or not, replaced or opposed by another open standard is not what matters: that’s the life of standards. I’m confident we will see their importance being highlighted again for everyone soon or later.

by Charles at May 07, 2016 09:10 AM

May 06, 2016

Michael Meeks

2016-05-06 Friday.

  • Up; lovely breakfast with Kendy, Petra & family. Some great music-making going on too, wonderful. Bid a hurried 'bye, and caught a bus/tram/bus/aeroplane back home. Worked away at the E-mail backlog on the plane variously.
  • Parents over in the afternoon; lovely to see them - time together in the evening.

May 06, 2016 09:00 PM

May 05, 2016

Jiri Eischmann

Libocon 2016: accommodation

We’re progressing with the organization of LibreOffice Conference 2016 in Brno. Italo Vignoli of The Document Foundation visited Brno last month, we showed him the venue and also places where we could hold a party, have a hacknight etc.

Recently we got a special discount for LIBOCon attendees from Vista Hotel. The hotel was recently renovated and is one of the closest hotels to the venue (15-minute walk or 2 stops by tram). The price we got is very good for the **** standard. You can find more info at the conference website and you can already book rooms.

We’re also looking for a low-cost option (most likely student dormitories) for those who don’t want to spend much money on accommodation and don’t require hotel comfort.

As the conference is getting closer we will publish more useful information for attendees on the conference website, stay tuned. We’ve also created a group chat for conference attendees on Telegram. You can ask us any questions there or chat with other attendees.

libocon16-logo


by eischmann at May 05, 2016 01:24 PM

May 03, 2016

Gülşah Köse

LibreOffice Hackfest Ankara, Turkey 2016

LibreOffice Hackfest Ankara was held for the first time in Turkey between on 29th April and 1st May sponsored by TUBITAK (Scientific and Technological Research Council of Turkey). Michael Meeks, Markus Mohrhard and Jan-Marek Glogowski came to Ankara, Turkey for sharing their knowledge with us about LibreOffice. 20~ people attended the event.

29th April:
  • Met with each other.
  • Michael and Markus made presentations about following topics
    • Solving arbitrary problems from a standing start - Real word engineering
    • LibreOffice code structure
    • LibreOffice core classes
    •  Automated testing
    •  Calc & Chart2
    •  ODF and OOXML in LibreOffice
    •  Data for LibreOffice developers
30th April and 1th May:
  • Coding and coding :)
 Hackfest was so beneficial for all attendees. We can get help from irc and mailing list but being together accelerated all of us. Michael, Markus and Jan were very friendly and helpful developers so we left hackfest very happy. We are going to go on contributing and spreading LibreOffice in Turkey.

Finally i want to say that time is the most precious thing we have so thanks to Michael, Markus and Jan for spearing time to us and many thanks to TUBITAK for sponsorship.

 And some photos \o/















by Gülşah Köse (noreply@blogger.com) at May 03, 2016 10:17 PM

May 02, 2016

Miklos Vajna

Classification toolbar in LibreOffice

In the past few posts in this blog I wrote about various digital signing-related improvements that will land in LibreOffice 5.2. In this post I would like to cover an other aspect of helping secure document handling: classification. First, thanks to the Dutch Ministry of Defense who made this work possible (as part of a project implementing trusted signing and communication in LibreOffice) in cooperation with Nou&Off. The basic idea is that in case the user is required to follow a policy when editing a document, then LO can help the user respect these rules in case LO is informed about the rules.

Luckily TSCP produced a number of open standards around this, which LO can implement without going after a specific vendor. For the scope of this post, two of them are interesting:

So how does this look like? View → Toolbars → Classification can enable a toolbar that’s disabled by default:

It has a list box that contains the categories described by the BAF policy. LO comes with such an example policy by default, that’s why you can see categories there already. If you want to use your own policy, you can do so: Tools → Options → LibreOffice → Paths has a Classification row to configure a custom policy:

And if you select the Internal Only category, you’ll see most of the features described by a category: it can add an info-bar (UI only), header/footer fields and a watermark (stored in the document) as well:

I would like to point out that the watermark is a proper scalable customshape, not a poor bitmap. :-) Perhaps this part could be extracted to a separate Add Watermark feature later, as I think it’s quite useful on its own as well.

Finally, one feature is that LO knows how secure the document is once it has a classification category, which means a classification scale and level. For two documents that have the same scale, LO can detect if the user would accidentally try to leak sensitive content from a document with higher classification level to a document that has a lower one. This is implemented when copy&pasting:

Most of these features work in all Writer, Calc and Impress. The header/footer fields and the watermark are Writer-only, and also Calc/Impress does classification checks only in its internal copy&paste code (e.g. not when doing paste special and choosing RTF).

Putting all of these together, LO can now help users required to follow classification rules in a number of different ways, as long as the rules they have to follow are available as a BAF XML policy. As usual, you can try this right now with a 5.2 daily build. :-)

May 02, 2016 06:50 AM

May 01, 2016

Charles Schulz

The Thunderbird hypothesis

(NB: the opinions expressed in this post are entirely mine and do not necessarily represent the views of the Document Foundation.)

A few days ago Mozilla published a study by Simon Phipps about the possible choices of entities that could host the Thunderbird project. The finalists, for the lack of a better word, were the Software Freedom Conservancy, the Mozilla Foundation (working on different terms with the Thunderbird project) and the Document Foundation.
I’m not going to write about which one I think is the best for the Thunderbird project for two reasons: I think the question itself is quite complex and I do not claim to know the Thunderbird community and project that well. That being said, each possible choice seems very interesting and exciting for Thunderbird in my view. image-of-mozilla-thunderbird-logo5141-580x358

Should the Document Foundation be considered as the final choice for Thunderbird, here’s my personal opinion on what challenges and opportunities await the Thunderbird project.

Let the contributors speak first

It sounds either like something obvious or someting that should have been already asked. To my knowledge, however, nobody has asked the community of contributors of Thunderbird if they have a clear opinion on the path to a (brighter) future. There’s more. Whatever the final choice of entity that will be made, Thunderbird should actually agree to that choice. And at least in the case of the Document Foundation, I believe it would only be logical that the members of the Document Foundation decide on whether it is a good idea for themselves.

One implied matter here is that the Thunderbird project should have a precise idea on who his actual contributors are, and from that data extract some notion on who can work on what, for how long and with what capability. What I’m trying to suggest here is that it is important to know where you’re starting from so that you can also tell what’s the more urgent tasks, technical or logistical.

Show me the code

When the LibreOffice project and the Document Foundation were started, we made sure code was available for download since the very first day. The reason we did this was twofold. We wanted to show we were credible from day one and we wanted to attract developers. Code is a great way to meet these two requirements: it reassures people and show potential developers you’re not all talk; in fact, you have something to show and potential itches to scratch. I do not suggest the Thunderbird project should have a fresh beta from day one. It should however have a public repository that shows some activity. Even better, a list of “low-hanging fruits”, issues or bugs that are relatively easy and fun to tackle would be a great way to attract developers.

The master of your ship

In the case of the Document Foundation, and to the best of my knowledge, the Thunderbird project will benefit from several key advantages: resources (both logistical and to some degree, financial), a very large autonomy (if not downright independence) and the ability and support to grow as a project and a community. What the Document Foundation will not provide, should it become the final choice of the Mozilla foundation as the next home for Thunderbird is an important point I fear many LibreOffice_Initial-Artwork-Logo_ColorLogoContemporary_500pxpeople have overlooked or have not understood.

  • The Document Foundation has no developers to offer, no contributor to be produced by magical means. Being a project of the Document Foundation allows you to be part of it as individual contributors and to set your project free. But neither money, nor code will start to rain on Thunderbird as a result. Signing up with the Document Foundation implies the Thunderbird project realizes hard work lies ahead.
  • The developers of the LibreOffce and the Document Liberation projects will not all of a sudden show up, fix your small XPCOM and XUL inconveniences and work on the remaining tasks for the project. The Thunderbird project, hopefully gaining developers in the transition towards the Document Foundation, will have to deal with its own technical challenges and opportunities on its own.
  • The Document Foundation will not dictate the roadmap and technological options for Thunderbird. Of course, I’m rather confident several LibreOffice developers can think of possible opportunities for technical cooperation and even some sort of loose integration between LibreOffice and Thunderbird. But that’s the extent of it: if there are enough developers interested from both sides, things will start happening. If not… it won’t happen, and nobody should feel sorry about it.

Opportunities

If you have been reading this post until this very point you may be wondering whether I would actually like to see Thunderbird join the Document Foundation. Of course I would be very happy to see Thunderbird join us and transform itself into a strong, community-led project that will put my previous posts about why I don’t like to use it to rest and to shame. But I also happen to think that it is crucially important for everyone involved (from Thunderbird to the Document Foundation to the Thunderbird users themselves) to get it right from the start. The best home for Thunderbird is the one that will let it grow into a strong community of contributors. In order to do that the most important part does not come with the host structure but from within Thunderbird itself. I strongly believe that the Document Foundation is ideally positioned to be that home. Once the contributors are active, the technical debt is being effectively addressed, then I am confident that the much awaited synergies will start to show: document management, email editors and outliners, common packaging, LibreOffice OnLine and even an online Thunderbird continuum with their desktop versions, Android ports…

Seriously, the road ahead is bright and clear. But until we reach that point, there are some real challenges to overcome. I wish the best to Thunderbird, sincerely, whatever will be the decision of Mozilla.

by Charles at May 01, 2016 09:23 PM

Andreas Mantke

Test-Website For LibreOffice Educational Portal

During the German speaking LibreOffice community we discussed to work on an educational site. I made a first draft of a Plone site for such a LibreOffice educational portal and did some further work over the last weeks. I committed my code to the github repository of the Document Foundation.

Today I run buildout on the educational site again and it is in sync with my current development status yet. You can view the site at: http://vm141.documentfoundation.org:9090/bildungsportal/libreoffice-bildungsportal

by andreasma at May 01, 2016 06:48 PM

Florian Reisinger

OOXML Strict and MS Office 2010

One of the benefits of being a student is getting Office 365. I also have Office 2010 so that leaves me with bot Office 2010 and 2016.

Recently I tried to save a Excel file in OOXML Strict and confront my 2010 edition Excel with it.

<figure class="wp-caption alignnone" data-shortcode="caption" id="attachment_1102" style="width: 1920px">Unbenannt<figcaption class="wp-caption-text">This file has been created with a newer version of MS Excel – For opening this file you need a converter. Would you like to download it from Office.com?</figcaption></figure>

The hilarious thing is the following image:

<figure class="wp-caption alignnone" data-shortcode="caption" id="attachment_1106" style="width: 653px">Unbenannt<figcaption class="wp-caption-text">Source: https://blogs.office.com/2012/08/13/new-file-format-options-in-the-new-office/</figcaption></figure>

 

 

So my Office 2010 should be able to open the Strict OOXml without problems (with this some month old file it actually does). But why is Microsoft frightening the enduser? The best thing is the linked page (from the dialog in the first picture) “Support for Office 2003 has ended“. If you need the converter, it can be found here. UPDATE:Removed link as it broke my Office 2016!!!!

And finally the sentence you were waiting for: Waaait, Office 2010 can open the OOXML strict standard, but not the file saved with Office 2016 with “OOXML strict”. So the “OOXML strict” is not Standard (or there is a biiig bug in Office 2010, which prevents interoperability)…..

 

 

 

 


Tagged: Excel 2010, Excel 2016, LibreOffice, MS Office, OOXML strict

by Florian Reisinger at May 01, 2016 08:36 AM

April 30, 2016

Andreas Mantke

Bildungsportal-Add-On Goes Further

I worked a bit on the way the educational add-on creates URLs for new projects. It uses the title of a project now. I added also a feature to validate the project name uniqueness. I’ll work on the view of the projects next time.

by andreasma at April 30, 2016 12:44 PM

April 25, 2016

TDF Infrastructure Status

DoS Attack on Manitu

Our Hoster Manitu is currently experiencing a DoS attack on its infrastructure. They are working on measures to fight the attack. This might affect the availability of many of our services.

by The Document Foundation at April 25, 2016 10:00 PM

April 23, 2016

Charles Schulz

The importance of the Document Liberation Project

Today I would like to focus on a quite interesting project, even though it is rarely spoken of: The Document Liberation Project. The Document Liberation Project is LibreOffice’s sister project and is hosted inside the Document Foundation; it keeps its own distinct goals and ecosystem however. We often think of it as being overly technical to explain, as the project does not provide binaries everyone may download and install on a computer. Let’s describe in a few words what it does. The Document Liberation project aims at developing filters handling various file formats. The output of the project is then reused inside LibreOffice as well as in other Free Software such as (but not limited to) Inkscape, Abiword, etc.Docliberation

Many people have files and documents that are sitting somewhere on their hard drives and that were first generated by an ancient office suite, word processor or spreadsheet application. Most of these file formats were never publicly documented. As a result, people experience vendor lock-in as they are unable to convert them in a stable, supported and open file format they can actually use. In order to solve this conundrum the Document Liberation project has a set of export filters that convert files to ODF, epub and even Abiword format. Its crownjewel, so to speak, is the set of import filters it has been collecting over the years and that it has improved. Those filters range from MS Publisher files to Clarisworks and Apple Keynote and also have many rarely used file formats. Let’s take a look at the list mentioned on the project’s website:

libwpd
Corel WordPerfect import library.
libwpg
Corel WordPerfect Graphics import library.
libwps
Microsoft Works import library.
libmwaw
A library for import of many legacy Mac document formats.
libabw
AbiWord import library.
libcdr
Corel Draw import library.
libmspub
Microsoft Publisher import library.
libvisio
Microsoft Visio import library.
libetonyek
Apple Keynote/Pages/Numbers import library.
libfreehand
Aldus/Macromedia/Adobe FreeHand import library.
libe-book
A library for import of many e-book formats.
libpagemaker
Adobe PageMaker import library.

This list is impressive and keeps growing. One may also notice the usefulness of the project for digital artists and designers. You can help the project in three ways:
* help developing these filters and libraries
* help documenting the formats the project tries to manage
* submit test documents and assess how effective the filters are in real life.

You may of course donate to the Document Foundation as well. The Document Liberation project matters a lot. It matters for many different people and for the ecosystem of desktop software relying on these files, from office suites to graphical design tool and document processors. If you feel like you could help, do not hesitate one bit, your contribution will be much appreciated and you will help liberating the world, one document at a time.

by Charles at April 23, 2016 01:46 PM

Dennis Roczek

Some updates on the TDFWIKI

Last month we had some spam attacks on our TDFWIKI. We blocked the new accounts and deleted the pages manually. A really big thank goes to cloph as he helped me and disabled the manual registration for new users when I wasn’t available.:-)

After that we had modified again our Title-Blacklist to prevent pages create with well known spam titles (mostly including phone numbers for Canada and USA, some words like phone support, printer assistance, etc.).

Now we should improve our “abuse filter” which checks every edit for spammers who try to add phone numbers to the page content itself. Sadly we realized that it prevented sophie to add and create the recordings of the BoD calls, so it got deactivated again. This is still on my todo list.

 

After rereading my “unread” planet blog post – in this case Charles’ Losing the Art of Wiki , I added as suggested by beluga / buovjaga to add yet another extension: an improvement to the RecentChanges page.


by dennisroczek at April 23, 2016 01:21 PM

April 19, 2016

TDF Infrastructure Status

Migration of Excelsior and Falco

For the migration of our virtualization servers to our own rack and the upgrade to 10G based Intranet, we plan the downtime of excelsior on April 26, 0730UTC, and the downtime of falcon on April 27, 0730UTC. The downtime should last about one hour. The vms that will be affected are:

Excelsior - April 26, 0730UTC

  • vm134 - silverstripe staging
  • vm136 - CentOS 64Bit Buildbot
  • vm141 - Plone Test
  • vm144 - Bugzilla Test instance
  • vm146 - Askbot
  • vm151 - tdf.io URL shortener
  • vm156 - testwiki
  • vm161 - blog
  • vm162 - infra-testbed
  • vm163 - wiki-test
  • vm164 - officeshots
  • vm166 - Windows 64Bit Tinderbox
  • vm169 - pootle
  • vm170 - graylog

Falco - April 27, 0730UTC

  • vm137 - CentOS 32bit buildbot
  • vm139 - Callgrind vm
  • vm140 - Callgrind vm
  • vm142 - dev-downloads
  • vm143 - devcentral,perf
  • vm145 - jenkins
  • vm147 - moztrap
  • vm148 - gerrit
  • vm150 - bugzilla
  • vm160 - floyd - saltmaster
  • vm177 - CentOS 6 baseline 32bit
  • vm178 - gerrit-test
  • vm186 - new downloadarchive
  • centOS64bit

Update April 26, 0820UTC

excelsior has been migrated. There are some slight issues regarding the intranet connection, all public services are available again.

Update April 26, 0830UTC

The newly fitted network card for excelsior seems to have one faulty port. Excelsior needs to be shutoff again to replace the interface

Update April 26, 0845UTC

A HDD on excelsior also failed during migration, it will be replaced during the second downtime.

Update April 26, 1110 UTC

Excelsior is up and running.

Update April 27, 0920 UTC

Migration of falco takes a bit longer than expected - again Network card struggles - working on it.

Update April 27, 1030 UTC

Falco is up and running.

by The Document Foundation at April 19, 2016 10:00 PM

>Marius Popa Adrian

Firebird 3.0 is released

Firebird Project is happy to announce general availability of Firebird 3.0 — the latest major release of the Firebird relational database.The primary goals for Firebird 3.0 were to unify the server architecture and to improve support for SMP and multiple-core hardware platforms. Parallel objectives were to improve threading of engine processes and the options for sharing page cache across thread

by Adrian Marius Popa (noreply@blogger.com) at April 19, 2016 02:14 PM

April 18, 2016

>Marius Popa Adrian

Firebird 3 final is about to be released

The source code was just tagged in the repository, so we can expect the final release being out in the next days. One change in the new Firebird 3 OO examples api is addition of the Services example .

by Adrian Marius Popa (noreply@blogger.com) at April 18, 2016 12:55 PM

April 17, 2016

LibreOffice Design Blog

Our Happy Hour – How LibreOffice Sidebar Tenders Properties and Functions

In March 2016, we asked the community how they use the sidebar and how they feel it should evolve. About 290 participants answered the single choice questions and around 100 answered the free text question. All in all, users want …

by The LibreOffice Design Team at April 17, 2016 08:31 PM

April 14, 2016

Miklos Vajna

OOXML signature export in LibreOffice

After adding support for reading OOXML signatures in LibreOffice, I continued with implementing OOXML signature export (as in: not only verification, but signing).

By verification, I mean that I count the signature of the input document, then compare it with an existing signature, and if they match, it is verified. This can be also called "import", as I only read an existing signature, I don’t create one. By signing, I mean the creation of a new signature, which is always good — if it isn’t, that’s a programming error. This can be also called "export", as I write the new signature into the document.

First, thanks to the Dutch Ministry of Defense who made this work possible (as part of a project implementing trusted signing and communication in LibreOffice), this included:

  • signing a previously unsigned document

  • appending a signature to an already signed document

  • removing a signature from a document with multiple signatures

  • removing the last signature of a signed document, turning it into an unsigned one

Obviously the hardest part was the initial success: signing a previously unsigned document, in a way that is accepted by both LibreOffice and MSO. One trick here is that while in ODF the signature stream is simply added to an existing document storage, in OOXML the storage has to refer to the signature sub-storage (it’s not a stream, as it has a stream for each individual signature), then it has to be signed, and finally the signature can be added to the document storage. So instead of reading the document, then appending the signature, here we need to modify the document, and then we can append the signature. By referring the signature sub-storage, I mean it is necessary to modify [Content_Types].xml (so it contains a mime type for both the .sigs extension, and also for the individual /_xmlsignatures/sigN.xml streams) and also the _rels/.rels stream has to refer _xmlsignatures/origin.sigs, which will contain the list of actual signatures. A surprising detail is that the signature is required to contain quite some software and hardware details about your environment, like monitor resolution, Windows version and so on. For a cross-platform project like LibreOffice this isn’t meaningful, not to mention we have no interest in leaking such information. So what I did instead is writing hardcoded values based on what my test environment would produce, just to please MSO. ;-)

After the initial OOXML signature exporter was ready, the next challenge was adding multiple signatures. The problem here is that you have to roundtrip the existing signatures perfectly. And when I write perfectly, I really mean it: if a single character is written differently, then the hash of the signature will be different, so the roundtrip (when we write back an existing and a new signature to the document) will invalidate the signature. And there is no way around that: the very point of the signature is that only the original signer can re-calculate the signature hash. :-) So what we do is simply threating the existing signatures as a byte array, and when writing back, then we don’t try to re-construct the signature stream based on the xmlsecurity data model, but simply write back the byte array. This way it’s enough to extract parts of the signature which are presented to the user (date, certificate, comment), and we don’t need to parse the rest.

Removing one of multiple existing signatures isn’t particularly hard, you just need to update _xmlsignatures/_rels/origin.sigs.rels and [Content_Types].xml which refer each and every signature stream. It’s a good idea to truncate them before writing, otherwise you may get a not even well-formed XML as a result.

Finally removing the last signature is a matter of undoing all changes we did while adding the first signature (the content type list and the toplevel relation list), finally removing the signature sub-storage all-together. I also factored out all this signature management code from DigitalSignaturesDialog (which is a graphical dialog) to DocumentSignatureManager, so that all the above mentioned features can be unit-tested.

Putting all of these together, LO can now do all signature add, append, remove and clean operations a user would expect from what is referred as simply OOXML signature support. As usual, you can try this right now with a 5.2 daily build. :-)

April 14, 2016 06:20 AM