README for aspell-0.60-vc++-*.diff and aspell-0.60-vc++-*.zip This patch and zip file allows Aspell to compile with VC++. The changes were submitted by Gary Setter . This patch also contains a decent number of changes beyond what is required to get Aspell to compile with VC++, not all of which I approve of. As such, I, the author of Aspell do not officially support these changes. If you have problems with the code please contact Gary Setter. However, I am willing to work with somebody to get Aspell to compile with VC++ provided that the changes are broken down into into well defined patches (using the "context" or "unified" format). Each patch should focus on one specific problem. This way I can review the changes on a case by case basis. I am even willing to give someone who will commit time to the port CVS access, provided that they keep their changes on a separate branch, to aid in keeping their changes up to date until the point the official version of Aspell can compile with VC++. Due to a dispute over the behavior of the acommon::String class Gary Setter lost interest in working with me. However he did give me permission to release his changes: The file //home.att.net/~setter/Aspell6.ZIP Copywrite (C) 2004 by Gary Setter, in this document called the SOFTWARE PRODUCT, is a derivative work from Aspell 0.60 Copyright (C) 2001-2004 by Kevin Atkinson. Aspell, being under the GNU LGPL license version 2.0 or 2.1, the SOFTWARE PRODUCT is also under the GNU LGPL license version 2.0 or 2.1. You may receive a copy of the LGPL license at //www.gnu.org/. To the maximum extent permitted by applicable law, Gary Setter expressly disclaims any warranty for the SOFTWARE PRODUCT. The SOFTWARE PRODUCT and any related documentation are provided "as is" without warranty of any kind, either express or implied, including, without limitation, the implied warranties of merchantability or fitness for a particular purpose. The entire risk arising out of use or performance of the SOFTWARE PRODUCT remains with you. ... Note that I have not made any conditions to your use of the Win32 port, you may give me attribution, but you are not required. Kevin Atkinson 2004-11-07