Caolán McNamara
LibreOffice QA Blog
Marius Popa Adrian
Miklos Vajna
Official TDF Blog
Tomaž Vajngerl
Last updated:
June 12, 2021 06:01 PM
All times are UTC.
Powered by:
Imprint
Privacy Policy
We originally posted this tender in April, but we are now extending the application deadline.
The deadline for questions stays as in the original tender: June 15, 2021
The deadline for applications has been extended to: June 24, 2021
For all details on the tender, please refer to the original blogpost.
Berlin, June 10, 2021 – LibreOffice 7.1.4 Community, the fourth minor release of the LibreOffice 7.1 family, targeted at technology enthusiasts and power users, is available for download from https://www.libreoffice.org/download/. LibreOffice 7.1.4 includes around 80 bug fixes, with 20% focused on Microsoft Office file compatibility (DOCX, XLSX and PPTX, and legacy DOCs).
For enterprise-class deployments, TDF strongly recommends the LibreOffice Enterprise family of applications from ecosystem partners, with long-term support options, professional assistance, custom features and Service Level Agreements: https://www.libreoffice.org/download/libreoffice-in-business/.
LibreOffice Community and the LibreOffice Enterprise family of products are based on the LibreOffice Technology platform, the result of years of development efforts with the objective of providing a state of the art office suite not only for the desktop but also for mobile and the cloud.
Products based on LibreOffice Technology are available for major desktop operating systems (Windows, macOS, Linux and Chrome OS), mobile platforms (Android and iOS) and the cloud. They may have a different name, according to each company brand, but they share the same LibreOffice unique advantages, robustness and flexibility.
Migrations to LibreOffice
The Document Foundation has developed a Migration Protocol to support enterprises moving from proprietary office suites to LibreOffice, which is based on the deployment of a LTS version from the LibreOffice Enterprise family, plus migration consultancy and training sourced from certified professionals who offer CIOs and IT managers value-added solutions in line with proprietary offerings. Reference: https://www.libreoffice.org/get-help/professional-support/.
Availability of LibreOffice 7.1.4 Community
LibreOffice 7.1.4 Community represents the bleeding edge in term of features for open source office suites. For users whose main objective is personal productivity and therefore prefer a release that has undergone more testing and bug fixing over the new features, The Document Foundation provides LibreOffice 7.0.6.
LibreOffice 7.1.4 change log pages are available on TDF’s wiki: https://wiki.documentfoundation.org/Releases/7.1.4/RC1 (changed in RC1) and https://wiki.documentfoundation.org/Releases/7.1.4/RC2 (changed in RC2).
LibreOffice Technology based products for Android and iOS are listed here: https://www.libreoffice.org/download/android-and-ios/, while for App Stores and ChromeOS are listed here: https://www.libreoffice.org/download/libreoffice-from-microsoft-and-mac-app-stores/.
LibreOffice individual users are assisted by a global community of volunteers: https://www.libreoffice.org/get-help/community-support/. On the website and the wiki there are guides, manuals, tutorials and HowTos. Donations help us to make all of these resources available.
LibreOffice users are invited to join the community at https://ask.libreoffice.org, where they can get and provide user-to-user support. People willing to contribute their time and professional skills to the project can visit the dedicated website at https://whatcanidoforlibreoffice.org.
LibreOffice users, free software advocates and community members can provide financial support to The Document Foundation with a donation via PayPal, credit card or other tools at https://www.libreoffice.org/donate.
LibreOffice 7.1.4 is built with document conversion libraries from the Document Liberation Project: https://www.documentliberation.org.
Line heights in Writer are typically defined in points on the UI (e.g. 12pt), though they are measured in twips internally (1 point is 20 twips). This height was stored in a 16bit unsigned integer, so the maximum allowed height was 65536 twips, around 116 cm.
Now we track line heights with 32 bits ints, so this limitation is practically removed.
Once you insert an image to a Writer document, you can customize its anchor type. The as-char anchor type is handy if you don’t want text to flow around the image. This has the side effect that a large image significantly increases the nominal height of a line. The problematic document had an image height of 118.9 cm (46.81 inch), so the unsigned integer used to represent its height wrapped around, leading to an incorrect layout.
Now it looks like the way you would expect it:
If you would like to know a bit more about how this works, continue reading… :-)
As usual, the end goal was reached via a set of incremental commits:
The very first integer truncation was found using gdb, manually. At that point it was clear that
some tool to catch the problematic places would accelerate development. First
sw: replace most static_cast<sal_uInt16>()
calls with o3tl::narrowing() prepared Writer code so that sanitizers can flag the interesting code
locations when using -fsanitize=implicit-unsigned-integer-truncation
-fsanitize=implicit-signed-integer-truncation. This is important, as conversion with
static_cast<> counts as an explicit integer conversion, and sanitizers can’t flag such
conversions.
Then sw: allow the height of a line to be larger than 65536 twips took care of the height part.
Finally sw: allow the width of a line portion to be larger than 65536 twips fixed the width part.
Collabora intends to continue supporting and contributing to LibreOffice, the code is merged so we expect all of this work will be available in TDF’s next release (7.2).
The Document Foundation (TDF) is the charitable entity behind the world’s leading free/libre open source (FLOSS) office suite LibreOffice.
We are looking for an individual or company to implement master document fixes.
The documentation team regularly publishes guides and books. The underlying workflow requires to fix bugs and issues with the master document feature of Writer.
The scope of this tender is to fix at least the following issues:
The work has to be developed on LibreOffice master, so that it will be released in the next major version.
The bugs must be fixed and verified.
All technology standards of relevance, as well as their targeted versions for this tender should be declared or defined in the offer’s description of implementation.
A key item of the deliverables for this tender and therefore also a decision criteria – besides qualification, references, price, and completeness of fullfilment – is extensive is documentation about the approach chosen to implement or fix the above items. We expect bidders to provide documentation on both the code and the non-code parts of this tender, e.g. methodology, structure and technical aspects. The Document Foundation will publish this under a free and open source license and make it available to the general public. Publications will be in the Help system and in the Guides books.
If the bug fix incurs in a change in the user interface or user procedure, it should also contain the necessary instructions to activate the procedure.
Required skills
Other skills
We use free, libre and open source (FLOSS) software for development wherever possible, and the resulting work on the program code must be licensed under the Mozilla Public License v2.0.
TDF welcomes applications from all suitably qualified persons regardless of their race, sex, disability, religion/belief, sexual orientation or age.
Bidders will get a preference for including a partner or independent developer who has not been involved in a successful tender before. For such developers, who have not yet been part of a successful tender bid, we aim on a best-effort basis, but without any guarantees whatsoever, to provide some mentoring in understanding the code base and the process in contributing to the code. We expect that time and efforts on the bidder’s side for this should not be part of the paid work for this tender. Please mention such need of LibreOffice development mentoring in your offer.
As always, TDF will give some preference to individuals who have previously shown a commitment to TDF, including but not limited to certified developers and/or members of TDF. Not being a member, or never having contributed before, does not exclude any applicants from consideration.
The task offered is a project-based one-off, with no immediate plans to a mid- or long-term contractual relationship. It is offered on a freelance, project basis. Individuals and companies applying can be located anywhere in the world.
When budgeting, we anticipated that this project (all items combined) to take in the region of 5 days of work. Should bidders’ assessment result in a significantly different number, please reach out to us before sending your bid, so we can clarify upfront.
TDF is looking forward to receiving your applications for the aforementioned tasks, your offer in form of a fixed-time, fixed-budget approach, and the duration period for the implementation in calendar weeks after the final awarding of the tender, via e-mail to a committee at tender20210602@documentfoundation.org no later than July 5, 2021.
Applicants who have not received feedback by August 2, 2021 should consider that their application, after careful review, was not accepted.
All bidders are invited to ask their questions on this tender until June 23, 2021. Questions and answers will be made public in a collected and anonymized form.
by Popa Adrian Marius (noreply@blogger.com) at June 07, 2021 06:50 PM
by Popa Adrian Marius (noreply@blogger.com) at June 07, 2021 05:42 PM
Kudos to Ilmari Lauhakangas for helping to elaborate this list.
567 bugs, 57 of which are enhancements, have been reported by 323 people.
Top 10 Reporters
584 bugs have been triaged by 85 people.
Top 10 Triagers
620 bugs have been set to RESOLVED.
Check the following sections for more information about bugs resolved as FIXED, WORKSFORME and DUPLICATE.
198 bugs have been fixed by 52 people.
Top 10 Fixers
List of critical bugs fixed
List of high severity bugs fixed
List of crashes fixed
List of performance issues fixed
(This is part of The Document Foundation’s Annual Report for 2020 – the full version is here.)
In January 2020, just before release of LibreOffice 6.4, the Documentation Team was proud to announce the Math Guide 6.4, an update of the previous version (4.0), updated to cover all of the innovations included in the latest release of the software. The guide was updated by Roman Kuznetsov and revised by Dave Barton from the documentation community. This was followed by the Calc Guide 6.2, a long-awaited update of the old Calc Guide 4.4.
In May, the guide to Base for LibreOffice 6.2 was released, covering, LibreOffice’s database component. It was updated by Pulkit Krishna, Dan Lewis, Jean Hollis Weber, Alain Romedenne, Jean-Pierre Ledure and Randolph Gamo. Another update in May was the Getting Started Guide 6.4 – the introductory guide for the latest LibreOffice 6.4, aimed to the general public interested to quickly get familiar with the software. It’s available as a PDF for offline reading, and ODT (OpenDocument Text) for editors and translators.
In summer, the Documentation Team announced the availability of the LibreOffice Draw Guide 6.4, the complete handbook for the drawing tool of LibreOffice. The guide was updated from the existing release (4.3) and include all the improvements developed since early 2014, when the last version of the guide was published.
Then there was the LibreOffice Calc Guide 6.4, the complete handbook for the spreadsheet tool. It was also updated from the existing release (6.2) and included all of the improvements developed in Calc since then.
In October, the Math Guide 7.0 was published – being the first guide based on LibreOffice 7.0. The effort was mostly carried by Rafael Lima and reviewed by Jean H. Weber. The new guide covers were designed by Rizal Muttaqin and Drew Jensen. The final publication was carried by Olivier Hallot. This was followed by the Calc Guide 7.0, a team effort of Steve Fanning, Gordon Bates, Kees Kriek, Annie Nguyen, Samantha Hamilton, Olivier Hallot and Jean Hollis Weber, coordinated by Felipe Viggiano.
Many guides were also translated in to various languages, thanks to our worldwide communities. For more information on their work, and the specific guides that they translated, see the “Native Language “Projects” section of this Annual Report.
For the second year in a row, The Document Foundation was accepted as an organization in the Google Season of Docs, a programme whose goals are to give technical writers an opportunity to participate in contributing to open source projects, and to give open source projects an opportunity to engage the technical writing community.
In 2020, TDF’s documentation community offered a wide range of projects for technical writers, and extended the reach by providing projects for e-learning, mathematical documentation and code-oriented documentation.
TDF received several applications, containing important information including the technical writer’s resumés, proposals for project schedule and suggested deliverables. After a careful evaluation by the project mentors, TDF accepted the application of Ronnie Gandhi, a computer science undergraduate student enrolled at IIT Roorkee, India.
Steve Fanning, who had already worked as coordinator of the Calc Guide, served as mentor with Olivier Hallot as second mentor. Ilmari Lauhakangas and Olivier managed the administrative aspects of the project on behalf of The Document Foundation.
Ronnie worked on improving the descriptions for Calc’s functions, adding statements describing each function’s compliance with the Open Document Format for Office Applications (OpenDocument) Version 1.2 specification. Each function was also supplemented by extra use cases, illustrations and external references (where applicable).
Access the Extensive Calc Functions Description on The Document Foundation’s wiki. Thanks to Ronnie for all his work, and the mentors for assisting him on his journey.
At the beginning of May, we started a new Month of LibreOffice, celebrating community contributions all across the project. We do these every six months – so how many people got sticker packs this time? Check it out…
Fantastic! This makes it the most successful Month of LibreOffice ever, slightly overtaking the results from May 2020.
Great work, everyone! Hundreds of people, all across the globe, have helped out in our projects and communities. We’re hugely thankful for your contributions – and, of course, everyone who’s listed on the wiki page can get a sticker pack, with these stickers and more:
If you see your name (or username) on this page, get in touch! Email mike.saunders@documentfoundation.org with your name (or username) from the wiki page so that we can check, along with your postal address, and we’ll send you a bunch of stickers for your PC, laptop and other kit.
(Note: your address will only be used to post the stickers, and will be deleted immediately afterwards.) If you contributed to the project in May but you’re not on the wiki page, please let us know what you did, so that we can add you!
And we have an extra bonus: 10 contributors have also been selected at random to get an extra piece of merchandise – a LibreOffice hoodie, T-shirt, rucksack or snazzy glass mug. Here are the winners – we’ll get in touch personally with the details:
More progress, Entries, SpinButtons, PushButtons, CheckBoxes/RadioButtons, TreeViews and basic Notebooks and DrawingAreas working in the GTK4 port
The LibreOffice Quality Assurance ( QA ) Team is happy to announce LibreOffice 7.2 Alpha1 is ready for testing!
LibreOffice 7.2 will be released as final in mid August, 2021 ( Check the Release Plan ) being LibreOffice 7.2 Alpha1 the first pre-release since the development of version 7.2 started at the end of November, 2020. Since then, 5971 commits have been submitted to the code repository and more than 1040 bugs were set to FIXED in Bugzilla. Check the release notes to find the new features included in this version of LibreOffice.
LibreOffice 7.2 Alpha1 can be downloaded from here for Linux, MacOS and Windows, and it can be installed alongside the standard version.
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.
LibreOffice is a volunteer-driven community project, so please help us to test – we appreciate it!
Happy testing!!
…
Early days yet, but here's some screenshots of an experimental port of LibreOffice to GTK4 I've commited upstream during the week. It starts without crashing, renders, accepts user keystrokes and mouse events, basic Input Method support also works.
Standard GTK file dialog functionality works.
Standard GTK message dialogs work.
Context menus, now using Popover Menus, work.
Toplevel Menubar and menus, via gtk_popover_menu_bar_new_from_model, are also functional.
Working sample native GTK dialog. A work in progress, my current thinking is with GtkButtonBox gone that moving the old action area contents to the dialogs GtkHeaderBar seems the easiest route.
 |
| Figure 1: Command Popup window |
by Tomaž Vajngerl (noreply@blogger.com) at May 13, 2021 02:14 PM
Kudos to Ilmari Lauhakangas for helping to elaborate this list.
577 bugs, 71 of which are enhancements, have been reported by 362 people.
Top 10 Reporters
609 bugs have been triaged by 100 people.
Top 10 Triagers
617 bugs have been set to RESOLVED.
Check the following sections for more information about bugs resolved as FIXED, WORKSFORME and DUPLICATE.
207 bugs have been fixed by 47 people.
Top 10 Fixers
List of critical bugs fixed
List of high severity bugs fixed
List of crashes fixed
List of performance issues fixed
The bibliography feature in Writer allows authors of e.g. scientific papers to track sources: first you can insert bibliography entry fields, then at the end you can generate a bibliography table automatically.
Writer recently gained two improvements in this area, and now there is one more: the ability to refer to a specific page of a (potentially long) source.
First, thanks TUBITAK ULAKBIM who made this work by Collabora possible.
The same feature in normal HTML linking / citation is well-known: you can place anchors in your document and then links can refer to not only to your page, but also can set the fragment part of the URL to jump to a specific section directly. E.g. this link will jump to the "Motivation" section of the above referred previous post.
Wouldn’t it be nice if you could also jump to a specific page of a scientific PDF?
You can add such references by choosing the Insert → Table of Contents and Index → Bibliography Entry menu item. Set Bibliography Source to Document Content and press the New button. The appearing dialog now has widgets to set a specific page number:
This is then stored in the URL by setting its fragment to page=..., and typically PDF readers
understand this syntax, so when you click on the URL, the PDF will open exactly on the cited page.
This also works the other way around: URLs with such syntax are presented to the user with the dedicated widget to see, edit or delete the page number of the URL.
Finally, if you refer to different pages of the same source, the bibliography text generator detects this and lists the source in the bibliography only once.
If you would like to know a bit more about how this works, continue reading… :-)
As usual, the high-level problem was addressed by a series of incremental development steps:
sw bibliography, refer to a page: strip URLs in the bibliography table improved the bibliography table generator to not show page fragments
sw bibliography, refer to a page: de-duplicate bibliography table URLs merged the idendical sources to a single entry in the bibliography
sw bibliography, refer to a page: make the biblio field clickable allows opening the URL-with-page by clicking on the bibliography entry field
sw bibliography, refer to a page: add open hyperlink context menu implemented the context menu, in case you prefer to avoid ctrl-click for hyperlink opening
sw bibliography, refer to a page: add PDF export links improved the PDF export to have clickable bibliography entry fields
sw bibliography, refer to a page: fix biblio field relative URLs added support for relative URLs, in case the edited document and referred PDFs are in the same directory, next to each other
sw bibliography, refer to a page: also de-duplicate relative URLs made the relative URL and bibliography table row merging work together
sw bibliography, refer to a page: edit the page number of individual entries allows editing just a single bibliography entry field for page number purposes, since in other cases it makes sense to update all fields of the same source (e.g. correcting a spelling mistake in an author name)
sw bibliography, refer to a page: add dedicate widget to show the page number, sw bibliography, refer to a page: save edited page number and sw bibliography, refer to a page: add insert/delete UI add support for creating, showing, editing and deleting page numbers of such URLs on the user interface
Collabora intends to continue supporting and contributing to LibreOffice, the code is merged so we expect all of this work will be available in TDF’s next release (7.2).
In other words, how much faster will a compiler be after it's been built with various optimizations?
Given the recent Clang12 release, I've decided to update my local build of Clang11 that I've been using for building LibreOffice. I switched to using my own Clang build instead of openSUSE packages somewhen in the past because it was faster. I've meanwhile forgot how much faster :), and openSUSE packages now build with LTO, so I've built Clang12 in several different ways to test the effect and this is it:
The file compiled is LO Calc's document.cxx, a fairly large source file, in a debug LO build. The compilation of the file is always the same, the only thing that differs is the compiler used and whether LO's PCH support is enabled. And the items are:
Or, if you want this as numbers, then with Base being 100%, CPU is 85%, LTO is 78%, LTO+PGO is 59%, Base PCH is 37% and LTO+PGO PCH is 25%. Not bad.
Mind you, this is just for one randomly selected file. YMMV. For the build from the video from the last time, the original time of 4m39s with Clang11 LTO PCH goes down to 3m31s for Clang12 LTO+PGO PCH, which is 76%, which is consistent with the LTO->LTO+PGO change above.
Both Word and Writer allow specifying borders for any kind of table cells. When the user creates a vertically merged cell, there is a covering cell and there is one or more covered table cells.
The Writer approach is to render the cell borders according to the properties of the covering cell. This has the benefit that each edge of the table cell has a single border style (e.g. dashed or hairline).
The Word approach is to render the cell borders as if there would be no vertical merge, according to the properties of the covered cell. This has the benefit that merging the content of cells vertically doesn’t change the border rendering, but it also requires more complex code for painting.
Writer can now detect that your tables originate from Word formats and render table borders the Word way in that case.
Here is how the new rendering result look like:
And here is how it used to look like:
And finally the reference rendering is:
You can see that the B4 and B5 cells are covered, they had some unwanted border on their left side and this is now gone.
If you would like to know a bit more about how this works, continue reading… :-)
First, some building blocks were introduced: SwCellFrame::GetCoveredCellInRow() can look up a
covered cell in a certain row, provided that this cell covers it
Building on top of this, SwCellFrame::GetCoveredCells() can provide a list of cell frames which
are covered by the current cell, due to vertical merge. This is needed, because previously the
layout didn’t have to consider properties of covered cells, so while the document model had this
information, it was not visible to the layout in a convenient way
Using the above functionality, SwTabFramePainter::Insert() can suppress painting of certain
border lines in Word compatibility mode
Finally, the code change can be covered with a test by recording the rendering and asserting the vertical positions of border points: we can check that all the positions belong to the 1st, 2nd or 3rd rows, and not to a row below them
Collabora intends to continue supporting and contributing to LibreOffice, the code is merged so we expect all of this work will be available in TDF’s next release (7.2).
In 1988 as a scrawny eleven-year old arrival alone at boarding school, perhaps the only Quaker in a thousand strong body; I wore a white poppy to the large Remembrance Day commemorations. I recall the interest and forceful objections of my peers and elders - some with armed service connections, and my impassioned pleas for a personal pacifism. No doubt there were some who were intellectual defenders of the doctrine of Just War: (love's response to a neighbour threatened), as I myself became later in life - but I suspect that the fun of picking on those who are noticeably different was the dominant motivation. I imagine a majority of those in the Free Software community have suffered similar or more traumatic experiences, associated with being noticeably and vocally different; of being outstanding in one area & yet weak in others: perhaps socially and/or athletically. Hopefully that lets us empathise with others who are oppressed. That's why in this debate I think the purest motives on both sides here are closest to this: What is love's response to a neighbour who is threatened? and then what is proportional?
Recently RMS returned to the FSF board with to my mind an indefensible lack of grace & engagement with his critics. This seems to unfortunately intersect with the absence of good, representative governance structures for eg. GPL users to affect license direction. People started on-line petitions in liu of voting to either remove the FSF board or to unconditionally support RMS. Spoiler alert - there is something to annoy everyone here. I don't believe either of these stated positions is helpful and one of them is actively dangerous. I expect RMS to demonstrate hard-core leadership by preparing for his inevitable political or physical death, and building good governance structures that can live on and continue his work. It is not a time to do nothing. KDE's, statement seemed constructive, Debian had a middle ground option, and even RedHat's position was not so extreme. I sincerely hope that the FSF can be improved and continue to reflect RMS' vision of Software Freedom.
The open letter to remove the FSF board contains much that is deeply problematic, yet there are some sensible pieces, take this one:
While these ideas have been popularized in some form by Richard M. Stallman, he does not speak for us. We do not condone his actions and opinions. We do not acknowledge his leadership or the leadership of the Free Software Foundation as it stands today.
Notice the credit, and yet creating distance, notice the sensible tone, and the moderate approach. I would like to think that the several thousand people signing up to this, many of whom I like, some of whom I've really enjoyed working with are primarily saying only what this paragraph says. If so - good, I can understand that. Unfortunately alongside this reasonableness are some very profound problems that needlessly makes this one of the most divisive initiatives I've seen in free-software:
The rational here seems really damaging:
"He has shown himself to be misogynist, ableist, and transphobic, among other serious accusations of impropriety [impiety?]. These sorts of beliefs have no place in the free software, digital rights, and tech communities. ... There has been enough tolerance of RMS’s repugnant ideas ... we will not continue suffering his behaviour, ... or otherwise holding him and his hurtful and dangerous ideology as acceptable. ... We ask for contributors to free software projects to take a stand against bigotry and hate within their projects."
This focus on beliefs is unconscionable. Beliefs struggle to exist outside people's heads so I read this as: People who we can plausibly accuse of having misogynistic, ableist or transphobic beliefs have no place in the free software community. This might sound plural and welcoming, and I understand the desire to stick up for those who are marginalized, but it has a number of acute problems.
Which are the views that must be held (or not held) to have a place in free software? Unfortunately the new orthodoxy while having sixteen promoters is unbounded - we are not given a comprehensive creed. We do have some very precise examples on what is not acceptable though. Lets take trans-phobia. Apparently RMS while not on the autistic spectrum, does have a phobia. However - exactly what that phobia is is rather less than clear. Many (including I suspect RMS) are convinced that he is not transphobic. There seems to be a somewhat complex difference in the doctrine of how best to de-gender pronouns which causes the problem.
Interestingly the ableist issue when I skimmed the snippets seems to be rooted in a specific view on the ethics of abortion. As a young woman finds herself unexpectedly alone at a crossroads of life-changing consequence it is hard not to have deep compassion for her! Indeed, my wife has spent some years giving space and a listening ear, to help women think through their choices at this crisis point. Views vary widely here, but it seems that even among abortion activists the (perhaps comforting) view that there is zero moral dimension: that the act is no more significant than clipping your fingernails is a rather extreme one. Nevertheless if you hold it I expect it makes it much harder to critique selective abortion - whether for sex, disability or (as technology advances) more eugenic Gattaca-style scenarios. I read RMS' deeply disturbing advice on selecting for ability (which is sadly common) as flowing from this understanding. Should an affirmation of the wonderful, unique, created in the image of God value of all persons at some point in this process be mandatory for inclusion in our community? A tough one.
Apparently the signatories of this document also think that having mysogynistic beliefs is grounds for excommunication from the free software community. Who chose these three beliefs? where did they appear from? are there any more things we should not believe? Presumably traditional convictions around marriage are also grounds, cf. the Brendan Eich hysteria but; what else?
The paradox of intolerance is often aired to lazily avoid spending any thought justifying this sort of statement & action. One day I hope to have time to read The Open Society and its Enemies and its counterpoint. The vital need is to respect the dignity, protect the property, and cherish the lives of others - particularly those who have historically suffered. I can see how this is especially important to trans people, and I take no pleasure in seeing them offended. Having said that there are also many groups who have suffered historically in horrible ways. History is indeed littered with examples of well meaning intolerance going badly wrong. It is also clearly the case that some speech is unacceptable (but beliefs!?). The interesting question here is really where to draw the line. No doubt it feels good to stand up for a vulnerable marginalized community by excluding those with whom they disagree. I do wonder whether that is easier than trying to understand and accurately portray both sides - or "putting the work in to understand other human beings".
It seems to me there is a substantial convergence of views between RMS and this new orthodoxy - so it should be far easier to find those whose beliefs diverge significantly. Luckily very detailed descriptions exist of what very large groups of people believe around the world. Many have different ideas of how best to love those with whom they disagree. For example Male and Female he created them - towards a path of dialogue on the question of gender theory in education. (published 2019 under Pope Francis). That should be easy to caricature in order to exclude people from the Free Software community. I think it would also be easy to argue that a loyal Catholic faithfully upholding the Churches' teaching has beliefs that are more easy to caricature as mysogynist than RMS'. I really don't want to pick on Catholics (who just happen to be rather good at multi-lingual write-ups of their doctrines), so how about a random update from the Church of England. Of course - in each case adherents would reject such a caricature and these labels; no doubt they would also have powerful convictions on when life begins. But perhaps that's all a bit Euro-centric - so how about Wikipedia on Islam, or we can spend all day cycling through major belief systems each representing hundreds of millions of people, and collectively billions. Almost all of these will have some element that will conflict with or upset the opinions of someone else. Most of these belief systems are mutually contradictory and/or mutually offensive at some level to adherents of others. So there should be no shortage of beliefs for which we can excommunicate others.
I hear the common objection: "But I have a friend who is a <insert religion> and they don't believe anything (like that) - perhaps we can only exclude the ones that actually believe these things?". I'm sure you do have such a friend, and so do I. Clearly no world religion has a monolithic interpretation. The balance between revelation & personal experience, the hermeneutics and theology varies extraordinarily widely. That results in sets of people under the same apparent umbrella holding widely different beliefs; even if we can safely assume that you truly know what your friend believes; and this is before we get into more esoteric Spaghetti Monster style creeds.
All that aside - I see no way to argue for excluding RMS on the basis of his beliefs (ie. he is not progressive-orthodox enough) without also loosing a big chunk of the rest of the world as well. Please notice - nothing in the statement that so many signed says this is specific to leaders, or being a prominent person, each belief itself is grounds: "these sort of beliefs have no place in the free software community?". Why pick belief as a rationale?
An acquaintance of a friend spent many decades smuggling 'pornographic literature' into the Eastern Block - (very good for marriage enrichment). He also founded a non-profit Open Doors, here's a quote from the pre-amble to their watch list:
In the most populated countries on earth, [people] live in a surveillance state ... China has also developed widespread facial recognition software and established laws requiring facial scans to purchase a phone. When taken together, these two technological advances mean the government can track individuals like never before ... China is also rolling out a country-wide Social Credit System (SCS) by which authorities plan to reward "good" citizenship and punish "bad."
Another interesting problem with orthodoxy is the surprising belligerence and infighting that it can breed - often on minor issues. This is familiar from the innumerable schisms in small churches. A joke is told in the aftermath of a church dividing; of an old friend checking in with one of the new leaders: "Ah, these are terrible faithless times - we've split again over doctrine, and now it's just me and my brother. And to be honest - I'm not so sure about him!". I was interested to see the story of eg. Valerie Aurora: an extremely smart & dynamic feminist who is a leading expert on the latest diversity topics. Yet she was somehow ejected from Double Union the hacker/maker space she co-founded because of inadvertently infringing the code of conduct that she ~wrote. I fear living in a world where even outwardly conforming to the latest progressive orthodoxy would tax the wisdom of Solomon.
It is interesting to read about the beliefs of some of the people involved here; sadly I don't know Molly - but I've had the privilege of working with Matthew Garrett in his early days on GNOME - and a smarter, more charismatic, outspoken, iconoclastic(?), amusing person it's hard to find - quite apart from his amazing depth of contribution to Free Software. I was interested to try to quickly skim Molly & Matthew's beliefs based on what they write and see how they measure up.
Before doing that - let me re-assert that I take the freedoms of speech, conscience and expression extremely seriously as self-evidently vital for the functioning of an open society, though not absolute. While I want everybody to live in a physically safe space, I want to discuss views robustly in an atmosphere of respectful enquiry, with complete freedom and openness. It is not my intention to enlarge the sphere of (self) censorship.
There is however a kind of humour whose value (if any) is drawn from trampling the personal & sacred to elicit a response; is it nervous schadenfreude for those thus offended? (in this case those who love Christ more than friends or family). I don't see many cursing with ~obsolete god's names eg. Marduk so what can we learn from:
I'd prefer five words such as: challenging, fascinating, absorbing, collaborative, rewarding myself - but I'd hate to live in a world devoid of humour. Another example - I was interested by Molly's re-tweet on another hot potato (as always well worth reading the primary source court judgement rather than the dubious spin below):
To me it is curious that someone can champion excluding people over their heterodox beliefs, while simultaneously shouting things like the below; perhaps some irony overload here:
Apparently it is easy to end up championing the gentle treatment of a sexual minority while thinking it is funny to be gratuitously offensive to other minorities. Surely it can be offensive enough to respectfully state ones position. Still - in a world where there is a broad freedom of belief, conscience and speech, possibly some humour can cut through the gloom. A possibly tragic, possibly humorous but probably co-incidental aside here is that some chunk of this is based on an excessive focus on a small divergence in linguistic orthodoxy; when this was a hallmark of the GNU-slash-Linux campaigns of the past.
Perhaps you think it is deeply unfair to examine people's public twitter feeds - which occur outside the context of a project - to determine whether their beliefs are aligned with the standards they demand from others. Actually - I tend to agree. For good reason any sensible code of conduct excludes speech and behaviour outside its immediate project context. Not so this statement - its scope is everyone, everywhere and all of the time - even historic beliefs.
But possibly you think that it is ok to attack the privileged to defend the weak; that it is proportional to agitate to end someone's career in order to avoid the risk of a friendly minority member inadvertently working alongside someone who has some subset of beliefs that differ from theirs.
I was encouraged recently to watch this, and I excerpt the first part:
This idea of purity, never compromised, always politically woke & all that stuff - you should get over that quickly. The world is messy, there are ambiguities, people who do really good stuff have flaws.
(his Catholic vice-president also seems to be doing well as of late too). I expect that any model of people that doesn't tolerate the complexity and malleability of human experience and belief will ultimately not represent the world well. That will lead to disappointment. You should get over that quickly. I'm certainly far from perfect, my views change over time, perhaps the same is true for you. As Lincoln pointed out that Those who look for the bad in people will surely find it, I'm often guilty of that myself.
Should we fear a world-view that locates most of the world's problems in other people? The flaws I'm most concerned about are my own (which are more than obvious though I'm certain I have more that you can locate). It is because of those flaws that I need to live in a place that is patient and loving.
Should we fear a world-view that builds a path to redemption via being maximally unpleasant to others who disagree? Or is it better to try hard to "Act justly and to love mercy and to walk humbly with your God" (Micah 6).
Is being offended occasionally by others' (truly objectionable) beliefs the price of collaborating with people with diverse viewpoints, discussing anything and everything without boundaries and learning? Not always a small price to pay, but is it not necessary? Surely it is the case that each member of outlying groups benefits from mutual tolerance. Indeed we often celebrate the amazing contributions to society of those who (at the time) were viewed to have unacceptably fringe beliefs & practices. Becoming a less tolerant society is potentially polarizing and dangerous.
What is love's response to a neighbour in need in this instance? Probably it is to vigorously encourage RMS to setup a representative governance so actual users of the GPL family can determine its post-RMS future. Perhaps it is to loudly re-iterate the obvious: that RMS does not represent you or me - and that we don't share the details of his unusual politics; to make more obvious that personal views are disjoint from organizations' missions, and to ensure we are able to choose our representatives in a secret ballot. But love's response is certainly not to let Free Software get twisted into a new and narrow orthodoxy consumed by gender politics to its own harm and the exclusion of others. We should remain a broad, tolerant and inclusive church even when it hurts. We used to be focused on liberty & freedom - I miss that.
"We ask for contributors to free software projects to take a stand against bigotry and hate within their projects."
Bigotry - a stubborn and complete intolerance of any creed, belief, or opinion that differs from one's own.
It seems obvious to me that this new orthodoxy combined with political power is rather dangerous. Perhaps those who have not grown up with some of the common stories would do well to read them. How about the fiery furnace - takes two minutes of your life; but why is it so hard to show due respect to the pagan government's request? is that really breaking the 2nd commandment? Or - if you have a very strong stomach - try just eat the pork: why won't they obey orders from an authority (Epiphanes: 'god manifest') - perhaps interesting? What requirements or forced conformity might be too much? Is there a shortcut via coercion to truly change society to how I want it to look? or is winsome persuasion the best way? Of course there is a shameful record of burnings, division & bigotry - often over rather small divergences in orthodoxy throughout the Church's history, without even getting into where major creeds interacted at a larger world scale. Then again I'm sympathetic to the Pastafarian concern that arbitrarily unreasonable creeds can be created, and that other points of view have no systematic orthodoxy to protect them which seems unfair: surely it is so: so lets treat all people fairly when our worlds collide.
"We want to hire diverse people - but only if they are exactly like us."
One of the things that has saddened me most among those I've worked with in the past is that it is now acceptable for people to say that they would not hire people with beliefs that I know many wonderful, excellent, Christian programmers have. There is a rising tide of intolerance of those that are perceived not to kowtow to the new progressive orthodoxy.
Generally an attitude of graciously accepting others' hostility has held, along with avoiding law-suits. I fear though that as attacks on believers' presence in Free Software get more explicit there will be a slowly growing realization of the problem here. Not to pick on Mozilla (though they did sign this problematic statement) but I'm curious how views that are 'traumatic and damaging' can be accommodated there. I think it is past time to start monitoring religious affiliation as well as ethnicity as part of diversity.
Can any company explain how These sorts of beliefs have no place in the free software, digital rights, and tech communities can intersect with companies that build products around such communities? Surely we can find lots of quotes saying how important community is to developing software. Surely we can find statements that employees are members of such communities. So is it really credible to a-priori exclude masses of people on the basis of their beliefs from your employee pool? Does that extend to refusing to hire people based on their beliefs? Or perhaps people with incompatible beliefs just get inferior jobs inside the company partitioned away from those communities? Certainly - I feel far from safe & welcome applying to one of the listed companies there without further re-assurance. It is deeply ironic that in the past one of the (baseless) explanations from some of the more reasonable people I talk with for excluding believers from management is that they might discriminate when hiring.
If this statement was focused on leaders, it could be characterized as installing a new glass-ceiling for any who are not progressive-orthodox. Even if it were re-written as a criteria for leaders - I'm still far from sure we will get better leaders by selecting for conformity rather than competence.
As the virtual becomes increasingly more important than the physical for some people's livelihoods hopefully we can all agree that encouraging equitable behaviour online is a good thing.
As should not need saying: these views are mine, my own. I don't speak for my employer, nor any projects I'm affiliated with, nor my Church, or my friends. Feel free to borrow any views you find persuasive or reject any you find objectionable.
2021-04-14: Impressed to receive a very gracious apology from Matthew G for his language; though of course - I'd prefer movement on the substance; good chap; (he approved this, and tweeted). Also an amusing comment from a friend on the parallels between Act justly, and to love mercy and the Robustness principle
I posted about Writer gutter margin in general back in February, and two follow-up requests accumulated around this new feature since then.
First, the gutter margin could be on the left or at the top for non-mirrored documents, which initially sounded like a complete solution, but later it turned out that right-to-left (RTL) documents want it on the right.
Second, there was a request from the OASIS TC to to implement the ODF filter differently for gutter margin.
Neither of these is simple to do, so this hackweek was a good opportunity to address these problems.
Here is the layout and user interface for RTL gutter looks like:
You can see how the gutter is on the right (not the left) and you can alter this behavior with a dedicated checkbox on the UI.
If you would like to know a bit more about how this works, continue reading… :-)
sw page rtl gutter margin: add doc model introduced a new RES_RTL_GUTTER page style property
sw page rtl gutter margin: add UNO API added a new public RtlGutter UNO API property
sw page rtl
gutter margin: add layout was the tricky layout piece, extending SwBorderAttrs
sw page rtl
gutter margin: add DOCX filter mapped this to DOCX’s <w:rtlGutter>
sw page rtl
gutter margin: add ODF import mapped this to <style:page-layout-properties
style:writing-mode="..."> in case the attribute value is RTL
sw page rtl gutter margin: add DOC filter mapped this to DOC’s SFRTLGutter, amusingly that handling of that was somewhat there, but more or less broken since 2002-02-04
sw page rtl
gutter margin: add RTF filter mapped this to RTF’s \rtlgutter section flag
sw page rtl gutter margin: add UI introduced a new checkbox on the UI to set/get this, and fixed up notifications, so that the incremental layout repaints the necessary page frames when this setting changes
Finally I had a little bit of remaining time, so I addressed a request from the OASIS ODF TC:
sw page gutter
margin: reimplement ODF filter changed the ODF markup to be more compatible with readers ignoring
<style:page-layout-properties loext:margin-gutter="...">
Collabora intends to continue supporting and contributing to LibreOffice, the code is merged so we expect all of this work will be available in TDF’s next release (7.2).
Kudos to Ilmari Lauhakangas for helping to elaborate this list.
654 bugs, 69 of which are enhancements, have been reported by 414 people.
Top 10 Reporters
698 bugs have been triaged by 101 people.
Top 10 Triagers
637 bugs have been set to RESOLVED.
Check the following sections for more information about bugs resolved as FIXED, WORKSFORME and DUPLICATE.
224 bugs have been fixed by 51 people.
Top 10 Fixers
List of critical bugs fixed
List of high severity bugs fixed
List of crashes fixed
With Clang12 almost released, I guess it's high time to write a conclusion to the Clang11 changes that improve compilation times with PCHs. I originally planned to do this after the Clang11 release, but with the process to get the changes reviewed and merged having been so tedious I was glad it was finally over and I couldn't at the time muster the little extra effort to also write this down (I spent way more time repeatedly writing 'ping' and waiting for a possible reaction than writing the code, which was really demotivating). But although the new options are described in the Clang11 release notes, I think it'd be useful to write it down in more detail.
First of all, I've already written why C++ developers might care, but a thousand pictures can be worth more than a thousand words saying how this can save you even 60% of the build time:
You may want to check that your ccache and icecream are not too ancient if you use them, but by now any reasonably recent version should do. And if you need to do changes that would repeatedly trigger larger rebuilds (such as changing a header), the trick to temporarily disable PCH builds is to do 'make BLOCK_PCH=1'. And since PCH builds sometimes cause build errors in non-PCH builds because of missing #include's of headers, it's a good idea to touch all your changed files and do 'make BLOCK_PCH=1' before pushing your change to Gerrit. This is all you should need to know, the LO build system will take care of everything else.
As for the rest of the world, this boils down to the two PCH-related sections in the Clang11 release notes.
The first one is using -fpch-instantiate-templates. It needs to be set when building the PCH, but it will work even if you just add it to the CXXFLAGS used for building everything. Recent enough CMake version should handle this option automatically, I have no idea about other build systems. It should be safe to enable the option for any building with PCH. It's not enabled by default in Clang only because of really corner cases with PCHs that are not self-contained. In other words, as long as your PCH works with an empty .cpp file, it's safe, and if your PCH is not self-contained, you'd be better off fixing that anyway.
The second part using -fpch-codegen -fpch-debuginfo is more complicated, as it requires build system support, and I'm not aware of any build system besides LibreOffice's providing it. This discussion in a CMake ticket provides an example of how to use the option that seems rather simple. For other build systems have a look at the description in the Clang11 release notes for all the details and possible complications, and consider whether it'd be worth it. Which it sometimes may not be, as this graph from my previous post shows (Clang means normal PCH build, Clang+ means only -fpch-instantiate-templates, Clang++ means all 3 options).
Note that you may get rather different results depending on how much you put in your PCHs. Unlike before, now the general rule should be that the more you add to your PCHs, even if shared only by several source files, the faster the builds usually will be. And since these options move building some code to the PCH-related object file, the improvement is usually even better for incremental builds than full rebuilds. I've been using PCHs this way for slightly more than a year, and I forgot already quite some time ago how slow it used to be.
I should ask you Lubuntu maintainers: please build LibreOffice with vcl:kf5 instead vcl:qt5. Because LibreOffice's vcl:qt5 backend still buggy and unstable. Look at it:
I just tried to use Lubuntu 21.04 beta, opened LibreOffice Writer and I wanted increase a scale of the page. So you can see what I saw: wrong vertical rule, ugly page view, etc.
by Roman Kuznetsov (noreply@blogger.com) at April 04, 2021 05:45 PM
The bibliography feature in Writer allows authors of e.g. scientific papers to track sources: first you can insert bibliography entry fields, then at the end you can generate a bibliography table automatically.
Writer now has two improvements in this area: more information about these entries in the form of a mouse tooltip and clickable URLs in the table.
First, thanks TUBITAK ULAKBIM who made this work by Collabora possible.
Generating a bibliography (table) for a document is a two-step process: first the user inserts bibliography entry fields to refer to sources, then later the bibliography can be auto-generated. It was not great that details of a source was only visible in the Writer edit window after generating the bibliography table. A somewhat related shortcoming was that URLs of sources were handled as plain text, while users expect that references are also clickable, similar to e.g. table of contents.
This is how a tooltip looks like, available even if there is no bibliography table yet:
And URLs in the bibliography table are now clickable:
If you would like to know a bit more about how this works, continue reading… :-)
As usual, the high-level problem was addressed by a series of incremental development steps:
sw tooltip on bibliography fields: add an SwTOXInternational factory and sw tooltip on bibliography fields: add a text factory that gives us a string were necessary refactors to get a string that looks like a row in the bibliography table, without having an empty bibliography table at hand
sw tooltip on bibliography fields: add the actual tooltip functionality improved the UI to have a tooltip
sw bibliography: make URLs in the bibliography table clickable implemented the clickable URLs feature
Collabora intends to continue supporting and contributing to LibreOffice, the code is merged so we expect all of this work will be available in TDF’s next release (7.2).
DevTools implementation has been completed and this is the third and final part of the mini-series. The focus of this part is on the object inspector, but I have also improved or changed other DevTools parts, so first I will briefly mention those.
 |
| Figure 1: Development Tools location in the menu |
 |
| Figure 2: Document model tree view and "Current Selection" toggle button |
 |
| Figure 3: Top toolbar and tab bar in object inspector |
 |
| Figure 4: Object inspector "Properties" tab |
 |
| Figure 5: "Properties" tab and the text view |
 |
| Figure 6: Object inspector "Methods" tab |
by Tomaž Vajngerl (noreply@blogger.com) at March 24, 2021 07:42 AM
In the previous blog post I explained the reasons and some issues on exporting LibreOffice Guides to the xHTML format. Now it is time to give more technical details.
I choose to use the extension writer2xhtml available in the Extension website, because the produced HTML5 look less cluttered than the native XHTML export. Nevertheless there it will be necessary to add some extra HTML5 lines, to load the CSS and a Javascript file.
There are some changes that should go upstream, because it does not change the resulting PDF or ODT book layout.
Each image must be anchored “as character” in the document. The image becomes a character and must be single in the paragraph. The paragraph must be centered in the page, using a style that aligns in the center, for example, the “Figure” paragraph style. The image caption paragraph must have style “Caption”. The wrapping frame that holds the image and the caption must also be anchored “as character” in a paragraph with style “Figure” as well. This arrangement is transparent when producing ODT, PDF and HTML5 documents.
Tips, Notes and Cautions headings use graphics as bullet. Many of these paragraphs have the bullet enabled by direct formatting and this is invisible to the user in LibreOffice, but will show when exporting to HTML5 with an ugly black circle.
Create a table style, or copy it from the table in the copyright section. Name the style as you want, custom table styles are stored in your user profile. Apply this style to all tables in the chapter. Open the table properties of each table and set alignment to “Centered”, and table width in 90%.
Remove cross references to pages. For example, “See figure 12 on page 30”. At best, use the “above” or “below” in the reference.
Add the sections described in 2,3 and 4 below.
The original chapter file is optimized for a book format, we need to prepare it for exporting to HTML5 where pagination is different, mostly by smooth scrolling. This involves steps but will not change the chapter contents, only the layout and some formatting
With the images anchored as explained above – a step that may require manual work – move the caption above the image. This can be quickly done by placing the cursor in the caption text and pressing Ctrl+Alt+Up Arrow, to swap the caption paragraph with the image paragraph. Some chapter have dozens of images so it will be nice to have a script to bulk execute this swap.
Wrap the top LibreOffice logo in a Section named “SEC_LOGO”.
Wrap the Guide name in a section named “SEC_GUIDE”.
Wrap the chapter title in a section named “SEC_TITLE”.
Delete the existing table of Contents.
Select the text from the copyright heading to the end of the chapter and wrap in a section named “SEC_DISPLAYAREA”. Ensure you leave some empty paragraphs after the end of the section.
On the bottom of the chapter, after the SEC_DISPLAYAREA section, add 6 new empty sections: SEC_TOC, SEC_BOOK_TOC, SEC_SEARCH, SEC_IMPRINT, SEC_DONATION, SEC_NAV. You can create these 6 sections in an empty document and load it as Autotext, so all section can be inserted in a single command using Autotext (Ctrl+F3).
Insert the chapter table of contents in the SEC_TOC section.
Change the template of the chapter to the provided template odf2htmlv2.ott.
Review the ordered and unordered lists in the chapter. The new template may highlight the spurious bullet and numbering inserted by direct format, and as explained above, is very hard to detect in the original ODT file. Some of these list direct formatting may also be detected in the HTML5 output.
Save your working copy.
The extension writer2xhtml adds a toolbar for exporting on a click. The extension allows some customization, not used here. The export used “original format” style and 115% font size.
The export is very fast and gives no choice to change the export name, so the exported file has same file name and html as file extension, overwriting existing files with same name and extension.
By default the exported file name opens in the system browser for inspection. The result is not yet what we want, we must apply specific CSS and Javascript for rearranging the layout of the sections. The se files are added in the HTML5 output juste before the </head> closing tag.
<link href="guideposition.css" rel="Stylesheet" type="text/css">
<link href="guideformats.css" rel="Stylesheet" type="text/css">
<script type="text/javascript" src="GS70.js" defer></script>
Two extra CSS files were created, one is guideposition.css and manages the sections position in the page, and has provision for handling other screen sizes such as in tablets. The second CSS file is guideformats.cssthat contains rules to override some attributes such as lists, fonts, font-size, colors, margins, padding and more of the sections.
This file fills the empty sections we added at the end of the chapter. Contents for donation, guide table of contents (jump between chapters), a legal imprint, a search form (to be implemented) and more. The javascript file is common to all chapter and is custom to the guide.
Exporting the LibreOffice Guides to HTML is another way to offer a rich contents to the public. Guides in HTML format can be installed in servers of schools, libraries, colleges and corporations alongside with a PDF copy, to support a migration project.
The rich set of features of Writer, while allowing the creation of wonderful documents, is also source of concern not only when exporting to formats that are less flexible that ODF, but also to manage the excess of freedom. The changes recommended and the detection of hidden direct formatting in lists are examples. It becomes clear that a set of sanitizing scripts can help to remove spurious formatting, unused legacy styles, detect unwated extra styles and adjust the objects in the documents.
When handling the full set of guides it is easy to dream of an office suite that can execute some "wishes" like "anchor all images as characters and center in line", "change position of caption in all frames to top", "format all tables with style 'guides' and align to center"... but that is for an office suite of the next generation!!!.
Partial results of all this work can be visualized below.
The getting started guide in HTML format.
Happy documenting!!!!
by Olivier Hallot (noreply@blogger.com) at March 22, 2021 03:25 AM
So, as I wrote before, MS broke LibreOffice work (and just broke many Windows 10 system) with its stupid update KB5000802.
OK, they gave us the fix for that problem. But it will be optional (!!!!). You should install it manually if you have the problem!
For Windows 10 20H2 and Windows 10 (2004) install KB5001567,
For Windows 10 (1909) — KB5001566,
For Windows 10 (1809) — KB5001568
For Windows 10 (1803) — KB5001565.
Why they made it different for different builds of ONE OS Windows 10, I don't know. And I think they don't know too.
You can find your Windows 10 build number in system options - system - about (I can show you only Russian variant):
by Roman Kuznetsov (noreply@blogger.com) at March 17, 2021 09:54 AM
by Popa Adrian Marius (noreply@blogger.com) at March 14, 2021 09:47 AM
If you use Windows 10 and you didn't disable its updates then you could got an update KB5000802 pair days ago that breaks LibreOffice work. If your LibreOffice crashes or doesn't print now, then:
- Delete that Windows update KB5000802
- Delete LibreOffice, include a user profile from C:\Users\User_name\AppData\Roaming\LibreOffice
- Reboot Windows
- Reinstall LibreOffice
If these steps didn't help, please write a comment here. Thanks
by Roman Kuznetsov (noreply@blogger.com) at March 13, 2021 09:37 PM
Templates contain generic content and structure, and are meant to create multiple documents. In contrast, a document is intended for a single use. While both types are more or less the same, the advantage of templates is the handling within the program (→Template Manager).Templates can seem daunting and overly complex as any new concept. Hopefully this series of articles will help to understand and clarify some of your worries. If you have never heard of templates or if, for any reason, you tend to avoid them- this is for you.…
Kudos to Ilmari Lauhakangas for helping to elaborate this list.
659 bugs, 75 of which are enhancements, have been reported by 399 people.
Top 10 Reporters
599 bugs have been triaged by 101 people.
Top 10 Triagers
522 bugs have been set to RESOLVED.
Check the following sections for more information about bugs resolved as FIXED, WORKSFORME and DUPLICATE.
153 bugs have been fixed by 37 people.
Top 10 Fixers
List of critical bugs fixed
List of high severity bugs fixed
List of crashes fixed
List of performance issues fixed
List of old bugs ( more than 4 years old ) fixed
110 bugs have been retested by 33 people.
Top 10 testers
On 1 October 2020, Collabora Online moved to its new home on GitHub, and started settling in the new infrastructure, expanding its fantastic community, and continuing the work to deliver the latest and greatest developments in productivity and collaboration together. Check our new community website for all the details! 
Collabora developers also keep fixing and improving our lovely mother project LibreOffice. As all the good work requires some appreciation, let’s take a look at what the seasoned developers of the Collabora team and the volunteer contributors from our community have been doing during the last 2 weeks.
On the Collabora Online code repository in the last week, 11 authors have pushed 42 commits to master and 72 commits to all branches. On master, 48 files have changed and there have been 1,567 additions and 835 deletions.
Congratulations to Gianni154, Samuel, sowoi, oiselarius and SerjSX for reporting their first issues and improvement requests on our GitHub repository!
Thank you all, and welcome aboard! 
You can also join the fun, and be part of our next list of new contributors!
Just go to our GitHub repo, fork it, build it (on Linux or on any platform), grab one of our newcomer-friendly easy hacks, and send your first pull request. And if you get stuck at any point, just drop by one of our communication channels.
COOL Weekly Meeting #13 has taken place on Thursday, February 18, 2021 at 11:00:00 am (UTC) with participants both from the community contributors and the Collabora team. We have got a quick update on what’s going on and discussed matters raised by the contributors, as well as having the chance to say hi to fellow members of the community. Topics discussed in the meeting include:
Check out the meeting minutes for the details of the meeting, and join us on Thursday, March 04, 2021, at 11:00 am (UTC) to stay in touch with the rest of the community. You may also make your own suggestions for the next meeting by following the link shared in the COOL Telegram group before the next meeting. We’re looking forward to hearing from you live.
Last but not least, we can’t thank enough to our translators who constantly help COOL and its friends talk many languages on this earth. Collabora Online speaks many languages, thanks to all of our translators in our translation project, and all of those who previously contributed and keeps contributing to our mother project, LibreOffice.
We’re continuing to work to find good ways to credit translators’ hard work in the product. Please see a list of those involved, and please get in touch if you’re not listed. Many thanks to all those who have worked on translating Online, you rock!
If you would like to help COOL speak your language, you can just go to our translation project on weblate, and start contributing!
We’re still contributing to LibreOffice and encourage you too to do so because LibreOffice rocks.
The post Collabora Online Community Roundup #10 appeared first on Collabora Office and Collabora Online.
| 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 Uwe Altmann 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). |
|
