Jim Jagielski himself has argued (both on LWN and on the Apache lists) for this state of affairs to continue. It was pretty obvious to people paying attention that even when IBM were still paying people to hack on (A)OO it had no community buy-in, but the last six months have demonstrated that the Apache Foundation would literally rather that low-information end users get compromised than have them use maintained code.

This ridiculous charade has to end soon (and almost certainly will: if it takes over six months for the current 'development team' to put out the sort of trivial point release that LibreOffice puts out like clockwork then it's likely that this one will be the last). Verified checksums and signatures for these binaries and source tarballs.īesides the usual testing of existing documents and creating new documents, ran through an automated test.Posted 18:09 UTC (Mon) by thumperward (guest, #34368) Used the en-US rpm install for Linux and the en-US exe for Windows and also installed the SDK for both platforms. On Linux Ubuntu 20.04 圆4 opened ODT, ODS, ODP and ODF as well as DOC, XLS, PPT and DOCX, XLSX and PPTX files without any issues.

Installed the en-US plus PT language packs as well as the PT installer under Windows 7 圆4, and Linux Ubuntu 20.04 圆4. Tested checksums for the install files en-US, de, esĮxisting, older DOCX, XLSX, PPTX documentsĬreated new docs for Writer, Calc, Impress and opened / edited the saved file with all languagesĬhecked the Source signature and SHA256 and SHA512 CRCs as well as both CRCs for the Linux 圆4 and Windows x86 main installer in en-US and PT and for the PT language pack binaries

How to use apache openoffice 4.1.2