Worked on a new WordPress site and bot some header errors. Tried to reset PW but it crashed. Seemed its difficult vor impossible to usw the database to set a new password with a md5-hash. Need more investigation ;-(
oreportcrashes when it fails to read kernel symbols as a user.
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.…
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.…
I worked on a new EPUB3 export filter in LibreOffice recently. First, thanks to the Dutch Ministry of Defense in cooperation with Nou&Off 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. :-)
broadwayd :5 &
firefox http://127.0.0.1:8085 &
GDK_BACKEND=broadway BROADWAY_DISPLAY=:5 soffice --nologo &
Berlin, November 9, 2017 – The Document Foundation (TDF) announces LibreOffice 5.4.3, the third minor release of LibreOffice 5.4 family. LibreOffice 5.4.3 continues to represent the bleeding edge in term of features, and as such is targeted at technology enthusiasts and early adopters.
TDF suggests to conservative users and enterprises to deploy LibreOffice 5.3.7 with the backing of certified professionals (an updated list is available at https://www.libreoffice.org/get-help/professional-support/).
LibreOffice 5.4.3 includes approximately 50 bug and regression fixes. Technical details about the release can be found in the changelogs here: https://wiki.documentfoundation.org/Releases/5.4.3/RC1 (fixed in RC1) and https://wiki.documentfoundation.org/Releases/5.4.3/RC2 (fixed in RC2).
LibreOffice 5.4.3 is immediately available for download from the following link: https://www.libreoffice.org/download/.
LibreOffice users, free software advocates and community members can support The Document Foundation with a donation at https://www.libreoffice.org/donate/. Donations help TDF to maintain its infrastructure, share knowledge, and organise events such as the Month of LibreOffice, which has last week and will be active until the end of November (https://blog.documentfoundation.org/).
Several companies sitting on TDF’s Advisory Board (https://www.documentfoundation.org/governance/advisory-board/) provide either value-added LTS versions of LibreOffice or consultancy services for migrations and training, based on best practices distilled by The Document Foundation.
Today is World Usability Day, beginning events around the world that “bring together communities of professional, industrial, educational, citizen, and government groups for our common objective: to ensure that the services and products important to life are easier to access and simpler to use.”
Starting today, and over the next few days, there will be 73 events across the globe, celebrating progress in user experience (UX) and educating everyone about how good design and usability affects our daily lives. Click here to find an event near you, and see this page to learn how to get involved.
Meanwhile, the LibreOffice design team is active in many areas relating to UX. One of the tasks is to respond to bug reports or enhancement requests on Bugzilla when UX input is requested with the keyword “needsUXEval”. This request might be just a simple “what do you folks think” or “how do we handle this in general”, through to a proposal for a complete redesign.
Started with a total number of more than 500 issues the team got the number down to 380 in the last year. And most tickets have been answered within one day!
Most conversation is done on Bugzilla, where every opinion is valued. Some issues need a closer look and are discussed in the weekly meetings. Your contribution at both places would be highly appreciated!
Get involved with our UX communityand you can make a big difference for millions of end users around the world.
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.
On the 1st of November we started a new Month of LibreOffice, celebrating contributions from our worldwide community. Everyone who helps out with the project gets a chance to win a cool sticker. So, one week in, how are we doing?
Well, so far 137 stickers have been awarded! That’s a great start, and you can see all the details on this wiki page. It shows usernames from various tools used in LibreOffice development, and we update it every day. You can see that we’ve had code contributions from several people – but of course, these are just community contributions. Click here to see full development stats including patches from people who’re paid to work on the codebase.
Meanwhile, our QA and localisation communities have been especially busy in the run-up to LibreOffice 6.0, which is due to be released in late January. And then our diligent Ask LibreOffice community has done great work answering questions from users and helping them to fix problems. Finally, we’re seeing useful documentation updates (especially on the wiki) and word-spreading on Twitter as well.
Thanks to everyone who has helped out so far! But there are still three weeks to go – so if you want to improve LibreOffice and get a shiny sticker for your laptop or PC, read on to see how you can help…
There are many ways you can help the LibreOffice project and claim a sticker:
The Document Foundation (TDF), the charitable entity behind the world’s leading free office suite LibreOffice, seeks an individual – or individuals part (or full) time – to be
a Development Mentor
to start work as soon as possible. The role requires the following:
The role involves working from home at your location for at least 20 hours per week, up to full-time and includes among other items:
Supporting existing mentors in the LibreOffice community including:
Previous experience with such tasks is highly welcome, so is using free software. Speaking and writing English reasonably well is a mandatory requirement.
The work time during the day is flexible, apart from some fixed times when availability is required (e.g. during meetings, which usually take place at 14:00 or 15:00 UTC once per week).
TDF welcomes applications from all suitably qualified persons regardless of their race, sex, disability, religion/belief, sexual orientation or age.
As always, TDF will give some preference to individuals who have previously shown a commitment to TDF, including but not limited to members of TDF. Not being a member, or never having contributed before, does not exclude any applicants from consideration.
TDF is looking forward to receiving your applications, including curriculum vitae, your financial expectations, and the earliest date of your availability, via e-mail to Florian Effenberger at email@example.com no later than December 5, 2017. You can encrypt your message via PGP/GnuPG.
If you haven’t received feedback by January 11, 2018, your application could not be considered.
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.
I gave a presentation about the creation of LibreOffice non-code extensions at the Open Rhein Ruhr in Oberhausen, a local open source event in Germany. The LibreOffice project attended the event with a booth too.
I added a first template for a non-code LibreOffice extension on Github. I’ll add some more during the next weeks. You’ll find them in a subfolder of my repository for the extensionbook:
Throughout the year, LibreOffice community members attend events around the world, helping to promote free software and open standards. We’re really grateful for their work! Today we have a couple of reports from recent events – and we start with Muhammet Kara who has been busy in Cyprus:
I attended the Free Software and Linux Seminar on October 20 at METU NCC (Northern Cyprus Campus). 60 people were there, all university students, and I talked about many topics: free Software, Linux, LibreOffice, ways to contribute, and opportunities like Google Summer of Code, Outreachy, and LibreLadies. Then I finished by answering their questions about Free Software, Linux, and Pardus. The excitement of the attendees was promising!
Then, on October 21 at METU NCC, I helped to organise a LibreOffice Developer Workshop. Many people were interested in joining this session, but I asked the organisers to bring a small group, so 10+ people attended. We formed a Telegram group with the attendees so that they can cooperate, and I can provide some hand-holding while they got their first patches merged. (So far two of them have had their patches submitted, reviewed, and ready to be merged. The first ones will also help the others to follow.) Overall, I am happy about the results.
Next up, we have a report from Stanislav Horáček about a recent event in the Czech Republic:
Zdeněk Crhonek and I attended LinuxDays, the biggest Linux event in the Czech Republic. A simple LibreOffice booth was managed there – here’s what it looked like (photo by Lukáš Jelínek):
We got useful feedback, and most of our visitors were satisfied with LibreOffice – there were fewer complaints about document compatibility than in previous years. In addition, there was interest in how development works and the role of The Document Foundation. We were surprised by some very specific questions (headless mode, Base, remote documents…) and it’s clear that LibreOffice Online is still generally not well known.
There was also a meeting of Czech localisation communities (Mozilla, GNOME, OpenSUSE) – we agreed to continue with cooperation (terminology and style consolidation, and an initiative to renew language dictionaries). Overall, I have a feeling that the Linux/FOSS community here is strong and growing, and it is great that LibreOffice can be part of it.
Thanks to Muhammet and Stanislav for their great work! We really appreciate your help spreading the word. And to others reading this: if you want to get involved as well and promote LibreOffice in your country, join our marketing mailing list and we’ll give you a hand!
Enumeration of lists is one of the most struggled features in LibreOffice Impress. That is clear from the issues reported on Bugzilla tdf#103364 and tdf#103369 with over 100 bugs and enhancement requests, but also when asking users. A usability test was conducted at the city of Nantes revealed some of the major problems that we want to tackle now.…
He took the small bundle from Karlsson and held her tenderly in his arms.
"Don't cry, there's a good baby", he said.
Astrid Lindgren "Karlsson on the Roof"
Making LibreOffice more flexible is one of our primary goals announced with the MUFFIN concept. Extensions are a great way for personalization and just like we did for color palettes, we’ve now made icon themes available as extensions. This blog post describes how to create and share your own icon theme extension.…
I got the chance to work a bit further on my script / documentation about German foundation law and added some bits to the text, cleaned some typos etc. during my vacation. There are some missing sections and I hope to find some time to add Thema soon. But that depends on the daily workload after my vacation.
Windows still provides two sets of many of its Win32 API functions taking or returning strings: a legacy “Ansi” (functions named like fooA) and Unicode (named like fooW; available since Windows NT, and in Windows 95 with Layer for Unicode – and thus on any Windows OS supported by LibreOffice).
The “Ansi” functions take 8-bit strings in current codepage (single- or multibyte). The repertoire of characters representable in those strings is, naturally, limited to that codepage (that is either setup in system’s Language for non-Unicode programs, or explicitly set by running application). Unfortunately, unlike in other contemporary OSes, Windows doesn’t allow setting its locale to use UTF-8. If a string arrives to such a function that contains characters outside of that set, the string content will be altered, and functions’ behaviour might change unexpectedly.
“W” versions of those functions take UCS-2 strings, that are able to represent most of Unicode range (I am unsure if those strings are actually UTF-16, and so are able to represent the full Unicode repertoire, but anyway, even UCS-2 is much wider than most of single- or multi-byte codepages).
In last two weeks, we have replaced many places (0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D) in LibreOffice codebase where legacy “A”-functions were still used, with explicit calls of their “W”-counterparts, removing redundant conversions of strings from LibreOffice internal UTF-16 string representation to 8-bit strings and back. One of most significant effects might be on file-management functions, where such conversions could alter paths/names containing Unicode characters not representable in currently selected 8-bit codepage, and lead to failed file operations. One example of such problems is tdf#103525.
The changes are included into master towards 6.0.
Last week, we’ve added application compatibility manifests to LibreOffice libraries and executables. This is intended to allow the program to run in current OS context, instead of switching to a previous (namely, Windows Vista in case of absent manifest section) OS compatibility context. The effects of this are listed in a MS KB (this is alternative link just in case).
Currently we declare compatibility with Windows 7 through Windows 10. This change is integrated into current master towards LibreOffice 6.0.
I took some time to set up the environment to forward the Zope server port to my local box. Because I want to log into the Zope Management Interface with the permissions of an admin user I had add one first to the Zope instance. I run the debug instance of the Plone CMS with the command ‚adduser <adminusername> <password>‘ for this purpose.
Then I started the debug-instance with the command ‚fg‘. Once the debug-instance ran in forground (fg) mode, I started the forwarding within a terminal on my local box:
$ ssh -L 8085:localhost:8085 -N <server_name> -v
The <server-name> is the login to the server, whose port I wanted to forward.
The I could reach the forwarded server port in my browser with: http://localhost:8085/manage
This pointed me to the login of the root of the Zope instance and the ZMI. There I could login with the newly created admin user.
The Document foundation blog have a post about LibreOffice 7th anniversary:
Berlin, September 28, 2017 – Today, the LibreOffice community celebrates the 7th anniversary of the leading free office suite, adopted by millions of users in every continent. Since 2010, there have been 14 major releases and dozens of minor ones, fulfilling the personal productivity needs of both individuals and enterprises, on Linux, macOS and Windows.
I wanted to take a moment to remind people that 7 years ago the community decided to make the de facto fork of OpenOffice.org official after life under Sun (and then Oracle) were problematic. From the very first hours the project showed its effectiveness. See my post about LibreOffice first steps. Not to mention what it achieved in the past 7 years.
This is still one of my favourite open source contributions, not because it was sophisticated or hard, but because it as about using the freedom part of the free software:
Replace hardcoded “product by Oracle” with “product by %OOOVENDOR”.
On a personal note, for me, after years of trying to help with OOo l10n for Hebrew and RTL support, things started to go forward in a reasonable pace, getting patches in after years of trying, having upstream fix some of the issues, and actually able doing the translation. We made it to 100% with LibreOffice 3.5.0 in February 2012 (something we should redo soon…).
This is how the export result looked like:
And this is how it now looks like, after fixing:
For a long time the PDF export filter had no tests at all; the current approach I introduced is that we parse the PDF export result with pdfium, which is an excellent PDF rendering library (I covered it in general in an earlier post).
So given that pdfium knows how that rectangle looks like, we should be able to query the details of it from a test as well, correct? It depends. Yes, it’s possible technically, but no, most of the pdfium functionality is actually not exposed at its public API.
The current situation is that one could use
FPDF_LoadPage() to get access to a PDF page, then
FPDFPage_GetObject() to iterate over objects on a page. We can filter for the
relevant object by using
that will give us the only path that has a yellow fill color.
But getting more info about the geometry of the path isn’t really possible. As
a workaround I went with
FPDFPageObj_GetBounds() for the test, but wouldn’t it
be nicer to get the individual segments (the objects that are the children of
a path) and then get coordinates and other properties of a segment? This is
what the recent API I added to pdfium now does. It provides the followings:
FPDFPath_CountSegments() gives you the number of segments of a path
FPDFPath_GetPathSegment() gives you a given segment, via a new
FPDF_PATHSEGMENT opaque type
you can use
FPDFPathSegment_GetPoint() to get the coordinates,
FPDFPathSegment_GetType() to get the type (move to, line to, etc.) and
FPDFPathSegment_GetClose() to see if the segment closes the current subpath
of the path (or not)
This means that after the next pdfium update in LibreOffice, PDF export tests can nicely assert these properties of paths instead of dubious bounding box should be larger after rotation assertions.
If a member of the LibreOffice extensions and templates website submitted a new project for publication it was added to the review list. But there is currently no notification of the reviewer about this new entry on the list. Thus the reviewer had to log in to the site constantly to check if there is a new project on the list.
To make the life of the reviewer a bit easier I added a notification by email in case someone submitted a new project for publication. I did this for both Plone addons which drive the LibreOffice extensions and templates site. The site itself runs on Plone 5, a powerful Content Management System.