Investigating

FOSDEM is one of the largest gatherings of Free Software contributors in the world and takes place each year in Brussels (Belgium) at the ULB Campus Solbosch. In 2019, it will be held on Saturday February 2, and Sunday February 3.

The Open Document Editors DevRoom is scheduled for Saturday, February 2 (from 10:30AM to 7:00PM, room UB2.147).

We are inviting proposals for talks about Open Document Editors or the ODF standard document format, on topics such as code, localization, QA, UX, tools, extensions and adoption-related cases. Please keep in mind that product pitches are not allowed at FOSDEM.

The length of talks should be limited to a maximum of 25 minutes, as we would like to have questions after each presentation, and to fit as many presenters as possible in the schedule. Exceptions must be explicitly requested and justified. You may be assigned LESS time than you request.

All submissions have to be made in the Pentabarf event planning tool: https://penta.fosdem.org/submission/FOSDEM19.

While filing your proposal, please provide the title of your talk, a short abstract (one or two paragraphs), some information about yourself (name, bio and photo, but please do remember that your profile might be already stored in Pentabarf).

To submit your talk, click on “Create Event”, then make sure to select the “Open Document Editors” devroom as the “Track”. Otherwise, your talk will not be even considered for any devroom at all.

If you already have a Pentabarf account from a previous year, even if your talk was not accepted, please reuse it. Create an account if, and only if, you don’t have one from a previous year. If you have any issues with Pentabarf, please contact ode-devroom-manager@fosdem.org.

The deadline is Monday, December 24, 2018. Accepted speakers will be notified by Thursday, December 27, 2018. The schedule will be published on Monday, December 31, 2018.

Recording Permission

We will record and stream all main tracks, devrooms and lightning talks live. The recordings will be published under the same licence as all FOSDEM content (CC-BY). If, exceptionally, you believe there is a legitimate reason why your presentation should not be streamed or recorded, you must seek our agreement before submitting it.

In the “Submission notes” field, please indicate that you agree to have your presentation recorded and published under the same license as all FOSDEM content (CC-BY). For example: “If my speech is accepted for FOSDEM, I hereby agree to be recorded and to have recordings – including slides and other presentation related documents – published under the Creative Commons Attribution (CC-BY) 4.0 International License. Sincerely, Name”.

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/

The Document Liberation Project (DLP) is a sister project to LibreOffice, and provides many software libraries for reading and writing a large range of file formats – such as files created by other productivity tools. Thanks to the DLP, LibreOffice (and other programs) can open many legacy, proprietary documents, but there’s always room for improvement! Check out this short video to learn more:

A picture of contributors attending LibOCon in Tirana, during a break. Most of them could travel to Albania thanks to the economic resources made available by our generous donors. Consider a donation to LibreOffice, to support our contributors traveling to events to talk about LibreOffice and ODF: https://www.libreoffice.org/donate

Many companies around the world use free and open source software (FOSS) to reduce costs, improve reliability, and free themselves from vendor lock-in. Today we talk to Iwan Tahari from FANS, an Indonesian shoe manufacturer, which has migrated to GNU/Linux and LibreOffice:

Firstly, tell us about your company, and your role in it…

I work at the FANS shoes factory in Tangerang, Indonesia. Our company has produced FANS shoes since 2001. As an Operation Director, I have to maintain smooth operation in the whole process, to improve our product quality and services. Currently, we have remote offices in Medan, Palembang, Surabaya and Solo that connect directly to our factory in Tangerang. All of our offices use free and open source software for daily operations.

When did you decide to migrate to open source software – and why?

We started to introduce FOSS to our staff in 2007 by dual-booting MEPIS Linux and Microsoft Windows XP on one out of three PCs that we had. It was a complete failure; the users almost never booted into MEPIS. Learning from the past mistakes, in 2012 we did a partial migration with five new notebook PCs installed with Linux Mint 13, for all managers and some higher-level staff members. Seven old PCs were still running Windows XP.

In 2013, we migrated almost all of the PCs to FOSS – only one Windows PC was left in the research and development department, because it was still using Corel Draw. In March 2014, we had a special training for using Inkscape, a vector graphics program. After the training, we fully migrated to FOSS. As of today, we still use only FOSS in all of our operations.

The main reason we migrated to FOSS was to have reliable and stable operations. Around 2012-2013, there was a nasty computer virus in Indonesia called Brontok. The main anti-virus programs were not fast enough to handle the widespread attack, so the only way to fix it was to reinstall the operating system.

This was so bad because of the high downtime in the reinstallation process. The only PCs that were not affected were Linux-based PCs. Since we migrated to FOSS, we have never reinstalled the operating system because of viruses or malware, even though we never use anti-virus software on our Linux-based PCs.

The other reason we use FOSS is cost-saving. Proprietary licenses are very costly; for each application we have to purchase separate licenses for each machine, while with FOSS the programs are completely free and we can install them on as many machines as we want. Our company has saved 133 millions Rupiah by using FOSS (around USD 10,000).

Tell us about your initial experiences with FOSS…

My first experience with open source software as when I was a university student. I graduated from CalPoly (California Polytechnic State University) in San Luis Obispo. My major is MIS (Management of Information Systems). One of our computer classes introduced us to Red Hat Linux. Honestly, I didn’t have a good experience with it (I believe it was Red Hat 4.0).

It took a long time and it was very complicated just to install the OS on an early Pentium machine (just to get the display to work correctly, and the configuration was really difficult for a regular user too). Well, it had a GUI, and some applications like AbiWord and Gnumeric but it was painfully slow. So at that time I believed that open source software was not for a regular users.

After I graduated, I worked in the logistics department of PT. Rodamas Jakarta (a nation-wide distribution company). One day, I saw InfoLinux magazine (a local Indonesian magazine that focuses on open source software) in the IT department. The magazine had a lot of good articles, and it came with a CD/DVD that contained a variety of Linux distributions. I also subscribed to this magazine. I become more interested in the open source world, and tried several live distributions like Knoppix without installing the OS.

Some came with OpenOffice which was similar to Microsoft Office. I liked OpenOffice better than Gnumeric and Abiword. My wife used to work in Haga Bank (a local Indonesian bank now acquired by Rabobank). Her office was using Fedora Linux and OpenOffice for daily operations without any critical problems. Learning from her experiences, when I became Operation Director at FANS shoes, I started the FOSS migration.

Why did you choose LibreOffice?

Because most Linux distros thesedays come with LibreOffice. It’s better to use the office suite that comes with the distro; it saves us time, as we don’t have to install another suite. For our company, LibreOffice is the best replacement for Microsoft Office. If there were no LibreOffice, we would probably have never migrated to FOSS.

I have an interesting story about LibreOffice: one time, my brother called me to ask for some help with his computer. He said he had received a Microsoft Office document file (docx), but he couldn’t open it. Unfortunately, his computer had an outdated OS and MS Office (Windows XP and Office XP).

He said that it’s urgent, that he needed to read the content of this document now. Well, it was late at night, so he was not able to get the installer from the computer store. So I said to him, try downloading LibreOffice, and see if it can open the file. So, he installed LibreOffice in his PC. He was really fortunate that the docx file could be opened with just a little problem (the text was not aligned properly), but at least it was readable. Since then, his computer has LibreOffice, and he continues to use it.

How popular is FOSS in Indonesia?

Open source in Indonesia is getting more popular. In the server market, open source solutions are growing rapidly here because they are cheaper than proprietary software. Unfortunately, it is not the same for daily home or office use of FOSS. Proprietary software like Windows, Office, Adobe suite, Corel Draw etc. are so dominant here. People are already familiar with these proprietary programs and are hesitate to change. Piracy is the main cause of the slow growth of FOSS in Indonesia – currently, there are more people using pirated software than original legal software.

It is very easy to get pirated software in Indonesia. It can be acquired at many computer stores – and sometimes it is included for free when purchasing a PC. So in fact, it’s much easier to get pirated software than FOSS. Still, our government is a little bit strict with pirated software in medium and large companies. Because of that, some companies have adopted FOSS. So I believe Free Software will keep continue to grow in Indonesia, but the adoption rate of FOSS will depend on the how good its marketing is, and also how strict the law enforcement of pirated software is as well.

What were your personal experiences in the Indonesian open source community?

At the early stage of the FOSS migration, I pretty much did everything by myself. I learned FOSS mostly from the web. Fortunately, most FOSS literature is available in the English language, which I can understand. In our company, the LibreOffice migration was a lot easier compared with migrations to other programs like Inkscape and GIMP. At first, we were having trouble migrating to Inkscape until we met Sokhibi (owner of Istana Media, and writer of several open source books).

We invited him to train us using Inkscape. From there, he introduced us to Blankon Linux (a custom Indonesian Linux distro). He was the Documentation Coordinator of Blankon Linux. Then the Blankon community helped us a lot in our migration – we even have a custom version of Blankon Linux specifically for our company needs.

Together with Ahmad Haris (Blankon Public Relation Coordinator), we created a writing contest for using FOSS, and we released an Indonesian Inkscape guidebook. In 2015, we had the GNOME Asia Conference in Indonesia – this was my first time being a guest speaker at a FOSS conference. I met so many excellent people from around the world that were helping the FOSS movement! I was introduced to other local open source communities (such as openSUSE Indonesia, Ubuntu Indonesia, the Indonesian Linux User Group etc).

Since then, I have been active with our local FOSS community, and our company has sponsored several FOSS activities/projects. In 2018, we held an Indonesian conference for LibreOffice. It was a big success, so many people are eager to know about the software. Sokhibi also released an Indonesian LibreOffice Writer guide, which is sponsored by our company.

The LibreOffice project was born in Europe, and had strong roots in that continent. What should we do to increase the market penetration in Indonesia?

It should be easy for LibreOffice to become more widespread in Indonesia. Most Linux distributions already include LibreOffice, so it’s no problem for Indonesian Linux users. Now, the problem is that there are only a small amount of Linux users here. LibreOffice is not known to most Windows users. I think LibreOffice’s marketing community needs to learn/adopt the strategy of Mozilla Firefox in winning the browser war with Internet Explorer. VLC (VideoLan Client) is also another successful open source software that is widely adopted in Indonesia. So these things need to be done:

1. Win the format war with MS Office
2. Local content (tutorial, books for using LibreOffice in Indonesian language) – LibreOffice’s Help needs to be properly translated to Indonesian too
3. LibreOffice videos. We need a lot of videos about LibreOffice tutorials in Indonesian language. LibreOffice Promotion videos. All LibreOffice videos should be available on popular streaming media.
4. Active Indonesian LibreOffice social media (Facebook, Twitter, Instagram,etc) that are helping new users
5. Indonesian LibreOffice ambassadors that are active within the community
6. Reach out program toward schools and companies, and other institutions
7. LibreOffice events, like the 2018 conference in Indonesia are good to penetrate the Indonesian market. Smaller events like release parties or mini conferences are also good. We could have join events with other FOSS projects
8. LibreOffice marketing attribute like stickers, banners, T-shirts, etc
9. Support for other platforms. Fully working LibreOffice for other platforms (ARM, RISC V, MIPS) should be available. The current LibreOffice viewer in Android is not enough. LibreOffice should also be available on emerging market of single-board computer platforms like Rasberry Pi, etc.

Thinking of the culture barrier and language barrier: which is the bigger one for open source?

With better technology, the language barrier will become smaller and smaller. We can now use many translation applications to help people adopt FOSS in many different languages. However, a culture barrier like the “piracy culture” I mentioned is not an easy thing to be solved. Probably it needs several generations of efforts to significantly reduce it. To end piracy, people need to change their mindset which I think is very difficult. We need to fight this piracy culture because it is bad for the whole community. For Indonesia, I believe this is number one enemy to the FOSS movement.

Finally, where do you see LibreOffice in five years from now?

I see great prospects for LibreOffice. In five years, I am sure LibreOffice will be gaining more and more users. The format war will be a long war, but in the end, the Open Document Format (ODF) will win the war. Like the web browser wars where the proprietary browsers are losing, I believe LibreOffice will one day win over MS Office. From version to version, LibreOffice is getting better and better while still retaining format compatibility, which is the key benefit of using LibreOffice. I believe LibreOffice will have a high chance to become the most-used in Indonesia with great efforts. When LibreOffice becomes the number one office suite here, I think all of the remaining South East Asia countries will follow.

Thanks to Iwan for his thoughts and feedback! One of the goals of LibreOffice is to be available in as many languages as possible, so if you’re reading this and want to help translate the interface into your native language see here to get started!

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

Thanks to the resources made available by our generous donors, we can organise workshops to educate volunteers about the migration process to LibreOffice and Open Document Format. If you support our activity, you should consider a donation to grow the project and extend our activities to more geographies.

Resolved - 2018-12-06 03:38:07 UTC

---

CI check failed (server time: 2018-12-06 03:35:37 UTC)

Expected HTTP response status: 200, got: 503

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. Luke ( 2 )
6. Telesto ( 2 )
7. Buovjaga ( 1 )

Evolution of Unconfirmed 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.

Resolved - 2018-12-02 10:32:37 UTC

---

CI check failed (server time: 2018-12-02 07:19:07 UTC)

Expected HTTP response status: 200, got: 503

help check failed (server time: 2018-12-02 03:59:47 UTC)

Get https://help.libreoffice.org/help.html: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

Resolved - 2018-11-28 20:39:31 UTC

---

extensions check failed (server time: 2018-11-28 20:38:22 UTC)

Expected HTTP response status: 200, got: 503

• Mail; continued debugging and polishing to a deadline. Interested by the GNU Kind communication controversy. Interested and pleased that the strange mix of libertarian, campaigning and (perhaps overly) permissive roots of the GNU project are still being championed by Richard, despite other views being represented. Still thinking through my take on the pronoun topic which intersects respect, integrity, truthfulness and much more. I find the Roman Catholic compromise interesting. What do you do when faced with a dogmatic requirement to call someone's interpretation of faith and hierarchy the one true/universal view ? What if you profoundly, but respectfully disagree with chunks of their doctrine and practice ? Do you go for Papist (rather divisive), some re-define the term to mean the universal set of all true Christians ? (but that doesn't help with the identity question). How about a fudge that acknowledges the chosen name and also the real identity of the one making the claim, in some suitable way (ie. Roman Catholic). Of course, there are plenty of weaker truth claims out there Unification Church vs. ~pejorative Moonies etc. Interestingly google tells me that these days catholic means "including a wide variety of things; all-embracing" with synonyms of: "diverse, eclectic ...". Perhaps a good thing to aspire to for communities seeking to accomodate and encourage dialog between those of widely varying ethical pre-suppositions.
• Prodded at the Chrome mobile device profiling bits - rather an excellent tool-set.

• Mail chew, dived into some hacking to help the team with their deadline; too fun - criminaly so; broke & re-assembled bits of code left & right. Worked excessively late - nice to have a continuous set of changes going in all night handing over from late-night Europe, to night Canada to early morning Russia, Europe. Tired.
• Coming increasingly to the conclusion that the HiDPI model of adding a scale-factor at the low-level rendering layer, while keeping the rest of layout, etc. working in a different co-ordinate space is the best of all worlds. Apple lead the way, gtk+ followed, and cairo makes it easy - even if the treasured shibboleths such as consistent height pixel aligned grid rendering need significant extra lifting. Not entirely clear how to do it through an integer pixel API though.

• Mail chew; partner call, sync with Daniel. Monthly all-hands. Hacking, call with Amir.

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!

• Mail chew, built ESC stats built slideware and stats. Lunch. Monthly commercial call. Worked at analysis, marketing bits with Amir & Eloy. Up late looking at documentation.

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 libreoffice@lists.freedesktop.org. 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.

• Mail chew, partner calls, sync with Miklos & Kendy.

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

LibreOffice individual apps universal useful.

Started with unsubscribing from mailinglists after a long day of skil enhencement.

In addition to finish rework in tabbed toolbar, context menu I also update the toolbar’s to have them more consistent between the different apps and within the app, so the UI jumping was reduced as much as possible.

Check out LibreOffice master: Download LibreOffice Master

If you like my work, become a

I attended my first after work health training today. The training took place within a group of eleven people. It picked the common health issues of office workers and will help to improve them. Nice evening within the group.

Afterwards driving home and pack the bag for a three days skill enhancement about current European topics.

Activities

• Text autofit confusion solved by Maxim Monastirsky.
• Several NotebookBar issues turned out to be gone after Andreas Kainz re-tested them.
• Jim Raykowski kept improving the Navigator and Sidebar with many commits.
• Brian Fraser continued to work on improvements to reordering of Impress animations.
• Justin Luth committed dozen of OOXML fixes.
• Mark Hung committed dozen of Impress fixes.
• Dozens of small fixes as a response to a PVS-Studio report. (Mike Kaganski (Collabora), Caolán McNamara (Red Hat), Xisco Fauli (TDF))
• Numerous performance issues reported by Telesto were triaged, some already fixed.
• Katarina Behrens (CIB) added drag&drop support to KDE5.
• Dozens of KDE5 backend issues in the 6.2 alpha1 were reported and triaged during the Bug Hunting Session.
• Usama and Buovjaga split an unusually complex report about Calc hyperlinks into multiple reports.
• Eike Rathke (Red Hat) implemented REGEX function
• Mert added language support to Android Viewer.
• Roman Kuznetsov re-tested many old bugs, some of which got closed as RESOLVED WORKSFORME.
• Zdeněk Crhonek added some new Uitests
• Muhammet Kara modernized and optimized Personas
• Rizal Muttaqin continues working on elementary icons

Reported Bugs

845 bugs have been reported by 408 people.

Top 10 Reporters

1. Telesto ( 67 )
2. Xisco Faulí ( 33 )
3. Daniel ( 32 )
4. Vera ( 23 )
5. Thomas Lendo ( 21 )
6. Aron Budea ( 19 )
7. Michael Weghorn ( 18 )
8. 和尚蟹 ( 15 )
9. andreas_k ( 15 )
10. Heiko Tietze ( 14 )

Triaged Bugs

861 bugs have been triaged by 81 people.

Top 10 Triagers

1. Xisco Faulí ( 205 )
2. Buovjaga ( 141 )
3. Dieter Praas ( 38 )
4. Heiko Tietze ( 38 )
5. Alex Thurgood ( 37 )
6. Oliver Brinzing ( 33 )
7. raal ( 29 )
8. V Stuart Foote ( 28 )
9. m.a.riosv ( 22 )
10. Mike Kaganski ( 22 )

Fixed Bugs

170 bugs have been fixed by 39 people.

Top 10 Fixers

1. Caolán McNamara ( 31 )
2. Eike Rathke ( 12 )
3. andreas kainz ( 11 )
4. Jim Raykowski ( 8 )
5. Julien Nabet ( 8 )
6. heiko tietze ( 8 )
7. Miklos Vajna ( 8 )
8. Muhammet Kara ( 7 )
9. Mike Kaganski ( 7 )
10. Jan-Marek Glogowski ( 6 )

List of critical bugs fixed

1. 120706 Crash in: SbxArray::Count() when trying to call a WinAPI function ( Thanks to Mike Kaganski )
2. 120387 EDITING Copy Chart Axis Title causes LibreOffice Calc crash ( Thanks to Jan-Marek Glogowski )
3. 120452 kde5: Impress crashes when opening slide containing video ( Thanks to Katarina Behrens )
4. 120261 gtk3_kde5: Crash with file dialog when Java extension “WollMux” is installed ( Thanks to Michael Weghorn )
5. 120782 Crash when dragging column from datasource to spreadsheet ( Thanks to Julien Nabet )
6. 120291 Attaching a connector makes draw Draw busy-loop and crash ( Thanks to Noel Grandin )
7. 120528 Crash when closing context menu in Data Provider dialog ( Thanks to Mike Kaganski )
8. 120785 CRASH: LibreOffice can be closed while Slide Design is open ( Thanks to Caolán McNamara )
9. 120451 kde5: Impress presentation mode crashes in single-monitor setup ( Thanks to Katarina Behrens )
10. 120334 Crash when closing dialog Position and Size ( Thanks to Caolán McNamara )
11. 120794 CRASH while selecting a drawing line ( Thanks to Noel Grandin )
12. 120731 Crash cuilo!makeAutoCorrEdit when open character dialog with large amount of text selected ( Thanks to Caolán McNamara )
13. 120862 Crash selecting a bullets or number item with double click ( Thanks to Caolán McNamara )
14. 120803 kde5: Impress crashes when exiting presentation mode ( Thanks to Katarina Behrens )
15. 120097 No document recovery dialog after a crash ( Thanks to Noel Grandin )
16. 120674 LibO crashes each time I try to add an object (button, check box, etc.) in a Dialog form ( Thanks to Armin Le Grand )
17. 120227 CRASH: Opening Format > Page in main menu crashes Calc ( Thanks to Caolán McNamara )
18. 120807 Crash on Crl+Shift+F10 in F5 floating Navigator page number field ( Thanks to Jan-Marek Glogowski )
19. 120487 Delete all comments leaves a comment box behind (and will end in a crash) ( not gtk3 ) ( Thanks to Caolán McNamara )
20. 118572 CRASH when an extension prompts an error from its own dialog ( Thanks to Caolán McNamara )
21. 120318 branch crashes in bibliography database -> Data -> autofilter ( Thanks to Julien Nabet )
22. 119067 REPORTBUILDER: Report label display string lost when saved and the actual string ‘LABEL’ used when the report is run next. ( Thanks to Armin Le Grand )
23. 120377 Impress crashes when change text animation to word by word. ( Thanks to Caolán McNamara )
24. 120830 CRASH opening Form-Based Filters ( Thanks to Noel Grandin )

Verified bug fixes

115 bugs have been verified by 19 people.

Top 10 Verifiers

1. Xisco Faulí ( 50 )
2. BogdanB ( 31 )
3. Thomas Lendo ( 9 )
4. Michael Weghorn ( 4 )
5. Buovjaga ( 3 )
6. Jean-Baptiste Faure ( 2 )
7. Timur ( 2 )
8. Heiko Tietze ( 2 )
9. Aron Budea ( 2 )
10. V Stuart Foote ( 1 )

Categorized Bugs

975 bugs have been categorized with a metabug by 34 people.

Top 10 Categorizers

1. Thomas Lendo ( 588 )
2. Aron Budea ( 71 )
3. Xisco Faulí ( 66 )
4. Heiko Tietze ( 47 )
5. Buovjaga ( 37 )
6. Rizal Muttaqin ( 30 )
7. Dieter Praas ( 30 )
8. Michael Weghorn ( 16 )
9. Vera ( 13 )
10. V Stuart Foote ( 11 )

Bisected Bugs

97 bugs have been bisected by 8 people.

Top 10 Bisecters

1. Xisco Faulí ( 72 )
2. Aron Budea ( 7 )
3. Buovjaga ( 6 )
4. raal ( 5 )
5. Oliver Brinzing ( 2 )
6. Telesto ( 2 )
7. Justin L ( 2 )
8. Roman Kuznetsov ( 1 )

Evolution of Unconfirmed 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: October 2018 appeared first on LibreOffice QA Blog.