Release Notes: To keep up the long tradition of broken .0 releases, wv2-0.2 refused to compile on gcc 2.95.x. This has been fixed. If you are using gcc 3.x you won't have to update as there are no functional differences.
Release Notes: The target of this release was to have a polished wv2 version for the upcoming KOffice 1.3 final. The most important bugfixes compared to version 0.1.9 are list related. Word 8 compatibility lists are now correctly handled, even if the document doesn't contain any native Word 8 lists. Additionally, the Word 6/7 list CRC sums are correctly calculated. All other changes have insignificant impact for users.
Release Notes: This is the first bugfix release since support for Word 6 and Word 7 documents has been introduced. The list handling for Word 8 files has been fixed, and support for Word 6 and Word 7 style lists has been added. To make wv2 less noisy in production, the configure flag --disable-debug has been added, which disables almost all output. Additionally, wv2 now recovers as much text as possible from documents using undefined characters of the CP12xy codepages.
Release Notes: This release contains a number of bugfixes and clean-ups in the Word 6/7 code. It's suggested to use this version for the upcoming KOffice 1.3 beta 3.
Release Notes: Support for MS Word 6 and MS Word 7 (a.k.a. MS Word 95) documents has been added to the library. Some minor bugs have been fixed.
Release Notes: This version fixes compilation with libgsf-1.8.x and fixes some build system warnings.
Release Notes: "/wv2" was removed from after the include path to avoid header clashes when #including files such as parser.h (libxml2 also has a header named parser.h). A bug in list handling that caused crashes on flaky documents was fixed, and a workaround was added for a different bug in list handling (05_...). The libtool versioning was also fixed.
Release Notes: A bug in the list handling code for Word 8+ in compatibility mode was fixed. A crash which occurred when handling stale field marks has been fixed. (Word doesn't seem to clean up the field marks sometimes.) The table parsing code is now more robust (the correct sub document is restored), so now fields inside tables also work, even if the table rows are parsed after finishing the main body text.