The Document Foundation Planet

 

January 23, 2018

Official TDF Blog

LibreOffice community focus: Design

LibreOffice’s design community works on the software’s user interface (UI), improving its usability and accessibility. With LibreOffice 6.0 due to be released at the end of the month, we talked to members of the community to get their perspectives on the new version…

What have you been working on in preparation for LibreOffice 6.0?

Various things, including:

  • New table styles and new gradients (click for bigger):

  • The LibreOffice 6.0 motif/splash screen:

  • And menu and toolbar improvements

What are your favourite new features in this release?

Both GSoC (Google Summer of Code) projects are really nice: the revamped customization dialog, and the special character dialog with quick access from the toolbar. In addition, there’s the ability to rotate images to arbitrary degrees, and many other small improvements.

What tools and services do you use in the design community?

At the moment we use Balsamiq Mockups, but next we switch to Pencil. In addition, we use LibreOffice Draw (eg for the new motif) and Inkscape. For communication, we are active on IRC (in the #libreoffice-design channel on Freenode) and Telegram.

Finally, how can people get involved with the design community?

A big thanks to the design team for their input and improvements in LibreOffice 6.0. For our final Community Focus, we’ll talk to the development community – more on that soon!

by Mike Saunders at January 23, 2018 09:59 AM

kainz.a

LibreOffice bitmap pattern

Do you like to use nice bitmap pattern in LibreOffice for area fill. So if you draw a rectangular, a start, … whatever you can use this bitmaps.

With the help of designers from openclipart, pixabay, publicdomainpictures, … I made 42 seamless area bitmap pattern but only 50% are needed. So which one do you like which one can be dropped.

image3851.jpg

Please comment to the bug reportt tdf#114817 or in the comment section. If you’d like to test them feel free to download the LibreOffice writer dokument.

by kdeonlinux at January 23, 2018 08:27 AM

January 22, 2018

Official TDF Blog

The Document Liberation project announces five new or improved libraries to export EPUB3 files and import AbiWord, MS Publisher, PageMaker and QuarkXPress documents

Berlin, January 22, 2018 – The Document Liberation Project announces five new or improved libraries to export EPUB3 and import AbiWord, MS Publisher, PageMaker and QuarkXPress files. The libraries have been originally developed for the LibreOffice 6.0 major release, but can be used by any other software thanks to the OSI (Open Source Initiative) compliant license.

libe-book exports LibreOffice ODT files to EPUB3. At the moment it offers just basic features, but development is still undergoing and new features will be added before the next major release. The library can be downloaded from https://sourceforge.net/projects/libebook/. A description of the architecture and the features is available here: https://vmiklos.hu/blog/basic-epub3-export.html.

libabw imports AbiWord documents, and can be downloaded from http://dev-www.libreoffice.org/src/libabw/. The library home page is at https://wiki.documentfoundation.org/DLP/Libraries/libabw.

libmspub imports MS Publisher documents, and can be downloaded from http://dev-www.libreoffice.org/src/libmspub/. The library home page is at https://wiki.documentfoundation.org/DLP/Libraries/libmspub.

libpagemaker imports PageMaker 6/7 documents, and can be downloaded from http://dev-www.libreoffice.org/src/libpagemaker. The library home page is at https://wiki.documentfoundation.org/DLP/Libraries/libpagemaker.

libqxp imports QuarkXPress 3.1/4.1 documents and templates and can be downloaded from http://dev-www.libreoffice.org/src/libqxp/. The library home page is at https://wiki.documentfoundation.org/DLP/Libraries/libqxp.

The Document Liberation Project was created to empower individuals, organizations and governments to recover their data – hidden inside obfuscated proprietary file formats – and migrate them into perennially accessible standard file formats.

To return effective control over content to the real authors, the Document Liberation Project develops software libraries that can be used by applications to read data in proprietary formats. The libraries are currently used by Calligra, Inkscape and Scribus.

by Italo Vignoli at January 22, 2018 12:38 PM

Sunday Marketing #3

Google Trends is a service which compares end user searches for specific terms, and as such is a useful marketing tool to get some insight on the awareness of LibreOffice in comparison with other applications. I have compared the five alternatives to the leading office suite during the last 12 months: LibreOffice is leading, followed – as expected – by OpenOffice and WPS Office. LibreOffice is also leading in term of geographical coverage.

by Italo Vignoli at January 22, 2018 02:00 AM

January 21, 2018

Kohei Yoshida

LibreOffice Development Talk at Triangle C++ Developer’s Group

It was a pleasure to have been given an opportunity to talk about LibreOffice development the other day at the Triangle C++ Developer’s Group. Looking back, what we went through was a mixture of hardship, accomplishments, and learning experience intertwined in such a unique fashion. It was great to be able to talk about it and hopefully it was entertaining enough to those of you who decided to show up to my talk.

Here is a link to the slides I used during my talk.

Thanks again, everyone!

by Kohei Yoshida at January 21, 2018 03:30 PM

January 18, 2018

Michael Meeks

2018-01-18 Thursday

  • Mail chew, call with HSBC - trying to persuade me to invest in bonds at 0.7%, when the UK Government is offering 2.2% direct at retail; weird. Marketing & Sales call. Lunch.
  • Mail, bits of code, bugs, ESC call, Advisory Board call, sales call.
  • FOSDEM put up some of my incoherent ramblings - looking forward to seeing people in Brussels!
  • Washing machine pump started to make noises as if a hair-band has got into it (urgh), will attempt dis-assembly. Thrilled to discover that the pump (and filter) are trivially accessible and easy to clean in contrast to the last machine where the pump was carefully concealed inside a razer-sharp metal box with rubber and pipe clips everywhere.

January 18, 2018 08:18 PM

Official TDF Blog

Wednesday Community #2

The sun never sets on the LibreOffice community, as there are always active members in some countries. Unfortunately, only a minimal part of this global effort is reflected on this blog, which should feature all activities and achievements. In order to get to this objective, we warmly invite all native language communities around the world to send us a short synopsis and a couple of pictures – if available – every time they do something significant for LibreOffice: a talk at a conference, a booth at an exhibition, a meeting, a conference, a localization sprint, or any other event. The same for achievements such as LibreOffice adoptions by government bodies, central or local public administrations, or large enterprises. Just send an email to media@documentfoundation.org, and we will take care of writing the blog post (if necessary, we will translate the local language to English).

by Italo Vignoli at January 18, 2018 02:07 AM

January 17, 2018

Michael Meeks

2018-01-17 Wednesday

  • Mail chew; patch review, estimation work, catch-up with Miklos. Booked flights to the Univention Summit before FOSDEM - should be great.

January 17, 2018 09:00 PM

Official TDF Blog

LibreOffice community focus: QA (quality assurance)

With LibreOffice 6.0 due to be released at the end of the month, we’ve been talking to various communities involved in the project. In the last couple of weeks, we’ve chatted with the localisation and documentation teams, and today it’s the turn of QA (quality assurance), which is coordinated by Xisco Fauli

What has the QA community been working on in preparation for LibreOffice 6.0?

During the development of LibreOffice 6.0, three Bug Hunting Sessions were held (6.0 Alpha1, 6.0 Beta1 and RC1), the last one just two weeks ago. There was also a parallel event organized by Muhammet Kara in Ankara, where volunteers gathered to test LibreOffice 6.0 RC1. Besides that, the QA team is constantly testing the latest daily builds, testing new features, and triaging the bugs reported on Bugzilla.

What are your favourite new features in this release?

That’s a difficult question, especially taking into account all the improvements done in this release to LibreOffice Android Viewer, to LibreOffice Online or the work done by the Google Summer of Code students among others. But if I had to choose one, I think I’d go for the characters dialog refactoring done by Akshay Deep and the UX (user experience) team, as this is probably the feature I will use the most in the near future. Here’s how it looks:

What tools and services do you use in the QA community?

A very handy tool recently completed by Markus Mohrhard is the automated updater for Windows and Linux, which allows the QA team to test daily builds without having to manually download the latest build every time.

This is very practical as testers no longer need to worry about constantly updating to the latest build, and can focus more on testing the program instead, assured that they are testing changes done to the code just the day before.

This tool was presented at the beginning of the LibreOffice 6.0 development cycle, and I believe it will have a very positive impact on the quality of 6.0 as it shortens the time between a problem being introduced in the code, and the time it’s found.

Another tool we’ve been using for some time now is the bibisect repositories, which allow us to find the exact code commit where a bug was introduced, increasing the chances that the bug gets fixed and reducing the time until it gets fixed.

Another tool which is fulling working now is a set of scripts called office-interoperability-tools that we use to automatically find document layout regressions in the master code branch compared to other office suites (in our case we use MS Office). Right now we use it with 8,450 files, and I believe it will also have a positive impact on the quality of LibreOffice 6.0.

Finally, it’s important to mention the main tool used in QA, Bugzilla, the place where all bugs are reported and triaged. Then there’s the wiki page where the QA documentation can be found, and testlink, the application to manage manual tests.

Finally, how can people get involved with the QA community?

The’re many ways one can help LibreOffice QA. Probably the simplest one would be: download the latest pre-release build (LibreOffice 6.0 RC2 as of today), install it and use it as you would use LibreOffice in your daily basis (but take into account it’s still a pre-release, so it’s not recommended to use it with important documents). If you find anything working incorrectly, please report it to Bugzilla.

On the other hand, if you prefer to follow a set of manual tests, you can use testlink (see the documentation for that. We also need help to triage bugs that are not-yet-confirmed, or retest old bugs to see if they might have been fixed.

Lastly, if you’re looking for something especially exciting things to do, you can help us to test daily builds, bisect bugs or write UI-tests. Don’t hesitate to join the #libreoffice-qa channel and say hello. We’ll be grateful to help you with any question or problem you have!

Much gratitude to Xisco and the diligent QA community for helping to make LibreOffice 6.0 a solid release. Their efforts are appreciated by users across the world. Next up, we talk to the design and development communities – more on this blog very soon…

by Mike Saunders at January 17, 2018 04:56 PM

January 16, 2018

Michael Meeks

2018-01-16 Tuesday

  • Sync with Andras, Jona, mail chew, commercial call, partner call, read reams of framework contract-ness. Dinner.
  • Debugged some JS horror - where we end up with a 'this' referring to an entirely different object in a class' method - type unsafety to the N'th.

January 16, 2018 09:00 PM

January 15, 2018

Michael Meeks

2018-01-15 Monday

  • Sync. with Miklos, Kendy, code review, lunch, mail, sync with Andras, customer call.

January 15, 2018 09:00 PM

Andreas Mantke

Finished Removing Not Used Accounts

It took some time to remove a lot of accounts from the LibreOffice extensions and templates website that are not used for contributions to the site and the LibreOffice eco-system. I finished this work during already.

It always possible and easy to create a new account on the site, if a new user / community member need one to contribute a LibreOffice extension or template project / release.

by Andreas Mantke at January 15, 2018 08:43 PM

January 14, 2018

Michael Meeks

2018-01-14 Sunday

  • Played bass & sang at All Saints, christening & Max spoke. Back for roast lunch, slugging, playing of 'Job Simulator' by babes, Adventures on Odyssey in the evening; put babes to bed.

January 14, 2018 09:00 PM

Andreas Mantke

Removing Not In Use User-Accounts

I created already some scripts to work on the user database of the LibreOffice extensions and templates website.  I got some different list of the users (e.g. contributing and not contributing users). I monitored this different groups of users for a longer time now. Today I used another script that I already created and began to remove a list of users with no contribution to the site.

by Andreas Mantke at January 14, 2018 05:37 PM

January 11, 2018

Miklos Vajna

EPUB3 export improvements in Libreoffice Writer, take two

I worked on improving the EPUB3 export filter in LibreOffice further recently. First, thanks to Nou&Off in cooperation with a customer who made this work possible. Since the previous blog entry there have been a number of improvements around a next set of topics.

Cover images

https://farm5.staticflickr.com/4760/38920770224_b247fa89c4_o.png

It is now possible to specify a cover image for the exported EPUB file. Given that a cover image is not naturally part of the Writer document model, I introduced the concept of a media directory for the EPUB export. The media directory is a directory next to the source file, with the <file name without extension> name. If that directory contains a file named cover.svg (or .gif, .jpg, .png), the exporter will automatically use it. Otherwise you can customize this default.

The picture shows two EPUB files in Readium with different cover images.

Improved metadata support

https://farm5.staticflickr.com/4603/38920770174_142950782e_o.png

It’s quite frequent that you are technically author of a document, but the logical author of the book is somebody else. Same for the date of the book, and so on. So the EPUB export dialog now has support for overwriting the defaults coming from the Writer document model. For mass-conversion of documents it’s possible to place a <file name without extension>.xmp file in the media directory and XMP metadata from that file will also overwrite metadata coming from the document model.

The picture shows the extended EPUB export options dialog.

Footnotes and image popups

https://farm5.staticflickr.com/4612/38920770144_e90e2a8e92_o.png

I’ve added support for footnotes. As a special case of this, image popups on images and text is now supported. This works by placing a relative link on a text portion or on an image, and placing an image with the same name (e.g. in high resolution) in the media directory. In this case the EPUB export will bundle the image from the media directory inside the EPUB file and clicking on the text or image will open the bundled image in a popup (or in some other container, depending on how your reader interprets footnotes).

The picture shows such a popup in Microsoft Edge.

Fixed layout

https://farm5.staticflickr.com/4604/38920770104_108465bda1_o.png

The EPUB3 fixed layout is quite similar to PDF, just it is built on top of XHTML and SVG. Possible use-cases for this can be:

  • exporting a document where presenting the content as reflowable text would be misleading (e.g. comic books), but the publisher of the book only works with EPUB (reflowable or fixed layout, but no PDF)

  • printing (again, in case for some reason you want to avoid PDF)

These might be very specific situations, but luckily supporting them is not too complex. I implemented an approach very similar to the PDF export, where we export individual pages of the Writer document’s layout as a metafile, and then consume that — this time with the SVG export. Building on top of the existing Writer layout and SVG export means the hard work is really done by these components, the EPUB fixed layout export just puts these together.

The picture shows a Writer document with a table of contents containing page numbers, a header and a footer in Readium.

All this is available in master (towards LibreOffice 6.1), or you can grab a daily build and try it out right now. :-)

January 11, 2018 11:25 AM

January 08, 2018

Tor Lillqvist

LibreOffice Vanilla 5.4.4 released on the Mac App Store

Collabora has now released LibreOffice Vanilla 5.4.4 on the Mac App Store. It is built from the official LibreOffice 5.4.4 sources. If you have purchased LibreOffice Vanilla earlier from the App Store, it will be upgraded in the normally automatic manner of apps purchased from the App Store.

LibreOffice Vanilla from the Mac App Store is recommended to Mac users who want LibreOffice with the minimum amount of manual hassle with installation and upgrades. If you don't mind that, by all means download and install the build from TDF instead.

We would have loved to continue to include a link to the TDF download site directly in the app's description, as we have promised, but we were not allowed to do that this time by Apple's reviewer.

Because of the restrictions on apps distributed in the App Store, features implemented in Java are not available in LibreOffice Vanilla. Those features are mainly the HSQLDB database engine in Base, and some wizards.

This time we include the localised help files, as there were some issues in accessing the on-line help.

Since the LibreOffice Vanilla 5.2 build that was made available in the Mac App Store in September 2016, there have been a few Mac-specific fixes, like the one related to landscape vs. portrait mode printing on Letter paper. There are more Mac-specific bugs in Bugzilla that will be investigated as resources permit.

Some fine-tuning to the code signing script has been necessary. For instance, one cannot include shell scripts in the Contents/MacOS subfolder of the application bundle when building for upload to the App Store. This is because the code signatures for such shell scripts would be stored as extended attributes and those won't survive the mechanism used to upload a build to the App Store for review and distribution. (For other non-binary files, in the Resources folder, signatures are stored in a separate file.)

We also have made sure the LibreOffice code builds with a current Xcode (and macOS SDK).

by Tor Lillqvist (noreply@blogger.com) at January 08, 2018 12:24 PM

January 07, 2018

Andreas Mantke

Update Of Software For The LibreOffice Extensions Website

I worked on a small update of the Plone add-ons that I created to run the new LibreOffice extensions and templates website. The source code of this update went to the github repository of the Document Foundation and I published a new release of the Plone add-ons on the cheeseshop.

I updated the LibreOffice extensions and templates website with the new code of the add-ons via buildout today.

by Andreas Mantke at January 07, 2018 08:48 PM

January 01, 2018

Eike Rathke

Happy New Year 2018

Today is Sweetmorn, the 1st day of Chaos in the YOLD 3184

by erAck (23@127.0.0.1) at January 01, 2018 12:38 PM

December 29, 2017

Andreas Mantke

Update LibreOffice On Debian Stretch

I added a new repository for backports to my fresh installed Debian Stretch on my old netbook and installed LibreOffice 5.4.4 from this backports. The netbook is running the current stable LibreOffice yet.

by Andreas Mantke at December 29, 2017 05:48 PM

December 28, 2017

Eike Rathke

Germany is still an underdeveloped digital country on 4G mobile networks

15GB per month for €25, while in the neighbor country Denmark you get Unlimited GB for the same price..

One tariff with €199.95 for Unlimited GB in Germany btw... statistics of Nov-2017 with data of 2016.

by erAck (23@127.0.0.1) at December 28, 2017 10:39 PM

Andreas Mantke

Installed Debian Stretch On My Old Netbook

I installed the Debian stretch release on my old Medion netbook from 2008. I choosed the desktop Xfce, because it is much smaller than KDE or Gnome. I used an USB Blue ray player and the netinstall cd for the installation and got further packages from a mirror. The default installation contains LibreOffice version 5.2.7.

by Andreas Mantke at December 28, 2017 09:57 PM

December 24, 2017

kainz.a

LibreOffice Tabbed Toolbar Compact

The Notebookbar implementation Tabbed Compact is finished and can be tested. Download LibreOffice Master for

Configure Notebookbar:

  • Tools -> Options -> Advanced -> Enable experimental features
  • View -> Toolbar Layout -> Notebookbar
  • View -> Notebookbar -> Tabbed Compact

And this is how it will look like

The idea of the Toolbar is that you get all actions grouped in different tabs. The benefit is that there is enough space for most actions from LibreOffice and you can show action icons and labels. In addition the UI is sizable.

Download and test it.

by kdeonlinux at December 24, 2017 10:34 AM

December 22, 2017

LibreOffice Design Blog

LibreOffice mascot – lesson learned and an apology

With many approaching the holiday season, it looks like the heated discussions about the LibreOffice mascot have settled down. It is probably too early to re-launch the project, as memories of what has happened in October and November are still rather fresh, and so we would like to share our thoughts and plans on this project with you before we the next steps are taken.…

The post LibreOffice mascot – lesson learned and an apology appeared first on LibreOffice Design Team.

by Italo Vignoli at December 22, 2017 06:37 PM

December 14, 2017

kainz.a

Elementary LibreOffice

ElementaryIcons.png

Two months ago I start to finalize the existing Elementary icon theme for LibreOffice. It’s about 2.000 icons and now they are available in LibreOffice 6.0 beta. In addition all icons are available as svg file so it can be used and edit in an easy way.

Please download and test LibreOffice 6.0 beta to give feedback. You switch the icon theme with Tools -> Options -> View -> Icon Style. We talk about a lot icons not all are perfect. Feedback is always welcome.

Test LibreOffice 6.0 beta

Mary Christmas and an shiny new year with LibreOffice 6.0.

 

 

by kdeonlinux at December 14, 2017 09:10 AM

December 12, 2017

Muhammet Kara

Status Update: The Customize Dialog since GSoC17

I would like to give some info about the current status of and the changes in the Customize dialog after GSoC. Context & History During the summer, I participated in Google Summer of Code 2017 with the project “Revamp the Customize Dialog”, and worked to modernize LibreOffice’s Customize dialog to improve user experienceby giving it a better look, and making it more user friendly and accessible, while eliminating some under-the-hood bugs at the same time.

by Muhammet Kara (muhammetk@gmail.com) at December 12, 2017 12:00 AM

December 05, 2017

Miklos Vajna

EPUB3 export improvements in Libreoffice Writer

I worked on improving the EPUB3 export filter in LibreOffice recently. First, thanks to Nou&Off in cooperation with a customer who made this work possible. Since the previous blog entry there have been a number of improvements around 4 topics.

https://farm5.staticflickr.com/4540/38847800651_d5271ced3a_o.png

The character properties of link text is now handled correctly, in the above example you can see that the text is red, and this comes from a character style.

Improved table support

Previously the support for tables was there just to not loose content, now all kinds cell, row and table properties are handled correctly. A few samples

  • custom cell width:

https://farm5.staticflickr.com/4566/38847800611_38b8483d7f_o.png
  • custom row height:

https://farm5.staticflickr.com/4580/38847800521_26285a9152_o.png
  • row span:

https://farm5.staticflickr.com/4540/38847800461_359651bc3d_o.png

So the table support should be now decent, covering row and column spanning and various cell border properties.

Improved image support

Previously only the simplest as-character anchoring was supported. Now much more cases are handled. Two examples:

  • image borders:

https://farm5.staticflickr.com/4541/24975193838_94818bd1ed_o.png
  • image with a caption:

https://farm5.staticflickr.com/4568/24975193608_83239bf287_o.png

This includes various wrap types (to the extent HTML5 allows representing ODF wrap types).

Font embedding

If the user chooses to embed fonts (via File → Properties → Font → Embed), then the EPUB export now handles this. Here is a custom font that is typically not available:

https://farm5.staticflickr.com/4561/38847800811_613d6fbbd2_o.png

(The screenshot is from the Calibre ebook reader.)

All this is available in master (towards LibreOffice 6.1), or you can grab a daily build and try it out right now. :-)

December 05, 2017 10:11 AM

November 29, 2017

WorldLabel

Preparing Labels With Libreoffice Video By Bruce Byfield

How to Prepare Labels with Libreoffice.org by Bruce Byfield.

This tutorial covers using templates, how to import images and use text, in-depth instructions on using mailmerge and more.

For more reading on using labels with Libreoffice:

Creating fancy labels with Libreoffice

Mail merge address labels with Libreoffice

Working with Barcode with Libreoffice/Openoffice

Have more questions about using labels, feel free to visit the forums and engage the community in helping you

by wlmanager at November 29, 2017 05:00 PM

>Pranav Kant

Dialog Tunnelling

So I’m finally resurrecting this blog to life after a long time.

I’m simply going to talk about what I’ve been currently working on in Collabora Online or LibreOffice Online, as part of my job at Collabora.

In our quest to bring more features available to our users editing documents in the browser, we are attacking something that contains the majority of the features in LibreOffice – the dialogs. One of the complaints that power users make in Online is that it lacks advanced features: they cannot add coloured borders in their paragraphs, manage tracked changes/comments, correct the spelling and grammar in the document, etc. The question before us is how do we bring these functionalities to the cloud at your disposal in your browser tab?

We really don’t want to write another million lines of code in Javascript to make them available in your browser and then dealing with separate set of bugs for time to come.

So we decided to come up with a plan to just tunnel all the hard work that developers have done for the past couple of decades: come up with appropriate infrastructure to open the dialog in headless mode, paint them as a bitmap in the backend, and tunnel then image to you in the browser. And then add life to them by tunnelling your mouse/key events as well which will invalidate and update the new image you are seeing the browser. Don’t worry; we are not sending the whole dialog image back to your browser every time. Only the part that needs updating in the dialog is sent back to the browser saving us precious time and network bandwidth improving your UX.

The current state of the project looks really promising. Not just the modeless dialogs, we are able to tunnel the modal ones as well which is not something we had expected earlier.

Since text is boring, here’s a preview that shows dialog tunnelling in action in our test tools, GtkTiledViewer. The integration with Online is ready too and undergoing some final polishing. But it’s not something you’d have to wait for too long; we are polishing a big refactor to LibreOffice core master to install the dialog infrastructure needed for integration. Now you will be able to do pretty much all the things in Online (and in CODE version 3.0 soon to be released) that you’ve always wanted to do.

Here are the slides from the talk I delivered on the same topic in our annual LibreOffice Conference in Rome this year.

November 29, 2017 12:00 AM

November 28, 2017

Stephan Bergmann

LibreOffice, Flatpak’ed, Flathub’ed

flathub

Flathub is the app store for all things Flatpak. And LibreOffice is now available there, too!

When we started flatpak’ing LibreOffice, we made builds of the LibreOffice “Fresh” stream available on the Document Foundation download pages. Since LibreOffice 5.4.2, we now provide such builds through Flathub.

The benefit to you as a user is that there are builds for more architectures (currently aarch64, i386, and x86_64), and that you need to keep track of one less single-app Flatpak repo. (Check out what else is available in the Flathub repo!)

The benefit to me as provider of the original Document Foundation flatpak builds is that the Flathub infrastructure now does those builds for me. We will stop providing the Document Foundation builds after the current LibreOffice 5.4.3.


by stbergmann at November 28, 2017 08:36 AM

November 27, 2017

Lior Kaplan

AGPL enforced: The Israeli ICT authority releases code

Data.gov.il was created in 2011 after the Israeli social justice protests as part of the the public participation initiative and started to offer data held by the government. Back then the website was based on Drupal. In 2016 it was changed to CKAN, a designated system for releasing data. This system is licensed under the AGPLv3 requiring source code availability for anyone who can access the the system over a network, de facto for every user.

Since the change to CKAN, open source people asked the state to release the code according to the license but didn’t get a clear answer. All this time when it’s clear it’s violation.  This led Gai Zomer to file a formal complaint in March 2017 with the Israeli State Comptroller. Absurdly, that same month the ICT authority mentioned a policy to release source code it owns, while failing to release code it has taken from others and adapted.

With the end of the summer break and Jew holidays, and after I wasn’t able to get the source, I decided to switch to legal channels, and with the help of Jonathan Klinger and my company, Kaplan Open Source Consulting, we notified they should provide the source code or we’ll address the court.

Well, it worked. In 3 days time the CKAN extensions where available on the website, but in a problematic way, so users weren’t able to download easily. This is why we decided not to publish this code release and let them fix it first. In addition we made it clear all the source code should be available, not only the extensions. Further more, if they already release it’s recommended to use git format instead of just “dumping” a tarball. So we told them if they aren’t going to make a git repository we’ll do that ourselves, but in any case, would prefer them to do that .

While this issue is still pending, the ICT authority had a conference called “the citizen 360” about e-gov and open government in which they reaffirmed their open source plans.

A slide about open source from the Israeli ICT authority presentation

A slide about open source from the Israeli ICT authority presentation

Now, a month later, after our second letter to them, the about page in data.gov.il was updated with links to the ICT authority GitHub account which has the sources for the website and the extensions. A big improvement, and an important mark point as the commit to the repository was done by an official (gov.il) email address.

Beyond congratulating the Israeli ICT authority for their steps forward and the satisfaction of our insisting on them became fruitful, we would like to see the repository get updated on a regular basis, the code being given back to the various CKAN extensions (e.g. Hebrew translation). In general, we hope they would to get inspired by how the how data.gov.uk is doing technical transparency. If we allow ourselves to dream, we would like to see Israel becoming a dominate member in the CKAN community and among the other governments who use it.

We’re happy to be the catalyst for open source in the Israeli government, and we promise to keep insisted where needed. We know that due to other requests and notifications more organizations are on their way to release code.

(This post is a translation from Hebrew of a post in Kaplan Open Source Consulting at https://kaplanopensource.co.il/2017/11/20/data-gov-il-code-release/)

by Kaplan at November 27, 2017 08:06 AM

November 26, 2017

Eike Rathke

Upgrading Digikam from 4.x to 5.x and wrong AlbumRoots

(Not so) recently I upgraded a Debian system from Jessie to Stretch. Along with that came an upgrade of the Digikam photo management application from version 4.x to 5.3. After starting that the first time the albums were empty. WTF? Putting the modified digikam4.db aside, creating a fresh one and restoring the old one and comparing those revealed that they differed in how the AlbumRoots path was stored. Digikam 4.x stored it as volumeid:?path=%2Fhome%2F... (with URL encoded %2F as / slashes) where Digikam 5 stores a literal / slash. Changing that to what Digikam 5 expects did the trick and the albums were there again. So when upgrading, before you start Digikam 5 for the first time, do the following (assuming the database is /home/you/Pictures/digikam4.db)

  • backup your original digikam4.db file
  • install the sqlitebrowser package if not installed yet
  • on a terminal command line invoke: sqlitebrowser ~/Pictures/digikam4.db &
  • go to the Browse Data tab
  • Table: AlbumRoots
  • select (click into) the identifier field
  • in the right edit field change its content from volumeid:?path=%2Fhome%2Fyou%2FPictures to
    volumeid:?path=/home/you/Pictures
  • Write changes and exit

Start digikam. All good (hopefully ;-)

Update 2017-11-27T14:50+01:00
Forgot to mention that when starting Digikam 5 the first time a dialog appears offering to migrate from version 4, it advises to not do so but has migration preselected, do not migrate there or it will mess things up. You may lose some existing personal preferences, but the migration for me at least simply did not work.
Related seems to be KDE bug 364258 though claimed to be fixed.

by erAck (23@127.0.0.1) at November 26, 2017 10:02 PM

November 25, 2017

Eike Rathke

International Day for the Elimination of Violence against Women

Today is the International Day for the Elimination of Violence against Women.

At the Rome Conference venue was a seat in the front row of the audience reserved for women who have been victims of violence and were killed.

Posto Occupato
Posto Occupato, Detail
SAVE SEATS (Posto Occupato) is a strong gesture dedicated to all women who have been victims of violence. Before they were cruelly killed by a husband, partner, lover or complete stranger they were all able to sit in a seat, on a bus, on a train, in the theatre, at school, in the subway, in society. We want to reserve this seat for them, so in day to day living they will not be ignored. POSTOCCUPATO.ORG

 

by erAck (23@127.0.0.1) at November 25, 2017 04:20 PM

November 23, 2017

Naruhiko Ogasawara

REPORT: LibreOffice mini-conference 2017 Japan (in openSUSE.Asia Summit 2017 Tokyo)



On Oct 22nd, 2017, we hosted an event titled "LibreOffice mini-conference 2017 Japan," as a sub-event of "openSUSE.Asia Summit 2017 Tokyo."
openSUSE.Asia Summit is:
"one of the great events for openSUSE community (i.e., both contributors, and users) in Asia. Those who usually communicate online can get together from all over the world, talk face to face, and have fun. Members of the community will share their most recent knowledge, experiences, and learn FLOSS technologies surrounding openSUSE."
This year hosted this event at the University of Electro-Communications (UEC) in Chofu, Tokyo, and I was honored to be a committee member.
In spite of the bad weather immediately before the hit of the huge typhoon Lan, over 150 participants from nine countries gathered in two days (Oct 21st and 22nd), and we enjoyed various talks and workshops on openSUSE and various open source software (including LibreOffice, of course) and were able to interact with each other.

Thanks to The Document Foundation for helping the travel cost, we could invite 3 speakers from cities far from Tokyo, then we had 6 speakers from 3 countries (Taiwan, Indonesia, and Japan).
Sponsor board and event board.  See "LibreOffice: The Document Foundation" logo!

Talk highlight

Let's see each talk in our mini-conference!

Opening Talk: LibreOffice: The Office Suite with Mixing Bowl Culture, by Naruhiko Ogasawara


My talk :)
Introducing LibreOffice to use the keyword "Mixing bowl," taken from TDF official slide provided as a marketing material.
I love LibreOffice because everyone in the community is kind to anyone who acts to do something.  I aimed to convey a message that anyone can participate LibreOffice project in the same opportunities, and I could do (hope so).

The Interoperability of Documents, by Franklin Weng

Not only the full talk in mini-conference, but he also had a lightning talk on 21st Oct evening. by hisa_x.  Flickr link


Franklin, who leads ODF migration in Taiwan, talked about the importance of creating interoperable documents and how to do it.  "Document interoperability = Working together better" in this talk was a simple and strong, important message.
One of the keys is "document format," so we must choose ODF instead of OOXML to make interoperable documents (and of course LibreOffice is the best office suite to generate ODF ;).
I thought "interoperability" was a keyword of the mini-conference (coincidentally, many talks mentioned that).

State of CJK issues of LibreOffice, by Shinji Enoki

Shinji wearing Rome conference T-shirt. Cool! by hisa_x. Flickr link
https://speakerdeck.com/enoki/state-of-cjk-issues-of-libreoffice-libreoffice-miniconf

Shinji Enoki is a member of LibreOffice Japanese Team (Japanese NLP), same as mine.  He continuously attended LibreOffice Conference for years, and this talk was "replay" of last global conference talk in Rome.
In The Next Decade Manifesto,
WE COMMIT OURSELVES:  to support the preservation of mother tongues by encouraging all peoples to translate, document, support, and promote our office productivity tools in their mother tongue
Then, not only UI/document translations but language-dependent features work well is also important.   But sometimes it is quite hard for developers to understand what is "work well" in language which is not his/her mother tongue.  Especially CJK, RTL for a developer who uses latin language.  So we, Asian users have to improve LibreOffice by ourselves and to help developers to go the right way.
He introduced current status of CJK issues with examples such as IVS problem, and several resources provided by the project:

Introduction to Japanese Darkness "Excel Houganshi," by Rin Nakamura

Rin Nakamura talking about Excel Houganshi. by hisa_x. Flickr link
Hmm... it is quite hard to explain what the talk means because it very tied to Japanese culture... but I'm trying.
"Houganshi (方眼紙)" means "graph paper," paper with pre-printed square grids.  In Japan, it is common to use Excel like as Houganshi, to make all cell width and height exactly same.  You can easily see so many "Excel Houganshi" via google images.
Nakamura-san claimed "You don't do this (to create "Excel Houganshi"), then introduced an example that he was bothered by such Excel Houganshi, and demonstrated the trick to make it a proper document based on it.
His message was "use tools (like office suite) with proper way."   Excel Houganshi has been a good technic in "print to paper" era, but in the digital era, it became "Japanese Darkness" culture.  No one wants to maintain Excel Houganshi document.  So, the talk was strongly related to Franklin's talk;  Excel Houganshi is exchangeable, but NOT interoperable.

Write Your Story with OpenSource, by Umul Sidikoh

Umul talking with demonstrations. by Edwin Zakaria. Flickr link

Umul from Indonesia told us how to write a document using Writer style features, with lots of demonstrations.  Live demo sometimes makes us very frustrated, but she tried well :).
This talk also related to interoperability.  Using style feature makes documents more interoperable.  It is "right way" to use Writer, instead of insert new line, white space or specify font directly, as Franklin mentioned.
I heard that this was her first overseas trip and she seemed to enjoy both the conference and Tokyo.  I believe it was a great step for her to move forward to contributing LibreOffice, and she'll continue to contribute us, with contacting other LibreOffice people.

How to build LibreOffice on your desktop, by Masataka Kondo

(Oops, I couldn't find out his photo... ><)


LibreOffice is open source software.  It means, we could build LibreOffice from source code by ourselves.  Kondo-san, another member of LibreOffice Japanese Team, introduced LibreOffice building-how-to with openSUSE and Linux Mint.
Franklin commented we also could try with Docker (and he let us know the link).  I never tried to use Docker to build LibreOffice, then I would like to try near future.

Lightning Talks

openSUSE.Asia Summit has 2 lightning talk sessions in evening each of day.
In day 1 session, Franklin presented "Become a TDF Member."  It was fantastic!  Everyone was bursting laughing :).

In day 2 (the day of LibreOffice mini-conference) session, two interns from iCraft, the company which provides LibreOffice support in Japan and sponsored openSUSE.Asia Summit, had talks related their home country (Tunisia and Ethiopia) and LibreOffice.  They are also very interested.
TRABELSI Mohamed talking about Tunisia and LibreOffice, by hisa_x, Flickr link
Aschalew Arega Ademe talking about Ethiopian IT / FLOSS includes LibreOffice, by hisa_x, Flickr link

What is a "LibreOffice mini-conference"?  Is this different from LibreOffice Kaigi?

Anyway, I would like to explain that ;)
In my personal opinion, since LibreOffice is a consumer product, it is important that there are events where users can participate it by their mother tongue. That's why there is LibreOffice Kaigi. "Kaigi" is taken from a Japanese word "会議" means "conference," which means that it is the event for Japanese speakers by Japanese speakers. Of course, it is respect for RubyKaigi (the annual conference of the programming language Ruby), too.
Nonetheless, for the community members, of course, international exchange is also very important. We already have an annual event called LibreOffice Conference which is a wonderful opportunity to exchange information and opinions. However, the LibreOffice Conference is held in Europe (I do not want to say that is a bad thing), it is a bit difficult for Asian "neighbors" to gather. We use different mother tongues, but we live in a similar time zone, similar culture, so there should be something we can do together. Therefore, I think that it is better to have an "international, regional" conference. That is a "mini-conference."

Conclusion

I could say that our "mini-conference" this year was a huge success.  Everyone enjoyed lots of interesting talks and spent a great time to talk each other.

Thanks to all attendees, speakers, sponsors (includes The Document Foundation) and excellent volunteer staffs of openSUSE.Asia Summit.  Hope others will host another mini-conference (or any title, means "international, regional") and we will meet there!
Speakers group photo in our booth, by Edwin Zakaria. Flickr link 


Note:

I believe all videos of openSUSE.Asia Summit 2017 will be published soon.  I will inform you here when it's done immediately.


by Naruhiko Ogasawara (noreply@blogger.com) at November 23, 2017 04:22 AM

November 20, 2017

LibreOffice Design Blog

Statement about LibreOffice Mascot Project

On Thursday, we came to the conclusion to close voting for the LibreOffice mascot in advance of the planned schedule in December. For a number of reasons, the process has evolved in a direction we were not expecting. When we started, we were looking for a visual image which could represent LibreOffice, a free office suite developed by an international and diverse community of friends, and not for a subject of heated discussions between groups and individuals.…

The post Statement about LibreOffice Mascot Project appeared first on LibreOffice Design Team.

by Italo Vignoli at November 20, 2017 09:40 AM

November 16, 2017

LibreOffice Design Blog

LibreOffice mascot survey: The progress so far

As you’ve no doubt seen, over the last few months we’ve been looking for a LibreOffice mascot. This is just something fun for our community to use, for instance on T-shirts at events, so it doesn’t have to be ultra slick and professional – it isn’t a replacement for the official branding and logos that we use in the software, website and marketing materials.…

The post LibreOffice mascot survey: The progress so far appeared first on LibreOffice Design Team.

by The LibreOffice Design Team at November 16, 2017 03:39 PM

November 13, 2017

LibreOffice Design Blog

LibreOffice Mascot: Iterating the submissions

tl;dr: Please comment at https://imageboard.documentfoundation.org/posts

The voting phase has been conducted with great success. More than 27,000 people had a look at the submissions and many voted on all items. Thanks a lot for your interest and contribution! There has also been some discussion on various social media channels about the procedure.…

The post LibreOffice Mascot: Iterating the submissions appeared first on LibreOffice Design Team.

by The LibreOffice Design Team at November 13, 2017 07:10 PM

November 10, 2017

Miklos Vajna

Basic EPUB3 export in Libreoffice

https://farm5.staticflickr.com/4577/37588898064_117dc4a933_o_d.png

I worked on a new EPUB3 export filter in LibreOffice recently. First, thanks to Nou&Off in cooperation with a customer who made this work possible. The current state is that basic features work nicely to the extent that the filter is probably usable for most books (they typically mostly have just text with minimal formatting), so this post aims to explain the architecture, how the various pieces fit together.

The above picture shows the building blocks. The idea is that nominally EPUB is a complete export filter, but instead of doing all the work, we offload various sub-tasks to other modules:

  • First we invoke the existing (flat) ODT export, so we can work with ODF instead of with the UNO API directly. This will be useful in the next step.

  • Then we feed the SAX events from the ODT export to a new librevenge text export. Given that the librevenge API is really close to ODF (and xmloff/ has quite some code to map the UNO API to ODF), here it pays off to work with ODF and not with the UNO API directly.

  • The librevenge text export talks to a librevenge generator, which is David Tardon’s excellent libepubgen in this case.

  • Finally libepubgen calls back to LibreOffice, and our package code does the ZIP compression.

The setup is a bit complicated, but it has a number of advantages:

  • Instead of reinventing the wheel, LO and DLP now shares code, libepubgen is now a dependency of LibreOffice.

  • libepubgen doesn’t bring its own ZIP writer code, it can nicely reuse our existing one.

  • This is a great opportunity to finally write an ODT→librevenge bridge, so other DLP-based export libs can be added in the future (e.g. librvngabw).

  • If we ever want to export to EPUB from Draw/Impress, libepubgen will help us there as well.

As a user, here is a list of features you can expect working:

  • plain text should work fine (formatting may be lost, but content should be fine)

  • table of contents, as long as you properly use headings or you separate chapters by page breaks

  • export options: EPUB3 vs EPUB2, split on headings vs page breaks

  • basic set of character and paragraph properties should work

During development I regularly used epubcheck, so hopefully the export result is usually valid.

All this is available in master (towards LibreOffice 6.0), or you can grab a daily build and try it out right now. :-)

November 10, 2017 10:19 AM

November 09, 2017

Caolán McNamara

gtk3 + broadway + libreoffice

Out of the box in Fedora 26 I see that our gtk3 version of LibreOffice mostly works under broadway so here's libreoffice displaying through firefox. Toolbar is toast, but dialogs and menus work.


broadwayd :5 &
firefox http://127.0.0.1:8085 &
GDK_BACKEND=broadway BROADWAY_DISPLAY=:5 soffice --nologo &

by Caolán McNamara (noreply@blogger.com) at November 09, 2017 09:08 PM

November 08, 2017

LibreOffice Design Blog

Community-vote for the new ‘Getting Started Guide’ cover

The new release 6.0 of LibreOffice is just around the corner. And we also want to update the documentation for this release. We have three proposals for new covers and would like to know which one you prefer.

Please vote by clicking option 1, 2 or 3 below and submit per “vote”.…

The post Community-vote for the new ‘Getting Started Guide’ cover appeared first on LibreOffice Design Team.

by The LibreOffice Design Team at November 08, 2017 06:50 PM

November 06, 2017

Mike Kaganski

Big consequences of a good bug report

Last week I had fixed a trivial bug (a leftover from a former change where a function’s return was changed, but one place of its usage managed to escape to be not converted to properly treat the changed return). It seems to simultaneously have fixed a number of other bugs (the discussion may be found in the bug tracker issue). The little (a few characters) bug turned out to create both performance issues, and clipping of characters, so it had big impact on LibreOffice on Windows (with DirectWrite, e.g. when OpenGL is used).

The problem became trivial both to find and fix, because of great bug report by Telesto, who not only filed the report, but also had provided every relevant piece of information, including terminal output accompanied the problem manifestation. I cannot emphasize enough the importance of this: the effort of the bug reporter makes a difference. Without the effort, some problems remain very difficult for developers to be tracked down and get fixed.

I write this to praise Telesto‘s great job, and urge every reporter of a bug to follow this great lead.


by mikekaganski at November 06, 2017 07:00 AM