AbiWord 2.1.6 "Maple Syrup Chronometer Cleanup" Release Notes

AbiWord 2.1.6 "Maple Syrup Chronometer Cleanup" Release Notes

These release notes describe changes, system requirements, installation instructions, known issues, and feedback for AbiWord 2.1.6. These release notes are updated when we receive feedback, so feel free to check back for new information.

What's New
  • Somewhere over 70 bug fixes. 'Nuf said. Well, for a more detailed report of changes, albeit not at all exhaustive, see the 2.1.6 changelog.
  • Wrapping of text about objects!
System Requirements
  • AbiWord is fast and lean, leaving a very small footprint despite its wonderful features. It does not take much to run this word processor.
  • Detailed system requirements are available at http://www.abisource.com/support/require/
  • Installation varies from platform to platform, you probably know how to go about it for yours. If you have trouble, see the help pages.
  • There is also help in the source distribution if you choose to build from source. See abi/docs/build/BUILD.TXT.
  • Downloads may be found at http://sourceforge.net/project/showfiles.php?group_id=15518.
  • Additionally, many flavors of Unix or Unix-like environments carry AbiWord or have it in their ports collection or a package repository.
Known Issues
  • There is a performance issue on OSX described in bug 6881. Its effect is limited to OSX, and does not appear in 2.1.1, which is still available (see bug).
  • Printing from the command line on Windows appears to be broken in 2.1.x. It works in 2.0.x, but we still have not found the fix for this.
  • While many bug fixes have been made, many bugs remain (particularly with those features only recently developed), and therefore this release is not recommended for production environments. However, careful testing and extensive use of bugzilla.abisource.com are encouraged.
  • To request a feature or suggest an idea, see http://www.abisource.com/contribute/suggest/
  • For support, see http://www.abisource.com/support/
  • We cannot stress enough that while we want to find and fix bugs, duplicate reports only slow us down and divide resources. Please check for prior reports and add your comments there.
  • We love CONSTRUCTIVE feedback. Be friendly, appropriate, and patient. It always helps to counter pointing out a problem by pointing out something you like. Developers will be much more eager to help.
How to Contribute