LibreOffice 7.1 Community released with support for M1 ARM Mac and 'user interface variants'
- Reference: 1612440785
- News link: https://www.theregister.co.uk/2021/02/04/libreoffice_71_released_with_user/
- Source link:
The download on the LibreOffice site is called 7.1 Community, in an effort to get businesses to sign up with an "ecosystem partner" for paid-for support.
[1]
"An increasing number of enterprises have chosen the version supported by volunteers over the version optimized for their needs. This has had a twofold negative consequence for the project: a poor use of volunteers' time, as they have to spend their time to solve problems for business that provide nothing in return to the community, and a net loss for ecosystem companies," [2]complained the post introducing the new release.
We are also informed that 73 per cent of commits to the LibreOffice code come from developers employed by these companies.
[3]
[4]
The User Interface dialog asks the user to choose between seven different options
What is the technical difference between the community and enterprise versions?
While it is possible for the commercial LibreOffice providers to customise their builds and add features, the "community" version is not cut down. "There will be no difference in features in the version offered by TDF. The software isn't changing at all. This is a label on the name, nothing else," [5]said Mike Saunders, who does community outreach at TDF.
The issue is nevertheless a concern for users on two counts, one being that the business model behind the project is under threat, and the other that the suite is getting less Libre. Although the project is under-resourced [6]according to some key members , this is partly is down to oddities in the way it is financed as TDF itself is said to have large cash reserves.
[7]
A chart in LibreOffice Calc 7.1
What's new in 7.1?
Along with numerous small changes and performance improvements, one point of interest is a new dialog for selecting a user interface (UI). LibreOffice supports several UI variations and this dialog is presented on first start and available thereafter in the View menu.
Much complexity and history lurks here. Menu bloat is a problem with these massive office applications, which Microsoft addressed with its ribbon UI in Office 97.
Some users preferred the old drop-down menus which became a selling point for alternatives such as OpenOffice, from which LibreOffice was forked. On the other hand, familiarity with Microsoft Office raised expectations that other office suites would follow. The consequence is the LibreOffice today has some ribbon-like features, also retains drop-down menus, and provides options to customize the mix.
The UI variant dialog has seven options, starting with Standard Toolbar and including Tabbed, described as "most similar to ribbons used by Microsoft," though in practice the look and feel is very different. We found that the standard UI is the most consistent, with clutter and duplication are issues with some choices.
In Writer there is a new Style Inspector, which aims to answer the question "why is this text formatted the way it is?" The combination of paragraph styles, character styles and direct formatting can make this a puzzle. Those who enjoyed Reveal Codes in WordPerfect (remember that?) will like this feature.
Scripting LibreOffice will be easier thanks to the addition of [8]ScriptForge libraries , which can be invoked from Basic macros.
Features include array operations, string functions, "coherent error handling," file operations, and interop between Basic and Python. There are also examples to overcome what has been described by co-author Jean-Pierre Ledure as a "LibreOffice Application Programming Interface (API) steep learning curve."
Users with Apple's shiny new M1 silicon will find a native ARM64 build. "Both LibreOffice Vanilla and Collabora Office in the Mac App Store are universal apps, i.e. they come with both x86_64 and arm64 code in their binaries. (And even without that, x86_64-only builds work fine on Apple Silicon Macs, too, thanks to Rosetta)," [9]said Collabora engineer Tors Lillqvist, a LibreOffice developer.
There are also build instructions for Windows ARM64, though "it is in early development and has some known limitations," according to the [10]release notes .
Other changes include an outline folding mode in Writer, soft blurred shadows for objects in Impress and Draw (presentations and graphics), better SmartArt compatibility with PowerPoint, and a new dialog for installing extensions.
[11]
LibreOffice lacks the polish of Microsoft Office, and is primarily a desktop tool in an era of cloud and mobile, but its existence is of great value for Linux desktop users and others in search of an open-source alternative. ®
Get our [12]Tech Resources
[1] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2YBwoLMgLlOiZdjG@R8lGqwAAAI0&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[2] https://blog.documentfoundation.org/blog/2021/02/03/libreoffice-7-1-community/
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YBwoLMgLlOiZdjG@R8lGqwAAAI0&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[4] https://regmedia.co.uk/2021/02/04/uivariant.png
[5] https://blog.documentfoundation.org/blog/2021/02/03/libreoffice-7-1-community/#comment-76223
[6] https://www.theregister.com/2020/07/16/libreoffice_ecosystem_beyond_utterly_broken/
[7] https://regmedia.co.uk/2021/02/04/lo71-calc.png
[8] https://blog.documentfoundation.org/blog/2021/01/28/introducing-the-scriptforge-basic-libraries/
[9] https://www.collaboraoffice.com/desktop/update-on-libreoffice-support-for-arm-based-macs/#comment-250820
[10] https://wiki.documentfoundation.org/ReleaseNotes/7.1
[11] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YBwoLMgLlOiZdjG@R8lGqwAAAI0&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[12] https://whitepapers.theregister.com/
Re: Mixed messages.
Seems odd - baking your own cake and then paying to eat it.
Re: Mixed messages.
Erm... where are you getting your ingredients from? ;)
Re: Mixed messages.
When an arrogant project starts antagonising its users, it is destined to lose them.
A poor use of volunteers' time
"An increasing number of enterprises have chosen the version supported by volunteers over the version optimized for their needs. This has had a twofold negative consequence for the project: a poor use of volunteers' time, as they have to spend their time to solve problems for business that provide nothing in return to the community,..."
I don't know, a bug is a bug no matter if its reported by a business user or a home user. On top of that, the horrible UI and other usability deficiencies surely are not just paining business users but home users as well, so I fail to see how businesses using the free Community version would waste volunteers' time.
To me this reeks more like a stark attempt to get business users to pay up for TDF's support partners.
Re: A poor use of volunteers' time
I'm not sure we can assume that all support calls are bugs..... if only that were true :-)
Re: A poor use of volunteers' time
I think creating 7 alternative user interfaces is the biggest waste of volunteers time.
Lacks the Polish?
Rubbish.
Office 2007 and later are a shiny mess. Though there is a third party replacement for the evil ribbon, which makes access to features WORSE than conventional menus.
LO is far superior to MS Office 2003 in GUI and Writer works better than Word. The mistake is to use doc or docx for saving. Only use them to import or export. Use Styles properly. The undocked Style and Navigation windows are superior to MS Word 2007.
Re: Lacks the Polish?
If yours lacks Polish then you might need to download the correct language pack or version https://www.libreoffice.org/download/download/?type=deb-x86_64&version=7.1.0&lang=pl
Re: Lacks the Polish?
Gdansk you for that…
Re: Lacks the Polish?
"...LO is far superior to MS Office 2003 in GUI and Writer works better than Word. The mistake is to use doc or docx for saving. Only use them to import or export. Use Styles properly. The undocked Style and Navigation windows are superior to MS Word 2007..."
Or... as a business user, just use Word. You know it's compatible and you're not messing around with different formats to save or to export. You may be happy to do this but your average user doesn't want extra steps just to do their day job.
And here's an oft-overlooked point with regards to the ribbon in Office 2007.
MS did a ton of user research into the next features for Office.
And found out that a huge percentage of them were actually already available but users didn't know and/or couldn't find them.
So the aim of the original ribbon was to simplify that mess of sub-menus.
Which worked. For a time. But if you look at the last few releases of O365 you'll notice that MS are once again working hard to simplify the ribbon because like the original menus it's become cluttered and far less than intuitive to find things anymore, utterly defeating the whole object of having it in the first place.
I work in the EUC space. If you ask users, then the ribbon never comes up as being an issue for them except perhaps where some addon to e.g. Outlook or Excel has failed to put their icon onto it.
Rather than the ribbon, personally I find one of the areas where Word in particular is still ropy is collaborative working. Once a document gets above about 100 or so pages, it becomes a mess. Changes not saving or disappearing when someone edits a completely different part of the document. Corruption etc. That really is something they need to sort out properly because it's tedious as fuck working on an online copy and having to save a local backup just in case it decides to shit on the online one.
Re: Lacks the Polish?
I'm sorry as a business user I find LibreOffice opens old MSWord documents better than a modern MSWord, What's funnier is it produces better quality MSWord documents than MSWord does. Often 20-30% smaller for the exact same content.
YMMV
AAC
Re: Lacks the Polish?
Yeah, LO opens Word files just fine. It even saves small, not overly complex, Word files as DOCX without serious problems. Large, complex documents are an entirely different case. On several occasions around here LO has mangled the job of taking a DOCX file, making changes, and saving it as a DOCX file. I simply no longer trust it to round trip DOCX files. I _must_ be able to send DOCX, and usually receive DOCX. We tried to go all LO internally, but we can’t control documents from outside, which are almost always MS Office formats. Hell, we use Pages, despite its faults, for certain types of files and export to DOCX… and Pages doesn’t screw up the format, so it can be done. LO either can’t do it or doesn’t want to do it. Either way, they’re off the list of office suite replacements for MS Office. It’s a pity, really, they did a lot of things very well indeed, but we just can’t live with the round trip problems. And as long as we have to do business with people who use MS Office we will have to do round tripping. Pages, Numbers, and Keynote can round trip, with very few problems. LO, not so much. At least not in our experience. If this changes, perhaps then LO would be considered. Until then, it’s MS Office and Apple’s suite for us. Mostly MS Office.
Re: Lacks the Polish?
Wow: 12 years and people still can't cope with a GUI change...
There's nothing wrong with the Office ribbon. There isn't now, and there never was. Just old people who can't learn new skills (systemd)
Re: Lacks the Polish?
No, Writer is NOT better than Word. Style support is not as good as Word 2003; Word style support has improved with every new version, so Word 2019 is _considerably_ better at it than Writer. Table support is improved over what it was, but still isn’t up to Word; LO’s problem is that Word has had good table support since 1986, LO has a lot to catch up on. At least they’re better with tables than with styles. (Yes, I spend a lot of my day with tables, and use styles a LOT, I don’t use Pages because I hate the way it does styles, and, to a lesser extent, tables.)
Worse, the suggested ‘save as ODT, export to DOCX’ causes problems. Part of it is that DOCX is a moving target. Part of it is that some LO features are not available in DOCX, including lots of stuff to do with styles and tables, and this appears to be deliberate; things under the hood are not quite compatible. Exporting causes complex documents to have serious problems. (Guess how I know) And because some features are not available in DOCX, you _must_ save as ODT and export… and then spend time fixing the problems.
The majority of my documents go to MS Office users. It’s simply easier to just use MS Office and have done.
I don’t care about the Ribbon. I really don’t. I do care about my documents. I can generate documents my way with MS Office and minimal effort, while it takes effort to do the same in LO, and more effort to fix the exports.
And, one more thing: there are MS Office versions available for iPad. No official LO for iPad. I can touch up my MS Office documents from my iPad, but not any LO documents. Being able to fix things on an iPad has been a lifesaver more than once. Not having an official iOS version is a significant handicap for LO.
YMMV.
Basic macros & file operations
Oh dear, I hope that isn't an accident waiting to happen. A whole new world of toxic documents.
Re: Basic macros & file operations
Downvoted for the old reference. Also, the ribbon was a pig to get to know and that is one of the reasons I persisted with Open Office and into LibreOffice. My boss lady was a big user of Office productivity software and she hates the ribbon still. Menus evolved a long time ago and they work. Getting rid of them was not wise.
And yet no Android version
They can slap it on an M1, yet cannot slap it on Android and run it on a tablet?
The problem here is Google's choices with Android:
No paged virtual memory support in Android, apps are limited to 512Mb heap, Windows had virtual memory since Windows 3.1 in 1992 FFS, so why not Android? You Google programmers know how to do a the super-fast paged heap garbage collector/compactor right? The type where you remap pages not copy bytes around? These are 64 bit processors now, you have all that address space to page into. You can make it faster AND support large memory models for apps in Android. I have a tablet in front of me that cost barely $150 and has 8GB RAM, and yet the OS on it lets me access 1/16th of that RAM! This needs fixed!
Android apps have a lifespan determined by Google code, not the user. So no "save work before exit?". That data you worked on all day? Poof and its gone when you switch apps.
Poor cross platform independence, all the crap of variable screen sizes is loaded onto the apps.
Piss poor stylus support. By default (excluding Samsung) you won't get hover events in Android, so apps cannot use stylus-Hover unless they're designed exclusively for Samsung devices.
Mouse events likewise not device independent, a click isn't downgraded to touch event if the app doesn't support clicks.
Some incredibly bad GUI design choices. Take a tablet it will usually be used in landscape, so its a letterbox with limited vertical screen space. So then someone decides to take the top part as the status bar, and the bottom part as the navigation bar. A big thick bar across the bottom with 3 pissy little buttons on it. So now your landscape tablet screen is even more letter box format! WHY?
You can hide the bars in an app, but that only really works if you hide top AND bottom together (your full screen mode puts the app interface under the status bar even if you're not going to hide the status bar) and those bars will pop straight back up when you tap the screen. You tap on the app to do something and the navigation bar pops right back up as if every tap means the user is finished with the app. This is a business app and you probably want the status bar there all the time, but the navigation buttons you only need when you're finished with the app..... and since they are designed to work on a phone in portrait, you could fit the navigation buttons on the middle of the status bar in when in landscape. There simply isn't a need to waste huge tracts of screen.
It should be trivial to port apps like Libre Office to Android and get them to work consistently, but it is not. Fix this.
Ribbon UI in Office 97?
Much complexity and history lurks here. Menu bloat is a problem with these massive office applications, which Microsoft addressed with its ribbon UI in Office 97.
No, Office 97 was a good version! The ribbon was introduced in Office 2007 for Word, Excel, Powerpoint and Access.
I switched my company to Open Office and then Libre Office as my users wanted to cling on to Office 97 well into the 21st century. It's always been good enough for what we needed, although LO has performed significantly better in later releases.
And yes, I used to donate to TDF
a desktop tool in an era of cloud and mobile
And highly to be praised for that.
I'm not part of a team working on collaborative documents; my documents, my storage, my problem, thanks.
Re: a desktop tool in an era of cloud and mobile
And well suited for the coming era of safely air-gapped corporate documentation..
I donated
I donated. As an individual. They have a 501(3)(c) which is good for us old farts doing QCDs from our tIRAs.
Mixed messages.
On one hand they say companies are taking the product and not giving back, putting a strain in developers then state...
"that 73 per cent of commits to the LibreOffice code come from developers employed by these companies"
Or do they mean the support companies, rather than the end user companies?