- Mail chew, M. ill at home; picked up H. and Charlotte after an exam; built slides, poked projections. Lunch. Monthly mgmt call. Admin.
Andreas Kainz
LibreOffice Design Blog
LibreOffice QA Blog
Luboš Luňák
Marius Popa Adrian
Michael Meeks
Mike Kaganski
Miklos Vajna
Muhammet Kara
Official TDF Blog
Olivier Hallot
TDF Infrastructure Status
Last updated:
May 21, 2019 05:02 PM
All times are UTC.
Powered by:
Imprint
Privacy Policy
OW2con 2019 is the annual open source event bringing together the OW2 community, technology experts, software architects, IT project managers and decision-makers from around the world. The conference will be hosted by the Orange Gardens Innovation Center, Paris-Châtillon, on June 12-13, 2019.
The central theme of OW2con 2019 is: “Open Source Toward Industry Maturity”. Indeed, with open source becoming mainstream, IT developers, vendors, users and even open source organisations such as OW2 have to adapt. Today, open source projects are becoming increasingly competitive and all IT developers, vendors and users must have an open source strategy.
During OW2con 2019, The Document Foundation and LibreOffice Online will be presented during two different talks:
More information about OW2con 2019 are available on the event website: https://www.ow2con.org/view/2019/.
The LibreOffice Quality Assurance ( QA ) Team is happy to announce LibreOffice 6.3 Alpha1 is ready for testing!
LibreOffice 6.3 will be released as final in mid August ( Check the Release Plan ) being LibreOffice 6.3 Alpha1 the first pre-release since the development of version 6.3 started in mid November, 2018. Since then, 6390 commits have been submitted to the code repository and more than 1050 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.3 Alpha1 is already available for downloading here, 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 ).
For help, you can contact the QA Team directly in the QA IRC channel or via Telegram.
Happy testing!!
…
$ perf record -g ...$ perf script -s perf2calltree.py > perf.out$ kcachegrind perf.out
Learn C++ features with the help of LibreOffice developers! We’re running regular workshops which focus on a specific topic, and are accompanied by a real-time IRC meeting. For the next one, the topic is Binary Search Trees. Start by watching this presentation:
Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party.
If you accept this notice, your choice will be saved and the page will refresh.
And check out the suggested EasyHacks.
Then join us for a discussion via our #libreoffice-dev IRC channel on Freenode. You can ask experienced LibreOffice developers questions, and learn more about the language. We look forward to meeting you!
High packet loss ratio at the datacenter (or its upstream carriers) causes slowdown and service disruption. (Possibly depending on the IP protocol version and route taken.)
by The Document Foundation's Infrastructure Status at May 16, 2019 03:15 PM
It’s the Month of LibreOffice, and we’re awarding sticker packs – and the chance to win cool mugs – to all contributors in the project! On this page we’re maintaining a list of names/usernames for people who’re helping out, and everyone there can claim a sticker pack at the end! We’ll also choose 10 people at random to get one of the mugs. So, how many packs have been awarded so far?
But there are still two weeks to go, so if your name isn’t there, check below to see how you can get involved! Many tasks only take 10 or 20 minutes, but make a big difference to the project. (And if you have already contributed this month, but your name isn’t there, email us with details and we’ll look into it.)
There are many ways you can help out – and you don’t need to be a developer. For instance, you can be a…
So dive in, get involved and help make LibreOffice better for millions of people around the world – and enjoy your sticker as thanks from us. We’ll be posting regular updates on this blog and our Mastodon and Twitter accounts over the next four weeks!
Every year, The Document Foundation produces an Annual Report, detailing its activities in the projects and community. We’ll be posting parts of it here on the blog, while we prepare a final printed version…
In February, the Board of Directors of The Document Foundation – during its first meeting of the new term – confirmed Marina Latini in the role of Chairwoman, and appointed Björn Michaelsen to the role of Deputy Chairman.
Marina said: “Our project is growing fast with contributors from several countries, and we need to focus much more on lowering the barriers to being a really welcoming community. I would like our community to become as inclusive as possible, and never leave out those who, just in appearance, look different to us. Openness is a state of mind.”
Björn, who had previously served as a Deputy on the Board, added: “I am encouraged to see strong contributors to the project as new candidates in this election, and hope to share the duty of serving with them, together providing a strong and reasonable voice of independent and unaffiliated input in the Board. Ultimately, I hope after this one last term I can confidently leave TDF’s Board with many new diverse and independent voices in all parts of the project and foundation, and retire back to spending my contributions more on – for instance – the source code again.”
In May, TDF announced that BPM-Conseil, a company focused on open source business intelligence and based in Lyon (France), had joined the project’s Advisory Board. BPM-Conseil will develop the integration of LibreOffice with its business intelligence solutions Aklabox and Vanilla, and also create business intelligence-related extensions for LibreOffice.
BPM-Conseil is focused both on development of open source business intelligence solutions and on the related consultancy and integration activities. The company has a large roster of clients in France, such as the Ministries of Environment, Energy and Sea, Lyon Metropole, Nimes Metropole and City, La Rochelle Agglomeration, Haute and Basse Normandie, the Aveyron Department, and the University of Corsica.
In 2017, TDF launched four tenders aimed at sharing knowledge about improving LibreOffice in several strategic areas, where the tasks are beyond the capabilities of independent volunteer developers. In 2018, companies selected to implement two of the tenders reported back on their work.
Firstly, Collabora was selected for the tender “improve image handling in LibreOffice (#201705-01)”. A new image life-cycle was developed, with simpler memory management for handling images and new swapping strategy. The results were incorporated into the LibreOffice 6.1 release – and a more detailed technical description of the work is on the blog, in order to share knowledge and experience from this project with the developer community and the general public.
The second tender, “implement HSQLDB binary format import in LibreOffice (#201705-03)”, was also assigned to Collabora and implemented by Tamás Bunth. He developed a mechanism to import database files with high fidelity from the HSQLDB binary file format, used by many existing ODB files, by reading the Java serialization code, and writing a filter to import all data into LibreOffice Base. The objective was to remove the legacy Java/HSQLDB database and to simplify the move to Firebird. More details are provided here.
Throughout the year, TDF supported initiatives and campaigns from other organisations that promote free and open source software. For instance, in February, we joined “I love Free Software Day”, a campaign by the Free Software Foundation Europe (FSFE). As they explain: “We should remember the power of a simple ‘thank you’ to motivate Free Software contributors in their important work for society. And the 14th of February is the ideal day to do that.”
March 27 was “Document Freedom Day 2018”, a campaign about open standards and document formats, aimed at non-technical people. The goal is to make regular users more aware of interoperability issues, and the importance of storing documents (and indeed any kind of data) in open and standardised formats. This helps users to avoid vendor lock-in, giving them more freedom to use the software they want – and this is also important for governments, companies and organisations.
In September, we joined the “International Day against DRM”. DRM, or Digital Rights Management, is a set of access control technologies for restricting the use of proprietary hardware and copyrighted works, by controlling the use, modification, and distribution of copyrighted works. Instead of educating users, companies prefer to restrict them from exercising their legal rights under the copyright law.
DRM is an epidemic spreading across the web, infiltrating homes, classrooms, workplaces, and just about everywhere else users can go. Tools, technologies, books, games, movies, and music are coming to us locked down with DRM, whether they are streaming or claim to be locally hosted. TDF supports the International Day Against DRM as part of its daily fight to make content sharing available to all individuals, and to educate them to adopt open standards to foster innovation.
TDF also hosts and supports the Document Liberation Project (DLP), a sister project of LibreOffice, which fosters the development of software libraries that can import and export data in many different file formats. DLP libraries are used by many free and open source software projects, such as Inkscape, Scribus and LibreOffice, and help users to get control of their data – especially from old and proprietary file formats. In 2018, new libraries were added to the DLP project and the community produced videos encouraging people to contribute. Learn more about DLP in this quick video:
Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party.
If you accept this notice, your choice will be saved and the page will refresh.
Years ago I posted about a large rework to where Collabora helped a customer to make Writer read the drawingML markup for DOCX shapes. You can read the various benefits of this switch in that article — but similar to other large reworks, this also broke some previously working corner-cases, where test coverage lacked.
One of these is charts in group shapes. This needs explicit handling, as Writer normally handles charts as TextEmbeddedObjects, while code that imports charts from OOXML is not specific to Writer. The fix just tells the generic drawingML import to use a Writer-specific service name for the charts.
This is available in LibreOffice master (towards 6.3).
This year’s FOSDEM (Free and Open source Software Developers’ European Meeting) has been held in in the beautiful city of Brussels (Belgium), as usual, on February 2 & 3, 2019. It was organised by volunteers to promote the widespread use of free and open source software..
This was my first FOSDEM as a deputy member of the MC, and a fresh member of the Collabora team.
I will try to give some information about my talks, and share my experience.
The first 2 days was spent on the LibreOffice Hackfest, MC & BoD joint meetings. Seeing all friends face to face was a pleasure. We discussed some important matters face to face, and had a great time together.
Did some work on the LibreOffice themes, and discovered the ugly truth of major Mozilla API change.
We also had a community night/dinner with the LibreOffice community members on Saturday. Had pleasant chats with many friends, and a nice ‘kosher/halaal’ meal with Lior (thank you again!).
It was also a nice adventure, chasing Indian/Eastern/Asian tastes with Mike. :)
This year, I stayed with the pack in Bedford. Its location is perfect, but you may feel the building’s age. (In good & bad ways.) I had the first night with a semi-functional heater in the room. Not very pleasant, considering the winter of Brussels. Next day they gave a second portable heater -yay! :)-, and I survived with those.
Past, present, and the future of LibreOffice’s Personalization dialog.
LibreOffice has had the ability to use Mozilla Themes (Personas) for some time (Tools > Options > Personalization); but it kept breaking all the time, and never had an acceptable UX. Also tons of errors/warnings, and very slow search and apply processes almost brought it to the point of being killed for good. But I couldn’t let it die, started looking into the related code and the bug reports. Now it has a better UX/UI, and got most annoying bugs/crashers fixed, and is much faster.
I tried to present a summary about the journey so far, and the plans for the future.
Redaction in its sanitization sense (as distinguished from its other editing sense) is the blacking out or deletion of text in a document, or the result of such an effort. It is intended to allow the selective disclosure of information in a document while keeping other parts of the document secret. Typically the result is a document that is suitable for publication or for dissemination to others than the intended audience of the original document. For example, when a document is subpoenaed in a court case, information not specifically relevant to the case at hand is often redacted. Another example is patient information of hospitals, which is distributed to be used for research purposes.
A new document redaction feature for Collabora Office is being developed, and it will also be available on the next major version of LibreOffice. This new feature will provide a much more efficient means than the traditional print-redact-scan process, and will try to prevent also the accidental leakage of redacted information by completely removing them in the resulting PDF document, rather than just hiding.
Again a good use of time, full of experience sharing with fellow FLOSS developers, and community members.
Looking forward to the next FOSDEM! :)
by Muhammet Kara (muhammetk@gmail.com) at May 14, 2019 06:15 PM
You are one of the people who have been around from the beginning of The Document Foundation, and one of the oldest members of the community (including the years of OpenOffice.Org). How were you involved in the project?
I was using StarOffice 5.2 and was contributing support on the French speaking users list. When Sun Microsystems was about to open source the code and create the OpenOffice.org project, they invited me to join and support the community. From there, I’ve been involved in various tasks like localization, quality assurance or documentation.
We are getting close to the 10th anniversary of the LibreOffice project, and the 20th anniversary of the FLOSS office suite. Which are the milestones of this long history?
I may not remember all of them, but I guess the creation of the Native Language projects with the French speaking one as a Proof of Concept in 2001. Then the many community supported projects such as marketing, documentation, etc.
And then of course, the birth of the LibreOffice project. Since then I’ve the impression that each year is a milestone ;-)
There have been so many exciting things to do in each corner of the project. The community is pushing a lot of good ideas and energy. Considering the work done on QA, UX/Design and marketing for the product or the community, the new help system and the size of our infra, we have achieved more than we could even imagine ten years ago!
You have been involved in the localization of the software since the very first version, and now you are coordinating the activity of native language projects. Can you talk about the localization activity?
Localization is a complicated task, and sometime tedious. LibreOffice is a big software with thousands of different strings. Localization happens at the end of the software making process, so the workload depends on development, UX/Design and marketing projects.
Recently, there have been changes on the strings format for almost the entire interface of each module, on the help system and more and more marketing activities. Each localization member should be very proud of his/her work.
We want to cover more languages because localization is a way to preserve those languages, preserve the local culture and give all users the opportunity to express themselves in their own language. This is where my activities lie: understand the needs of localizers, voice their concerns, update the workflow and try to make them happy to translate the different projects.
You have been a member of the team for almost six years, with a number of different responsibilities. From your point of view, how well did the project during this time?
Happy to say: fairly well :-) The task was not easy but I believe we are doing right. Some people would like to see more things happening, or the project going faster or further. But we are a diverse community with different cultures, different business or occupations and different time zones!
We need to keep people together on the same path, to preserve the soul of the project. It’s not easy to keep an eye on the horizon on a daily basis, but our directors are doing that since the beginning and they are doing it very well if you look at the foundation’s results.
I can see my colleagues of the team working hard on each critical part of the production process, and at the same time taking care of the community, trying to answer end user questions and help independently from what they have on the table. I’m proud and very happy to be part of this team, and happy to see how mature the foundation has became. Every day I’m learning something new, either from them or from the community. I’m thankful for that :)
With the growth of the project and the community, you are now moving to the position of Foundation Coordinator. Can you describe this role?
I’m taking care of several foundation activities, like helping to organize LibOCon and Advisory Board meetings, and handling several administrative tasks. I’m also directly involved in L10n/NL, marketing and certification projects.
I follow what is happening in other parts of the project, and try to bring my help and my knowledge where needed. For example, when the work began on the UX, I helped the team with my knowledge of the product and its philosophy.
The change will happen mainly in the administrative parts, where an assistant will be hired by the foundation. That should leave me more time to push some projects we want to put in place, like the travel support program, Open Badges, moving to another translation tool, etc.
Looking at the next decade, which are the top challenges for LibreOffice?
One of the most important challenges for open source projects is to make the community of volunteers and ecosystem participants thrive. Our developers are securing this by constantly enhancing tools and processes, but at the same time users and contributors are evolving, and we need to reinvent ourselves almost every day. This also means to re-evaluate processes and tools, looking at them in perspective.
Last, but not least, the product has to further evolve according to changes in the market, and we have to invest to make the online version more popular amongst users and increase the number of adoptions and contributions to the project.
580 bugs, 63 of which are enhancements, have been reported by 339 people.
Top 10 Reporters
585 bugs have been triaged by 87 people.
Top 10 Triagers
520 bugs have been set to RESOLVED.
Check the following sections for more information about bugs resolved as FIXED, WORKSFORME and DUPLICATE.
231 bugs have been fixed by 42 people.
Top 10 Fixers
List of critical bugs fixed
List of crashes fixed
List of old bugs ( more than 4 years old ) fixed
84 bugs have been retested by 37 people.
Top 10 testers
118 bugs have been duplicated by 39 people.
Top 10 testers
90 bugs have been verified by 11 people.
Top 10 Verifiers
701 bugs have been categorized with a metabug by 26 people.
Top 10 Categorizers
99 bugs have been set as regressions by 23 people.
Top 10
94 bugs have been bisected by 10 people.
Top 10 Bisecters
Check the current list of unconfirmed bugs here
Check the current list of open regressions here
Check the current list of open bibisectrequests here
Check the current list of highest priority bugs here
Check the current list of high priority bugs here
Thank you all for making Libreoffice rock!
Join us and help to keep LibreOffice super reliable!
Check the Get Involved page out now!…
Our provider is experiencing connectivity hiccups, affecting the reachability of our services (depending on the route taken).
by The Document Foundation's Infrastructure Status at May 05, 2019 06:45 PM
The work around user experience often requires to create a minimal working example. Either users report an issue or request enhancements, the comparison with the current situation is necessary. LibreOffice has a built-in feature to create dummy text (type dt and press F3) but this function inserts only unformatted text.…
On vecation I ordinary have the best ideas. So this time I made an single line contextual toolbar for writer.
It’s how the single line toolbar should look like. One toolbar which is fully contextual. As one toolbar didn’t have that much space, you have the menubar for all available commands in LibreOffice.
It’s the most compact LibreOffice UI done on my smal Laptop screen (1366 x 768 px). But Contextual single work not only on small screens it’s flexible and suites all screen sizes.
Context Standard, Table, Image, Shape
If you’d like to test contextual single download the daily master build, enable experimental features (Menubar -> Tools -> Configure -> Advanced -> Enable experimental features) and change in Writer Menubar -> View -> User Interface -> Contextual Single.
To test download the daily build
https://dev-builds.libreoffice.org/daily/master/Win-x86@39/current
I broke the linux builds but now daily build for linux is available to check out the context single layout
https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86@87-TDF/current
by Olivier Hallot (noreply@blogger.com) at April 29, 2019 01:07 PM
Recently we at Collabora Productivity have made some substantial improvements to XLSX interoperability related to pivot tables, fixing many issues existed in Calc.
Personally I have committed these patches:
These changes allow our customers, and the whole LibreOffice user community, to enjoy better interoperability when using XLSX format. They will be available in LibreOffice version 6.3 later this summer; and they are immediately available for our customers in this week’s Collabora Office 6.0 update 28.
Thanks to our valuable customers who make these improvements possible funding the work!
LibreOffice do organize the bugs into [META] bugs, which is great cause when you link the bug to different [META] bugs you can organize bugfixing over different groups. I care about BUG 106228 which is the Icon meta bug and as you can see most of the icon bugs need developer work. Everything I could fix myself is nearly done.
There are two bigger tasks, but with great effort open
All main icon themes are available in svg, but the svg2png libreoffice renderer give bad quality, so we have to ship the png icons. If we could use the svg icons instead of the png, it mean less work for the designers and the posibility to have color scheme support for icons. 100% dark icon theme support and full color support. What a great improvement.
We have colibre, elementary, breeze, sifr, tango icon theme therefore the design group did the icons, some icons like bold, italic, strickout, underline, overline, … have letters which work fine for english users but had to be drawen for other languages. But to know which letter should be used we need the translation team so translation team please submit an bug report for each language and add at depends on 124956, than we will do the icon work.
Colibre, elementary, sifr, breeze will be in an good shape for the 6.3 release, but to fix the last bugs, we need developers, translation team, documentation team, … everybody in one team.
The LibreOffice guidelines say that you should show icons on the most important items https://wiki.documentfoundation.org/Design/MenuBar
Now the menubar show only the most important items so the user didn’t flash with icons, the user get an better overview of the menubars.
happy hacking.
by Popa Adrian Marius (noreply@blogger.com) at April 18, 2019 08:24 AM
I already wrote about the btLr text direction in the context of Writer table cells as a result of a Collabora hack week. This is meant to be an update to present what happened in the past 2 months. Here is a video showing the results:
I fixed the following problems since the last blog post on this topic:
All this is available in LibreOffice master (towards 6.3), so you can try it out right now, if interested.
Every powerfull text editor like, kate, sublime, notepad++, VS Code, … has it the menubar. Now even better in LibreOffice.
Items with subgroups were arranged at the end of groups , so it’s faster to read the menubar and the groups are between 3-4 items. Tiny changes with big effort.
If you like my work, become a 
All items in the menubar have now an icon. Some items are missing tdf#124200 but in general all commands will show an icon in the menubar.
For 6.3 all supported icon themes will have the new icons. Now you can check them out in Sifr (which is complete new for 6.3 release).
If you like my work, become a
680 bugs, 69 of which are enhancements, have been reported by 417 people.
Top 10 Reporters
687 bugs have been triaged by 93 people.
Top 10 Triagers
201 bugs have been fixed by 51 people.
Top 10 Fixers
List of critical bugs fixed
List of crashes fixed
List of old bugs ( more than 4 years old ) fixed
90 bugs have been verified by 10 people.
Top 10 Verifiers
131 bugs have been retested by 38 people.
Top 10 testers
762 bugs have been categorized with a metabug by 31 people.
Top 10 Categorizers
101 bugs have been set as regressions by 23 people.
Top 10
60 bugs have been bisected by 9 people.
Top 10 Bisecters
Check the current list of unconfirmed bugs here
Check the current list of open regressions here
Check the current list of open bibisectrequests here
Check the current list of highest priority bugs here
Check the current list of high priority bugs here
Thank you all for making Libreoffice rock!
Join us and help to keep LibreOffice super reliable!
Check the Get Involved page out now!…
Recently I implemented FOURIER() formula for LibreOffice Calc that computes Discrete Fourier Transform [DFT] of a real/complex data sequence. Computation is done using a couple of Fast Fourier Transform algorithms (all implemented from scratch). I’d like to thank Collabora Productivity for a fully funded hack week and lots of encouragement that enabled me to work on this feature.
The syntax of the formula is :
FOURIER(Array, GroupedByColumns, Inverse, Polar, MinimumMagnitude)
First and second arguments : First argument is the data array range. There are some restrictions on its shape. If the array is grouped by columns(rows), you need to indicate that by setting the second argument GroupedByColumns = TRUE(FALSE). In case of grouped by columns(rows) the “Array” can contain 1 or 2 columns(rows), where the first column(row) should contain the real part of the input sequence and second column(row) if present should contain the imaginary part of the input sequence. If there is only 1 column(row), the input sequence is assumed to be purely real. There is no restriction on the length of the input sequence. For example the length need not be an exact power of 2 like MS Excel’s Fourier analysis tool requires. The DFT computed by FOURIER formula is exact for the given length of the input sequence meaning it does not pad zeroes to the end of the input sequence to make the length an even power of 2.
The third argument “Inverse” is a boolean flag to indicate whether an inverse DFT needs to be computed. This argument is optional and the default value is FALSE.
The fourth argument “Polar” is a boolean flag to indicate whether the final output needs to be in polar coordinates. This argument is optional and the default value is FALSE.
The fifth argument “MinimumMagnitude” is a numeric argument and is used only if Polar=TRUE. All output components(frequency components if Inverse=FALSE) with magnitude less than MinimumMagnitude will be suppressed by a zero magnitude-phase entry. This is very useful when looking at the magnitude-phase spectrum of a signal (especially when its spectrum is sparse) because there is always some very tiny amount of rounding error when doing FFT algorithms and results in incorrect non-zero phase for some non-existent frequencies. By providing a suitable value to this parameter, these non-existent frequency components can be suppressed. The default value of this parameter is 0.0, so no suppression is done by default.
The result of this formula consists of two columns – first column contains the real parts (or the magnitudes if Polar=TRUE) and second column contains the imaginary parts (or the phases if Polar=TRUE).
Below is a screenshot of a sample usage of FOURIER() formula.
The data x[n] column was generated by the formula “=10*COS(2*PI()*COS(2*PI()*A2:A257/128))” (a typical frequency modulation example). Here a Phase-Magnitude spectrum is computed using FOURIER formula
=FOURIER(B2:B257,1,0,1, 1E-10)
Note that the Polar argument is set to 1, and MinimumMagnitude is set to 1E-10, to suppress the non-existent frequency components due to rounding errors. The plots here just visualize the data. The top plot shows the time-domain waveform and the next two plots represent the magnitude and phase spectra.
Fourier Analysis Tool
A Fourier analysis tool is also added to Statistics menu. All features of FOURIER formula are available graphically in this tool. Here is a screenshot of Fourier Analysis tool in action.
Implementation details of FOURIER formula
Basically two different Fast Fourier Transform (FFT) algorithms are implemented.
Both algorithms have asymptotic time complexity of O(N lgN), but Bluestein’s algorithm is much slower in practice. However many optimizations are in place to make the computation faster, especially when the input sequence is purely real.
Below are the patches that shows the evolution of the implementation of FOURIER formula over time.
Performance
Below are some perf measurements for various input cases. These numbers are only for the DFT computation part and does not include the time for writing data to the spreadsheet model. We don’t use multi-threading yet for FOURIER, so these are numbers for just one cpu-core.
Case#1 : Data length is a power of 2
| Real Input length | Time (ms) |
| 32768 | 2 |
| 65536 | 4 |
| 262144 | 21 |
| 1048576 | 185 |
| Complex Input length | Time (ms) |
| 32768 | 2 |
| 65536 | 5 |
| 262144 | 30 |
| 1048576 | 400 |
Case#2 : Data length is even but not a power of 2
| Real Input length | Time (ms) |
| 32766 | 8 |
| 65534 | 20 |
| 262142 | 105 |
| 1048574 | 1440 |
| Complex Input length | Time (ms) |
| 32766 | 15 |
| 65534 | 36 |
| 262142 | 313 |
| 1048574 | 3332 |
Case#3 : Data length is odd but not a power of 2
| Real Input length | Time (ms) |
| 32767 | 16 |
| 65535 | 39 |
| 262143 | 313 |
| 1048575 | 2729 |
| Complex Input length | Time (ms) |
| 32767 | 16 |
| 65535 | 38 |
| 262143 | 309 |
| 1048575 | 2703 |
After one of our hypervisors went down, one of the gluster filesystems that stores the VM disk images went into a bad state where it wouldn't heal files and thus some files got out of sync (split-brain) that was not fixed/prevented by gluster's self-heal-deamon.
We're manually fixing the split-brain/inconsistencies and bringing services back up, but before bringing back the critical services like bugzilla and askbot, we of course want to make sure the images are in a consistent state to avoid additional complications further down the road.
Update: bugzilla and askbot are up again. Unfortunately we had to restore bugzilla's from backup, so we "lost" some entries between time of last backup (March 25th 22:56 UTC) until beginning of outage (Mar 26 10:04 UTC) - the lost is in quotes, since the comments and assignments that were done in the meantime are not completely lost, but can be restored from the mail notifications/archive.
by The Document Foundation's Infrastructure Status at March 26, 2019 10:00 AM
I recently dived into the SmartArt support of LibreOffice, which is the component responsible for displaying complex diagrams from PPTX. I focus on the case when only the document model and the layout constraints are given, not a pre-rendered result.
In this post I would like to present the progress done earlier this year regarding the above mentioned diagram types — these are used in many documents.
The improvement (as always) come in small incremental steps:
Organization Chart is the most complex type I dealt with so far. I fixed
several issues (font color, vertical ordering, multiple paragraphs in a data
node, size of layout nodes, better support for hierBranch conditions, the
type of connector shapes). This allows giving readable result for diagrams
which are more complex than the simple 3-node one presented in the previous
post.
Cycle Matrix: there were missing child nodes here, the composite algorithm needed improved handling of position / size from constraints and the ordering / fill / line properties of actual content also needed fixing.
Picture Strip: the biggest problem here was the lack of pictures, but also the existing snake algorithm needed improvements (size, positioning, spacing and margins of the child shapes were not great).
With all these fixed, we reach a much better state for the mentioned diagram types.
The SmartArt test documents from sd/qa/unit/data/pptx/ is what I used for testing this work.
Here is how the baseline, the current and the reference rendering of Organization Chart looks like:
smartart-org-chart.pptx, baseline
smartart-org-chart.pptx, current
smartart-org-chart.pptx, reference
And here is how the baseline, the current and the reference rendering of Cycle Matrix looks like:
smartart-cycle-matrix.pptx, baseline
smartart-cycle-matrix.pptx, current
smartart-cycle-matrix.pptx, reference
And finally here is how the baseline, the current and the reference rendering of Picture Strip looks like:
smartart-picture-strip.pptx, baseline
smartart-picture-strip.pptx, current
smartart-picture-strip.pptx, reference
This is not not perfect yet, but it’s clearly a large improvement, all text is now readable from the diagrams and pictures are no longer missing!
All this is available in master (towards LibreOffice 6.3), so you can grab a daily build and try it out right now. :-)
I recently dived into the SmartArt support of LibreOffice, which is the component responsible for displaying complex diagrams from PPTX. I focus on the case when only the document model and the layout constraints are given, not a pre-rendered result.
In this post I would like to present the progress done earlier this year regarding the above mentioned diagram types — these are used in many documents.
The improvement (as always) come in small incremental steps:
Organization Chart is the most complex type I dealt with so far. I fixed
several issues (font color, vertical ordering, multiple paragraphs in a data
node, size of layout nodes, better support for hierBranch conditions, the
type of connector shapes). This allows giving readable result for diagrams
which are more complex than the simple 3-node one presented in the previous
post.
Cycle Matrix: there were missing child nodes here, the composite algorithm needed improved handling of position / size from constraints and the ordering / fill / line properties of actual content also needed fixing.
Picture Strip: the biggest problem here was the lack of pictures, but also the existing snake algorithm needed improvements (size, positioning, spacing and margins of the child shapes were not great).
With all these fixed, we reach a much better state for the mentioned diagram types.
The SmartArt test documents from sd/qa/unit/data/pptx/ is what I used for testing this work.
Here is how the baseline, the current and the reference rendering of Organization Chart looks like:
smartart-org-chart.pptx, baseline
smartart-org-chart.pptx, current
smartart-org-chart.pptx, reference
And here is how the baseline, the current and the reference rendering of Cycle Matrix looks like:
smartart-cycle-matrix.pptx, baseline
smartart-cycle-matrix.pptx, current
smartart-cycle-matrix.pptx, reference
And finally here is how the baseline, the current and the reference rendering of Picture Strip looks like:
smartart-picture-strip.pptx, baseline
smartart-picture-strip.pptx, current
smartart-picture-strip.pptx, reference
This is not not perfect yet, but it’s clearly a large improvement, all text is now readable from the diagrams and pictures are no longer missing!
All this is available in master (towards LibreOffice 6.3), so you can grab a daily build and try it out right now. :-)
| Prefix | Meaning |
|---|---|
| b | Boolean |
| p | Pointer |
| r | Reference |
| n | Integer/Numeric Type |
| c | Character |
| a | Anything else |
666 bugs have been reported by 379 people.
Top 10 Reporters
634 bugs have been triaged by 78 people.
Top 10 Triagers
158 bugs have been fixed by 49 people.
Top 10 Fixers
List of critical bugs fixed
List of crashes fixed
List of old bugs ( more than 4 years old ) fixed
51 bugs have been verified by 14 people.
Top 10 Verifiers
831 bugs have been categorized with a metabug by 26 people.
Top 10 Categorizers
86 bugs have been set as regressions by 22 people.
Top 10
54 bugs have been bisected by 11 people.
Top 10 Bisecters
Check the current list of unconfirmed bugs here
Check the current list of open regressions here
Check the current list of open bibisectrequests here
Check the current list of highest priority bugs here
Check the current list of high priority bugs here
Thank you all for making Libreoffice rock!
Join us and help to keep LibreOffice super reliable!
Check the Get Involved page out now!…
Currently there are some routing/connectivity issues with our hosting provider. Nothing we (TDF) can do, see our provider's ticket for latest info.
by The Document Foundation's Infrastructure Status at March 09, 2019 02:45 PM
Service disruption (slowdown, timeout) in The Document Foundation's main infrastructure. Reason: hypervisor crash. Update 12:30 UTC: Production VMs should no longer be affected. Resolved - 12:45:00 UTC
by The Document Foundation's Infrastructure Status at March 06, 2019 11:45 AM
by Unknown (noreply@blogger.com) at February 28, 2019 11:21 AM
If you work with tables in Word, it’s very easy to create this writing direction: the context menu in a table cell has a menu item to set the direction of the text, where you can rotate the text by 90 degrees counter-clockwise or clockwise. The counter-clockwise btLr direction is the problematic one. Support for tbRl was fine already, since that is needed typically for Chinese/Japanese scripts as well.
Here is how the baseline, the current and the reference rendering of btLr text looks like:
You can see how the second paragraph in the cell was missing from the rendered result and now we basically pixel-by-pixel match the reference.
If you would like to know a bit more about how this works, continue reading… :-)
The document model and UNO API were reasonably straightforward to implement, but the layout was much more challenging. Writer already supported 3 writing directions:
typically used for Latin (left to right, top to bottom)
Chinese/Japanese (top to bottom, right to left)
Mongolian (top to bottom, left to right) text.
This new one is also a vertical direction, also left to right, but bottom to top. The initial layout contained code to read the new enumerator from doc model, extend the SwFrame class to handle this new bottom to top mode, some handling of switching between horizontal/vertical mode and at the end mapping from Writer layout’s direction to VCL’s "900" font orientation. There are more things to handle in layout, but this was good enough to look at other areas as well.
The ODF filter required updating, which was a bit challenging as it was necessary to write different attribute names depending on which enumerator is used from an emumeration, and we don’t have good support for this. Once the filter code was in place, I could write some layout-level tests as well.
Since we have .ui files for UI descriptions, adding UI support was really easy.
Time came to step away from coding for a moment and write up paperwork to propose this feature to be part of the next ODF version (thanks to Andras for the help there!).
Finally I went back to layout, and improved things a bit more: after fixing baseline offsets, the positioning of the text was exactly matching what Word does. How do I know? I used this little script:
gs -dNOPROMPT -dBATCH -sDEVICE=jpeg -r75 -dNOPAUSE -sOutputFile=btlr.jpg btlr.pdf
gs -dNOPROMPT -dBATCH -sDEVICE=jpeg -r75 -dNOPAUSE -sOutputFile=btlr-word.jpg btlr-word.pdf
composite -compose difference btlr-word.jpg btlr.jpg out.jpgWhich allows seeing the differences between our and Word’s PDF output. Additional work was needed to handle multiple paragraphs in a table cell. At this stage I was happy enough with the rendering result, so finally pulled the trigger and replaced the old DOCX filter hack (using character-level rotation) with simple DOCX filter mapping from OOXML’s btLr direction to Writer’s btLr direction — i.e. what was already done for the tbRl case.
The feature works good enough already so that this new core feature can be used by the DOCX filter by default, but there are still a few rough edges:
the shell code (cursor travelling, selection painting, etc) only has partial support for this new direction
RTF and DOC filters are not yet updated
the ODF proposal has a list of contexts other than table cells where the new writing direction could be used, which lack UI/filter support/etc at the moment.
All this is available in master (towards LibreOffice 6.3), so you can grab a daily build and try it out right now. :-)
Recently my LibreOffice work is mostly focused on the Online. It's nice to see how it is growing with new features and has better UI. But when I was working on improving toolbars (eg. folding menubar or reorganization of items) I noticed one annoying thing from the developer perspective. After every small change, I had to restart the server to provide updated content for the browser. It takes few seconds for switching windows, killing old server then running new one which requires some tests to be passed.
Last week during the Hack Week funded by Collabora Productivity I was able to work on my own projects. It was a good opportunity for me to try to improve the process mentioned above.
I've heard previously about browsersync so I decided to try it out. It is a tool which can automatically reload used .css and .js files in all browser sessions after change detection. To make it work browsersync can start proxy server watching files on the original server and sending events to the browser clients if needed.
What is the advantage? Developer tools in the browser are not good enough?
Disadvantages
To integrate browsersync I needed to do some build system changes. First, all static files are served from 'loleaflet/dist' directory. These files are not the original sources but copies. I modified the Makefiles to create symlinks instead if the browsersync is activated. Thanks to that we can modify sources tracked by git and proxy can detect changes.
To try it out on your own:
make cleannpm install -g browser-sync--enable-browsersync argumentLOOL_SERVE_FROM_FS=1 make runmake sync-[writer|calc|impress]In the video below you can see how it works:
Next step will be to allow browsersync usage with cloud storage integrations like richdocuments, I noticed also some issues with access from other devices (app is still using original server for some resources).
by Unknown (noreply@blogger.com) at February 21, 2019 12:59 PM
by Popa Adrian Marius (noreply@blogger.com) at February 21, 2019 12:07 PM
| Imprint Privacy Policy | |
|
The Document Foundation is not responsible for the content on planet.documentfoundation.org. However - if you have any concerns about content please contact Simon Phipps for moderation. Copyright information: Unless otherwise specified in the author's blog, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). |
 |