Hi William, thanks for this. You will be releasing 0.8.7 though. If I find an oasis in this job-searching desert, I will be back alive and kicking. My todo list has a lot of things that can be done without breaking the API. I estimate it to some 12 months of free-time work. The main goal is to bring *all* the parsers to the level of converted features of the WP6 parser.
William Lachance wrote: > After talking a bit with Fridrich this week, I've volunteered to do > the work of making a new release of libwpd this weekend (the big new > feature, as I understand, is enhanced support for earlier versions of > the WordPerfect for Mac). Yeah, there is actually a new file format that we support WP Mac 1.x. What also means that libwpd is supporting to a certain extend probably *all* WP file-formats on the Earth. Concerning the features converted in WP Mac 1.x, we get the font size, the bold, italic (and other underline) properties, we do not get the font face due to a problem I outlined before. In terms of paragraph, we convert the alignment, line spacing and interparagraph space. We also support indents and hanging first line indent, the tab-tables and some other things. We theoretically support headers and footers, although we did not really reverse engineer all the information included in the functions. We also have basic support of foot and endnotes. We basically detect correctly the WP Mac 1.x documents apart those of them that contain only ascii characters and 0x0d. If we supported those ones, all logs on our boxes would be WP Mac 1.x documents. If I recall correctly, there was also a patch of Andrew Ziem removing memory leaks in wpd2foo when the format of the file we give to wpd2foo is not supported. Also we added the tab-table conversion in WP3 parser and fixed in WP6 a case where the WPXTable::makeConsistent function was using bitwise XOR instead of OR. Then in WPXString::WPXString(...), we fixed the incorrect use of bitwise operators instead of logical ones. I do not recall whether it was already in 0.8.6, but we replaced some abusive use of pointers by the use of references. I cannot see much more, since the libwpd-cvs archive is giving me Internal Server Error :-( > My plan is as follows: > 1. Make sure the regression suite still passes (updating it a bit if > necessary). The regression works well, the changes are mainly due to the fact that I forgot to regenerate it with the 0.8.6 release. Valgrind is not having any problem and the callgraphs are correct. libwpd is boringly stable :-) > 2. Update the CHANGES file. > 3. Release updated tarballs (not going to bother with binaries myself > this time: if anyone wants to contribute, they're welcome) I found in spite of everything a moment and I built the win32 binaries. The naming convention is the same like for 0.8.6 release. The wpd2sxw version is only the normal wpd2sxw 0.7.1 statically linked with 0.8.7. The binaries are properly time-stamped with version and build number. So, if the code does not change, these can be the release win32 binaries. Once again, thanks for doing this release. Cheers Fridrich ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Libwpd-devel mailing list Libwpd-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libwpd-devel
