The Document Foundation announces the availability of LibreOffice 3.3.3, a new release of the most stable version of the free office suite for personal productivity, targetingcorporate users. LibreOffice 3.3.3 is already available for download at the following address: http://www.libreoffice.org/download. According to Thorsten Behrens, a developer and member of the TDF Steering Committee, “LibreOffice 3.3.3 fixes several bugs and improves the security of the suite, to specifically address the needs of corporate deployments, where stability is more important than new features.
This branch will be maintained until the end of the year, to allow a smooth and safe transition to LibreOffice 3.4.x.” LibreOffice 3.3.3 is available for Windows, MacOS X and Linux (DEB and RPM), in over 100 different languages (more than twice the language coverage of comparable proprietary products). Users of LibreOffice 3.3.2 are invited to update theirsoftware.
This is the third update to the stable version of LibreOffice.
It contains only safe code fixes and translation updates, and is considered safe for production use.
Please check some changes in this stable release
This release is bit-for-bit identical to the 3.3.3 Release Candidate 1, so you don’t need to download or reinstall if you have that version already.
The distribution for Windows is an international build, so you can choose the user interface language that you prefer. Help content is available via an online service, or alternatively as a separate install.
For Windows users that have OpenOffice.org installed, we advise uninstalling that beforehand, because it registers the same file type associations.
If you run Windows 2000, you may require this update before being able to install LibreOffice.
If you run Linux, the GCJ Java variant has known issues with LibreOffice, we advise to e.g. use OpenJDK instead.
LibreOffice contains all the security fixes from OpenOffice.org in 3.3.0, and perhaps more as a side-effect of the code clean-ups.
For install Please follow instructions in our previous post