• Slugged much of the day; assembled Naomi's dresser, played with new bass guitar. Out for a walk on the heath with the babes in the dark.

• Out to Anglesey Abbey - enjoyed the tree & main house; back for lunch, out to play the Organ - David over - played silly games until late.

Resolved - 2018-12-28 11:39:21 UTC

---

extensions check failed (server time: 2018-12-28 11:37:31 UTC)

Get https://extensions.libreoffice.org: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

• Packed the house up, collapsed beds; managed to stuff presents into cars variously. Picked up a hire car with Tom, bid a fond au-revoir to R&A. Drove home, heated the house, unpacked, welcomed M&D, T&B&S&L.

I created a new clean buildout from the Plone coredev Github repository using a checkout of the 5.2 branch. I added a local.cfg file to my local repo and added some packages to this file. This packages were checked out within the next run of buildout using the new local.cfg buildout file, extending buildout.cfg.

I created the local.cfg using the pointer from this webpage:
https://github.com/plone/Products.CMFPlone/issues/2184#issuecomment-359445243

I added a further section to the local.cfg for ‘mr.bob’. Thus my local.cfg looks like this:

[buildout]
extends = buildout.cfg

parts += mrbob

always-checkout = true

custom-eggs +=
        collective.dexteritytextindexer
        bobtemplates.plone

        
test-eggs +=
        collective.dexteritytextindexer [test]
        
        
auto-checkout +=
        collective.dexteritytextindexer
        bobtemplates.plone
        
[mrbob]
recipe = zc.recipe.egg
eggs =
    mr.bob
    bobtemplates.plone
        
        
[sources]
collective.dexteritytextindexer = git git://github.com/andreasma/collective.dexteritytextindexer
bobtemplates.plone = git git://github.com/plone/bobtemplates.plone.git

I created a new branch inside the collective.dexterity local repository with ‘git checkout -b python3’ and did on this branch the steps that are described on this website:
https://github.com/plone/Products.CMFPlone/issues/2184

I run sixer and python-modernize on the package and was able to get it running with Plone 5.2 on Python 3.6. I already created a new Plone site from scratch for this.

Then I created a new Plone add-on package using mr.bob and run sixer and python-modernize against the new package. Once this was finished I added the package to the local.cfg buildout script and run buildout again. I was able to start the Plone site with ‘./bin/instance fg’ without issues again. I installed the new addon within the ‘Site Setup’ page of Plone. The new addon had no real content at that time (only the necessary boilerplate / template).

This created the environment to migrate the current state of my Plone addons to the new Plone 5.2 version and Python 3. This migration is necessary because the support for  Python 2, currently used by Plone, ends within a year.

• Up late; Nicolas, Laura & T arrived went to the park with the whole tribe; ate, caught up, played together.

The LibreOffice Quality Assurance ( QA ) Team is happy to announce LibreOffice 6.2 RC1 is ready for testing!

LibreOffice 6.2 will be released as final at the beginning of February, 2019, being LibreOffice 6.2 RC1 the third pre-release since the development of version 6.2 started in mid May, 2018. See the release plan. Check the release notes to find the new features included in this version of LibreOffice.

LibreOffice 6.2 RC1 can be downloaded from here, and it’s available for Linux, MacOS and Windows.

In case you find any problem in this pre-release, please report it in Bugzilla ( You just need a legit email account in order to create a new account ) so it can get fixed before LibreOffice 6.2 final is released.

For help, you can contact us directly in our IRC channel.

Happy testing!!

…

The post LibreOffice 6.2 RC1 ready for testing appeared first on LibreOffice QA Blog.

• Christmas day; stockings in the morning - thrilled to discover J&I had a stocking of our own - filled with chocolate & a pair of satsumas. Out with M&D to the excellent nearby CofE church for a Christmas service complete with interactive congregation word-cloud, and good music & talk.
• Back for presents, lunch; lots of lovely food, good company - sadly congested chest. Played games variously - Empires, Articulate etc.

(Thanks to Drew Jensen from our marketing community for the picture.)

Update 01:00 UTC: Due to an unforeseen namespace change in 1.1 we had to trigger a full reindex of all projects. The core and help projects are thus currently unusable on {OpenGrok. Expected ETA: Jan 1 afternoon UTC (will be refined if needs be be).

How much do you know about LibreOffice – the software, the community and its history? We’ve made a little quiz for you to try out, so check out the questions below, and you’ll find the answers at the bottom. Good luck :-)

1 – LibreOffice is a successor to OpenOffice.org, which was based on the proprietary suite StarOffice. Which company was behind StarOffice?

A: Star Corp
B: Solar Sys
C: Star Division

2 – In which year was The Document Foundation (TDF), the non-profit entity behind LibreOffice, legally established?

A: 2009
B: 2012
C: 2014

3 – Who is the current chairperson of TDF?

A: Marina Latini
B: Michael Meeks
C: Thorsten Behrens

4 – LibreOffice includes a graphics editing tool – what is it called?

A: Create
B: Draw
C: Graphic

5 – If you don’t like the default icon set in LibreOffice, how can you change it?

A: Under the Format menu
B: Via Tools > Options > View
C: Using an extension

6 – What’s the standard document format of LibreOffice called?

A: OpenDocument Format
B: OpenXML Format
C: LibreDocument Format

7 – What is a “Hybrid PDF?”

A: It includes interactive elements and animations
B: It includes all fonts, to display properly everywhere
C: It includes the original source document, to allow editing

8 – LibreOffice includes a dockable window to help you move around complex documents. What is it called?

A: DocBrowser
B: Navigator
C: Overview

9 – If you want Writer to automatically add numbered captions when inserting objects, where do you go?

A: Tools > Options > Objects > Preferences
B: Insert > Image > tick “Add captions” box
C: Tools > Options > LibreOffice Writer > AutoCaption

10 – With which major LibreOffice release did the branding change to include cubes?

A: LibreOffice 4
B: LibreOffice 5
C: LibreOffice 6

11 – LibreOffice 6.2 will include a new (optional) user interface design. What’s its name?

A: TabBar
B: GroupedBar
C: NotebookBar

12 – Where did the 2013 LibreOffice Conference take place?

A: Berlin
B: Milan
C: Paris

13 – And where will the 2019 Conference be?

A: Almeria
B: Stockholm
C: Budapest

14 – Markus Mohrhard is a long-time LibreOffice developer, who has been involved in the project since its early years. What is his nickname?

A: Moggi
B: Marko
C: Maggi

15 – Another hard-working member of the community is “raal”, who helps out with events in the Czech Republic. But what’s his real name?

A: Stanislav Horáček
B: Zdeněk Crhonek
C: Jan Dvořák

16 – Finally, who can join the LibreOffice project and help to improve the software?

A: Experienced C++ developers
B: Members of The Document Foundation
C: Absolutely anybody

And now, the answers:

1: C
2: B
3: A
4: B
5: B
6: A
7: C
8: B
9: C
10: C
11: C
12: B
13: A
14: A
15: B
16: C, of course!

We in the community wish you all a great Christmas and festive time, and a happy new year. Here’s to a great 2019, with many more LibreOffice releases, events and fun to be had!

Resolved - 2018-12-23 09:16:21 UTC

---

extensions check failed (server time: 2018-12-23 07:42:53 UTC)

Expected HTTP response status: 200, got: 503

Resolved - 2018-12-23 07:37:54 UTC

---

extensions check failed (server time: 2018-12-23 07:36:25 UTC)

Expected HTTP response status: 200, got: 503

Resolved - 2018-12-22 04:18:21 UTC

---

extensions check failed (server time: 2018-12-22 03:32:25 UTC)

Expected HTTP response status: 200, got: 503

LibreOffice has the capability to add references to a document and finally a bibliographical index, which is essential for scientific publications. The style of references depend on the journal and the discipline. So it is common to just add numbers in square brackets like [1] in engineering whereas humanities show name and year like (author, year).…

The post Save the bibliography? appeared first on LibreOffice Design Team.

Improve your C++ skills! Last week, we had a workshop covering an introduction to the language, and looking at functions and strings. Participants watched a couple of presentation videos, and then had the opportunity to put questions to experienced LibreOffice developers.

Well, the second workshop is coming up! On December 20 at 19:00 UTC, join us to discuss these topics: I/O streams and building LibreOffice! Beforehand, you can watch this video for an overview:

Then check out this page about I/O streams, and the building guides for LibreOffice. (You don’t have to read them all in detail, but take a look, and think of things you want to talk about!)

On December 20, you can join the discussion in the following ways:

• #libreoffice-dev on Freenode
• Our Jitsi channel

See you then!

Berlin, December 18, 2018 – The Document Foundation announces LibreOffice 6.1.4, the 4th minor release of the LibreOffice 6.1 family, targeted at tech savvy individuals: early adopters, technology enthusiasts and power users.

LibreOffice 6.1.4 provides over 120 bug and regression fixes over the previous version, contributed by a thriving community of developers, which are described in the change log pages: https://wiki.documentfoundation.org/Releases/6.1.4/RC1 (changed in RC1) and https://wiki.documentfoundation.org/Releases/6.1.4/RC2 (changed in RC2).

LibreOffice users are invited to join the community at https://ask.libreoffice.org, where they can get and provide user-to-user support. While TDF can not provide commercial level support, there are guides, manuals, tutorials and HowTo on the website and the wiki. Your donation help us make these available.

Enterprise deployments

LibreOffice 6.1.4 represents the bleeding edge in term of features for open source office suites, and as such is not optimized for enterprise class deployments, where features are less important than robustness. Users wanting a more mature version can download LibreOffice 6.0.7, which includes some months of back-ported fixes.

Value-added services for enterprise class deployments – related to software support, migrations and training – should be sourced from certified professionals (https://www.libreoffice.org/get-help/professional-support/). In addition, some of TDF Advisory Board members provide LibreOffice LTS (Long Term Supported) versions targeted to enterprise deployments (https://www.documentfoundation.org/governance/advisory-board/).

Sourcing enterprise class software and/or services from the ecosystem of certified professionals are the best support options for organizations deploying LibreOffice on a large number of desktops. In fact, these activities are contributed back to the project under the form of improvements to the software and the community, and trigger a virtuous circle which is beneficial to all parties, including users.

Availability of LibreOffice 6.1.4

LibreOffice 6.1.4 is immediately available from the following link: https://www.libreoffice.org/download/. Minimum requirements for proprietary operating systems are Microsoft Windows 7 SP1 and Apple macOS 10.9. Builds of the latest LibreOffice Online source code are available as Docker images: https://hub.docker.com/r/libreoffice/online/.

LibreOffice Online is fundamentally a server service, and should be installed and configured by adding cloud storage and an SSL certificate. It might be considered an enabling technology for the cloud services offered by ISPs or the private cloud of enterprises and large organizations.

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

LibreOffice 6.1.4 is built with document conversion libraries from the Document Liberation Project: https://www.documentliberation.org.

Am 15.12.2018 wurde die neueste Special Edition des Linux Pro Magazine mit dem Thema #LibreOffice veröffentlicht. CIB ist als kompetenter Partner und langjähriger Supporter von LibreOffice natürlich in der Ausgabe vertreten und gleich mit zwei Anzeigen dabei. On 15.12.2018 the latest special edition of the Linux Pro Magazine concerning #LibreOffice has been published.  As a … LibreOffice powered by CIB @ Linux Pro Magazine weiterlesen

After the first and second Bug Hunting Sessions of LibreOffice 6.2, which were held on October 22th 2018 and November 19th 2018 respectively, we’re glad to announce the third and final Bug Hunting Session for LibreOffice 6.2 on December 21st. You can see the release notes describing the new features here.

In order to find, report and triage bugs, the tests during the Third Bug Hunting Session will be performed on the first Release Candidate (RC1) version of LibreOffice 6.2, which will be available on the pre-releases server on the day of the event. Builds will be available for Linux (DEB and RPM), macOS and Windows.

Mentors will be available on December 21st 2018, from 7AM UTC to 19PM UTC for questions or help in the IRC channel: #libreoffice-qa (connect via webchat) and its Telegram bridge. Of course, hunting bugs will be possible also on other days, as the builds of this particular Release Candidate (LibreOffice 6.2.0 RC1) will be available until mid January, 2019. See the release plan.

During the day there will be two dedicated sessions, one about the new KDE5 Integration between 11AM UTC and 13PM UTC and the other about the tabbed NotebookBar from 15PM UTC to 17PM UTC as it is not experimental anymore.

As you may know, I was participating in this year Gerrit User Summit, 15th-16th November 2018 in Palo Alto, CA.

I gave two talks: Bazel build gerrit: New and Noteworthy about optimizing Gerrit Build with Bazel and Gerrit Change Workflows with details about interesting multi stop journey that replaced somewhat confusing Draft change/Draft patchset workflows with streamlined Work-In-Progress workflow.

There were plenty of great talks, including Gerrit Analytics, Kubernetes, Multi-Site and Mulit-Master deployments and details about new and shiny Gerrit 3.0 that is going to be tentatively released in Q2 2019.

During the developer hackathon, that took place before the user conference, Gerrit 2.16 release was conducted. Major new feature is: new UI has reached parity with the old GWT UI and therefore old GWT UI is deprecated in 2.16 and in fact was already removed on master and will not be included any more in Gerrit 3.0. Another major feature is Git protocol version 2.0 is fully supported through HTTP and SSH layers.

This release also included small improvements, like simplified debugging capability for UI, SSH and GIT requests. Moreover, submit rules can now be written in Java language as a Gerrit plugin, in addition to Prolog rules.

I would like to thank GerritForge Ltd. for sponsoring travel cost for my participation.

2018 has been a very special year – we were celebrating the 10th anniversary of Gerrit, on 14th November, 2018. 10 years ago Shawn Pierce created a first commit in Gerrit repository. It is such a terrible loss for the whole open source community in general and for Gerrit ecosystem in particular that long-time Git contributor and founder of the Gerrit Code Review project, passed away in January this year.

Last year we revised the workflow to insert special characters. Based on a design proposal the dialog was reimplemented in a Google Summer of Code project by Akshay Deep. The new dialog allows to easily browse through the list and to search for glyphs contained in the selected font.…

The post Special Characters: The Final Touch appeared first on LibreOffice Design Team.

What i love in Ubuntu : woobly windows via compiz https://code.mradford.com/post/the-ubuntu-compiz-desktop/

After a great LibreOffice Conference, followed by the LibreOffice Hackfest held at modulE and the SFSCon in Bolzano sponsored by CIB, the LibreOffice community met again in Sanremo on December 1st, for the annual conference of the Italian supporters and contributors, members of the LibreItalia association. Unfortunately CIB wasn´t able to attend the event, but thanks … LibreItalia Conference 2018 weiterlesen

General Activities

• LibreOffice 6.2 beta1 was released
• On November 19, the bug hunting session for LibreOffice 6.2 beta1 took place
• Tabbed notebookbar moved out of experimental
• Miklos Vajna (Collabora) worked on improving Smartart
• In the FR community Pierre Choffardet has been very active these last days, helped by other members of FR QA team, he narrowed several bugs like: bug 121128, bug 121116, bug 121117, bug 121118, bug 121119, bug 121120
• Németh László worked on improving LibreLogo
• Telesto tested LibreOffice 6.2 on MacOSX in deep
• Vera Blagoveschenskaya tested KDE5
• Markus Mohrhard fixed many chart bugs
• Mike Kaganski (Collabora) implemented a proper console mode on Windows.
• Liad Skiva found some crashes in the properties dialog
• Many bugs found by NISZ LibreOffice Team regarding interoperability
• Franklin Weng, Cheng-Chia Tseng and Jeff Huang hosted a QA event at the University of Cheng-Kung, Taiwan, where 70 students attended.
• Bartosz Kosiorek improved EMF+ support with several patches
• Mark Hung improved slideshow rendering with several patches
• Jens Carl moved dozens of Java tests to C++
• Zdeněk Crhonek created two dozen UI tests
• Tomaž Vajngerl ( Collabora ) worked on Document encription
• Rizal Muttaqin worked on Elementary icons
• Jim Raykowski collaborated with Andreas Kainz to make Notebookbars accessible
• Daniel Silva rebase his work from the GSOC on the new print dialog into master
• Michael Stahl rebase his work on redlinehide into master
• Aleksei Nikiforov fixed some KDE5 issues

Reported Bugs

741 bugs have been reported by 390 people.

Top 10 Reporters

1. NISZ LibreOffice Team ( 45 )
2. Telesto ( 41 )
3. Xisco Faulí ( 27 )
4. Vera Blagoveschenskaya ( 20 )
5. 和尚蟹 ( 12 )
6. robert ( 11 )
7. Roman Kuznetsov ( 11 )
8. Gabor Kelemen ( 11 )
9. Pedro ( 11 )
10. Regina Henschel ( 11 )

Triaged Bugs

813 bugs have been triaged by 86 people.

Top 10 Triagers

1. Xisco Faulí ( 286 )
2. Dieter Praas ( 51 )
3. Heiko Tietze ( 40 )
4. Oliver Brinzing ( 34 )
5. Timur ( 31 )
6. V Stuart Foote ( 29 )
7. raal ( 27 )
8. Alex Thurgood ( 27 )
9. Buovjaga ( 26 )
10. Aron Budea ( 15 )

Fixed Bugs

176 bugs have been fixed by 52 people.

Top 10 Fixers

1. Caolán McNamara ( 38 )
2. Markus Mohrhard ( 12 )
3. Mike Kaganski ( 9 )
4. Eike Rathke ( 8 )
5. Noel Grandin ( 7 )
6. andreas kainz ( 7 )
7. Regina Henschel ( 6 )
8. Xisco Fauli ( 6 )
9. Miklos Vajna ( 5 )
10. Samuel Mehrbrodt ( 5 )

List of critical bugs fixed

1. 121143 LibreOffice sends “your system has crashed” message if “Close Application” event is defined ( Thanks to Mike Kaganski )
2. 121538 choosing additional formatting in dialog insert fields cause crash (gen/gtk) ( Thanks to Caolán McNamara )
3. 121540 CRASH deleting a form from form navigator ( Thanks to Noel Grandin )
4. 121607 Crash when closing a document (being the only active) while being prompted for data source password ( Thanks to Caolán McNamara )
5. 121417 KDE5: Recent Documents -> Clear list leads to crash ( Thanks to Aleksei Nikiforov )
6. 121290 Crash, if press F4 for a selected callout ( Thanks to Caolán McNamara )
7. 121591 CRASH: Print Preview fails if cursor inside Floating frame ( Thanks to Mike Kaganski )
8. 121743 CRASH closing LibreOffice with Parameter dialog open ( Thanks to Caolán McNamara )
9. 121432 Pressing twice on the “Help” button causes LibreOffice application to crash when the focus is on one of the tabs on Properties window ( Thanks to Caolán McNamara )
10. 121746 CRASH closing LibreOffice with confirmation dialog open ( Thanks to Caolán McNamara )
11. 121263 Calc crashes when hide multiple sheets ( Thanks to Zdeněk Crhonek )
12. 120728 crash in report editing: insert page number in footer while header is active ( Thanks to Armin Le Grand )
13. 121179 FILEOPEN: Crash opening a certain file (gtk/gtk3) ( Thanks to Noel Grandin )
14. 121246 Crash clicking on ‘row’ of a chart (with missing chart bars) ( Thanks to Caolán McNamara )
15. 120997 Crash after Ctrl+Tab to traverse points of object ( Thanks to Noel Grandin )
16. 121644 Pressing on the “Reset” button when the writing focus is on the “Value” input field of a property causes LibreOffice to crash on Properties – Custom Properties ( Thanks to Caolán McNamara )
17. 121005 Crash in: libc-2.24.so ( only 6.1 ) ( Thanks to Caolán McNamara )
18. 121198 CRASH in SdrPage::GetPageNum() ( Thanks to Xisco Fauli )
19. 121647 font list box preview certain malformed TTF fonts crash LO — when receiving ShouldUseWinMetrics() handling ( Thanks to Xisco Fauli )
20. 121394 CRASH: Opening area dialog ( gtk3 ) ( Thanks to Caolán McNamara )
21. 120115 Crash in: SfxItemSet::GetItemState ( Thanks to Bjoern Michaelsen )
22. 119945 Impress/Draw hangs/crashes when exiting while editing formula ( Thanks to Mike Kaganski )
23. 112696 Crash in: SwFEShell::IsGroupSelected() ( Thanks to Caolán McNamara )
24. 121341 choosing insert trend line causes crash ( Thanks to Caolán McNamara )

Verified bug fixes

93 bugs have been verified by 15 people.

Top 10 Verifiers

1. Xisco Faulí ( 52 )
2. BogdanB ( 16 )
3. Vera Blagoveschenskaya ( 7 )
4. Aron Budea ( 3 )
5. Michael Weghorn ( 2 )
6. Cor Nouws ( 2 )
7. V Stuart Foote ( 2 )
8. Xavier Van Wijmeersch ( 2 )
9. Micha ( 1 )
10. Timur ( 1 )

Categorized Bugs

408 bugs have been categorized with a metabug by 36 people.

Top 10 Categorizers

1. Thomas Lendo ( 163 )
2. Dieter Praas ( 57 )
3. Xisco Faulí ( 38 )
4. Aron Budea ( 27 )
5. Roman Kuznetsov ( 18 )
6. Julien Nabet ( 15 )
7. V Stuart Foote ( 14 )
8. Vera Blagoveschenskaya ( 12 )
9. raal ( 6 )
10. Heiko Tietze ( 6 )

Regression Bugs

127 bugs have been set as regressions by 21 people.

Top 10

1. Xisco Faulí ( 68 )
2. raal ( 11 )
3. Alex Thurgood ( 7 )
4. Telesto ( 6 )
5. Timur ( 5 )
6. Buovjaga ( 4 )
7. Roman Kuznetsov ( 4 )
8. Luke ( 4 )
9. Aron Budea ( 3 )
10. Regina Henschel ( 2 )

Bisected Bugs

102 bugs have been bisected by 7 people.

Top 10 Bisecters

1. Xisco Faulí ( 72 )
2. raal ( 13 )
3. Aron Budea ( 9 )
4. Oliver Brinzing ( 3 )
5. Telesto ( 2 )
6. Luke ( 2 )
7. Buovjaga ( 1 )

 
 
 

Evolution of Unconfirmed Bugs

Evolution of Open Regressions

Evolution of Most Pressing Bugs

Thank you all for making Libreoffice rock!
Join us and help to keep LibreOffice super reliable!
Check the Get Involved page out now!…

The post QA Report: November 2018 appeared first on LibreOffice QA Blog.

LibreOffice has always supported usage of command line switches that allow operations like conversion of documents to different file types, or batch-printing. Using LibreOffice CLI in various scripts is a very common scenario.

But until now, it had somewhat suboptimal support for this on Windows. The main executable module – soffice.bin – being a GUI subsystem application, it could not properly output its messages to the calling console, as well as return error codes to check ERRORLEVEL for success. The hacks used to redirect the output of the GUI application to the calling console were unreliable and didn’t work at all on some supported versions of Windows. Sometimes one could not even see why the entered command line was rejected as invalid.

I have just pushed a commit that changes the situation. Now LibreOffice has proper console mode on Windows. soffice.bin is now built for console subsystem, which allows using it in abovementioned scenarios, having the stdout and stderr output, as well as return code, properly sent to console (or redirected using normal means); in debug builds, the debug output is also visible on the console. To allow comfortable usage, a new console launcher executable is introduced, soffice.com, in LibreOffice installation’s program/ folder, alongside with familiar soffice.exe, which is retained for all GUI uses, as before. This allows to continue using command lines like
"c:\Program Files\LibreOffice\program\soffice" --convert-to odt file.doc
from cmd.exe command-line interpreter, without specifying the executable extension, and have the soffice.com launched to have proper console operation (subject to value of PATHEXT environment variable). The command properly “owns” the console (does not return to command prompt) until soffice finishes.

The change will be available in LibreOffice 6.3 scheduled for Summer 2019 (if testing does not reveal a major problem which would require to revert this). I hope this will make use of LibreOffice CLI more comfortable for Windows users, on par with other platforms. If you find any problems with the solution, please report bugs to our bug tracker. Early testing using daily builds is much appreciated!

Anyone who follows my LibreOffice work knows that I spent quite some time on the automated testing frameworks for LibreOffice. As part of this blog I want to use the LibreOffice 6.2 branch-off as a chance to look at current automated testing related statistics. All of the numbers were generated on 2018-11-1, so might already be slightly outdated.

We currently have 4804 different C++ based test cases in 357 different test suites and contain a total of 26215 test asserts. The largest test suite is ucalc (a test suite in Calc that links statically against the main calc library) with nearly 25000 lines of code in several files and 291 test cases.

In addition to our normal C++ based tests, we also have 409 UI tests in 39 test suites. As part of the UI tests we have another 2282 assert statements. A special thanks here to Zdeněk Crhonek who has written 154 commits adding UI tests in 2018. Everyone else together wrote about 45 patches this year touching the UI testing code.

Less well known test concepts in LibreOffice include our callgrind based performance testing (26 out-of-tree test cases and 25 in-tree test cases) and the automatic import and export crash testing with nearly 100000 documents. We managed to run the automatic import and export crash testing, which also generates more than 200000 documents for the export tests, a total of 73 times this year.

Another interesting statistics of this year is that the bug report with the most linked commits is related to the automated testing. As part of the Bug tdf#45904 several brave LibreOffice developers, including Jens Carl and Rahul Gurung, have converted more than 40000 lines of old Java based API tests to C++. In total they have produced more than 60 commits that have been linked to the bug report in 2018 alone and 132 since 2016.

I’m most likely forgetting some additional test frameworks but wanted to give a short overview of all the work that goes into LibreOffice’s automated testing framework. If you are interested in joining the effort please talk to us on #libreoffice-dev or mail the LibreOffice developer mailing list at [email protected]. We have tasks in the automated testing area in C++, python, java and some web related tasks.

 

The LibreOffice Quality Assurance ( QA ) Team is happy to announce LibreOffice 6.2 Beta1 is ready for testing!

LibreOffice 6.2 will be released as final at the beginning of February, 2019, being LibreOffice 6.2 Beta1 the second pre-release since the development of version 6.2 started in mid May, 2018. See the release plan. Since LibreOffice Alpha 1, 1252 commits have been submitted to the code repository and more than 178 bugs have been set to FIXED in Bugzilla. Check the release notes to find the new features included in this version of LibreOffice.

LibreOffice 6.2 Beta1 can be downloaded from here, and it’s available for Linux, MacOS and Windows. Besides, it can be installed along with your actual installation.

In case you find any problem in this pre-release, please report it in Bugzilla ( You just need a legit email account in order to create a new account ) so it can get fixed before LibreOffice 6.2 final is released.

For help, you can contact us directly in our IRC channel.

Happy testing!!

…

The post LibreOffice 6.2 Beta1 ready for testing appeared first on LibreOffice QA Blog.

On Friday 16th we attended the SFScon, the most important and biggest Free Software conference in Italy, and a well known event all over Europe, too. We are proud to have sponsored this enlightening conference where experts from all over the world were discussing about free and open source software, community and innovative solutions for … Free Software Conference – SFScon weiterlesen

It was all started with the 16px blue folder that had a striking color at the time. I was really uncomfortable seeing an icon which had unmatched color choice with the larger one. It was looked so so out of place.

You Are So Out of Place, Boy

That is part of the elementary icon theme in LibreOffice that placed in LIBREOFFICE-INST-DIR/share/config/images_elementary.zip.
As soon as I unpacked the compressed file, my response at that time was "Wow, it looks like this icon theme needs more touch"

Maybe some of you know that in the latest fresh release (6.1), I managed to send my work to upstream: Karasa Jaga icon theme. That was my first real "visible" contribution so far. Unfortunately, Karasa Jaga has not been being default in any desktop environment nor operating system. So when I saw elementary, which is now the default theme of the GNOME desktop environment and its derivatives, I suddenly felt called back to plunge and immediately give more attention to this another colored icon theme.

elementary icon theme has indeed been "completed" last year, but I think there are many things that turn out to be many home works. Here some issues I've found:

1. Blurry Appearance, The Pixels Did Not Fit Right

Blurred icons are usually due to drawing process that did not follow the guide lines that are commonly available in drawing applications such as Inkscape. This causes the icon to look less clear and certainly not satisfying.

Let me show you some of the opaque icons I've found and also the work that has been done:

Blurred icons

2. Childish Appearance
Looked so unprofessional, such as being drawn in a hurry situation, especially the smallest size of 16 px, they did not meet the official HIG from elementary own.

Childish, yeaa

3. Different Appearance Between 16px*16px and 24px*24px Version
This is quite funny, but still annoying

Inconsistencies Here and There

3. Missing Many Fall Backed uno: Commands
So by default if a theme lack of an icon it will be eventually fall back to default - defined another icon theme. 

Fall Backed Menu Items

4. Missing Many Non cmd Components

As we know, Karasa Jaga, an icon theme derived from the Oxygen theme successfully entered the last fresh release of LibreOffice (6.1) on August. Since its inception for the first time, Karasa Jaga has been very complete and can even be said to have nearly 5,000 icons, because it has exceeded the number of icons that Galaxy and Colibre have had since first entering Karasa Jaga already has extra large icon support (32px * 32px).

But the work did not stop there, there were many things that should be improved. Moreover, in the next 6.2 release there are so many new icons that should be made especially to support the Notebookbar Tab interface. In addition, the existing icons also need to be adjusted, plus I want to add more SVG support.

Now I would like to show you the improvements that have been made to Karasa Jaga. Although in this period I was more preoccupied with improving the elementary icon theme, I did not leave the mandate to improve Karasa Jaga, just like I took care of my own child. :) I admit that for this period the improvement were not as massive as previously released, but significant enough to be discussed as well. Let's see

Before After

Before After Reference: https://gerrit.libreoffice.org/#/c/63315/

Now I would like to show you my two months work against LibreOffice elementary icon theme. This one just show you standard toolbar comparison between 6.1 version and 6.2 beta. To switch icon theme, select Tools > Options > View > Icon Style
To test latest work, you can download LibreOffice 6.2 beta : https://dev-builds.libreoffice.org/daily/master/

LibreOffice Writer

6.1

6.2 Beta

LibreOffice Calc

6.1

6.2 Beta

LibreOffice Impress

6.1

6.2 Beta

LibreOffice Draw

6.1

6.2 Beta

LibreOffice Base

6.1

6.2 Beta caption

With the support of the FSF.hu Foundation, I have successfully implemented some long-planned LibreLogo improvements. This has made LibreLogo more reliable in LibreOffice, helping more and more people to discover the beauty of programming with LibreLogo, like German schoolchildren or Italian kindergarten teachers. My developments:

• Adding LibreOffice unit tests for LibreLogo program execution and compiling. Based on this automated testing, Red Hat developer Stephan Bergmann has already found an interesting regex change in Python 3.7 (LibreLogo was written in Python programming language), and he has fixed LibreLogo, too.
• Compiling Logo expressions to Python, i.e. adding parentheses at the right places uses a parser instead of the former heuristic method. Thus, you can write arbitrarily complex expressions, either in combination with Python lists, and calling own Logo functions with more than one argument without parentheses. Note: In LibreLogo expressions you can use Logo and Python syntaxes at one time. To avoid conflict, now parenthesis directly following the function name, eg. in “sin(x) * 2” denotes Python syntax, (meaning 2·sin(x)), while the space separated version, eg. “sin (x) * 2”, denotes Logo syntax (meaning “sin(2·x)”, as the simpler Logo expression “sin x * 2”).
• Function definitions and Logo-like function calls can be in any order, resulting for example completely Logo-like dragon curve drawing Logo program (see on the attached screenshot).
• Fix of the “magic wand” icon enables a two-sided view, keeping also the debug function “jump text cursor to the wrong LibreLogo program line at compiling”.
• We can write ASCII and typographical apostrophes in character strings.
• The running program stops immediately by clicking the Cancel button on the dialog window of the commands INPUT and PRINT (no need to wait starting a new loop in cycles).
• One of the goals of the planned future LibreLogo developments is to provide a more detailed documentation of LibreLogo’s Python source code. As you can see, I have already tried to do this in the current patches.

These developments will appear soon in the next preliminary version of LibreOffice 6.2.

what is new:

• Elementary icon theme update
• Tabbed Toolbar for writer, calc, impress and draw (Optional)
• …

Can we say Elasticsearch is great for localized search? Let’s do a check. It is an engine that gives you most of the standard search features out of the box. There are many ways to look for an optimal window to implement fast and indexed document search, scoring docs based on certain formulas, autocomplete search, context suggestion, localized text comparison based on analyzers and so on!

I am here to discuss about implementing a localized search for remote languages, regardless of being supported by analyzers in ES or not and how to get good results (for starters), if not the best.

I will use Node.js and ES as the technical stack. Let’s define some standard types for our index schema. I have three cases considered here:

1. English Analyzer
2. Hindi Analyzer (Comes tagged with ES. See: Language Analyzers)
3. Standard Analyzer (Use if your language does not have an inbuilt analyzer in ES)

We need to define the schema in a way to support all the standard types. I have chosen three languages to display search. English, Hindi ( Indian native ), and Telugu (Regional South Indian Language with no default analyzer in ES).

We have Telugu under standard analyzer as it is based on the Unicode Text Segmentation algorithm, as specified in Unicode Standard Annex #29 and works well for most languages. We can also use Simple Analyzer as it is a modified form of Standard Analyzer and divides text on characters which are not a letter.

Now, we have a schema defined. Next, you create an index with the schema and populate the index with related documents. I am not sharing actual documents which were used for my testing, but one can find text resources online to populate an index. For Node.js, one can use ES client for Node.js, or an easier way would be ES rest API.

There is a whole variety of search one can perform on a document having the above schema for all fields with custom analyzers. [ Full-Text Queries in ES ]

I was able to get great search results for English and Hindi, and search results for Telugu were not much below the bar. The ease with which one can create an almost real-time search engine is something unbelievable. I have not gone into many technical details of analyzers and how they function by combining the appropriate character filters, tokenizer, and token filters. It is expected for a standard analyzer to be just acceptable with the results, of course, it is only for starters. An Elasticsearch user must implement full-fledged custom analyzer for a regional language to get more accurate results. Moreover, ES provides with few add-ons for Asian languages such as Korean, Chinese, etc.

So, we can conclude that Elasticsearch is indeed great to boost your product’s localization and accessibility in small time cost and high return value.

After releasing Hunspell 1.7 with several improvements, including the fast and better spelling suggestion, I publish the extended version of my presentation at LiboCon, Tirana: LibreOffice Language Technology – News & Best practices. I suggest checking its content especially for members of native language groups. I have listed several ideas, examples and code pointers to improve the support of your language in LibreOffice, helping your LibreOffice users.

Ich hatte an der HTW Dresden die Gelegenheit, einen Vortrag zum Thema “The Document Foundation als Beispiel für Governance in Open-Source-Projekten” zu halten.

Die Folien stehen hier zum Download zur Verfügung (PDF-Datei, 1,9 MB).

Als ergänzende Lektüre gibt’s noch die Folien zu den “Zehn Zutaten für eine zufriedene Community“.

The Document Foundation als Beispiel für Governance in Open-Source-Projekten (Vortrag an der HTW Dresden 2018)

Standard toolbar will be standard, there is NO change planned!

Click to view slideshow.

But that doesn’t mean that you are not allowed to play with different UI designes.

Check out LibreOffice master: Download LibreOffice Master

If you like my work, become a

Edit your Tables wherever you want