Hello,
J.M. Maurer wrote:
The libwpd dev team is basically only me, william and fridrich, and we
are all here! :)
This information is actually much more important than adding to the
comments on Groklaw concerning OOo, WP import and export [or the lack of
it]. We are three working on libwpd [the core of almost all opensource
import filters] in our spare time. Although we are committed to give the
best of ourselves, the fact that we are just human beings creates a
clear limit. The use of libwpd by OOo 2.0 will drastically decrease the
developper/user ratio of libwpd and one will have to set priorities and
filter the requests according to them.
fridrich is gone indeed iirc, ... and I just back from holiday... :(
/me back from holiday too, although I will need some time to get used to
normal life. BTW: pleased to see that fs01 and fs02 were integrated in
m118. It means that OOo 2.0 will surely use libwpd-0.8.2 with all the
nice stuff in extended charset to unicode mappings.
If you think it is a libwpd bug, then please file it at
http://bugzilla.abisource.com/enter_bug.cgi?product=libwpd
which is the official libwpd bugzilla. I never look in OOo´s bugzilla,
so any bugs filed there will not be seen by me (i think fridrich watches
it though)
This is very true, Marc. Nevertheless, from my experience, the
bug-reporting is not very simple activity for a normal user and I would
like to make it as simple as possible for users and developpers.
Moreover, I would be surprised if a normal user knew how to distinguish
between libwpd and writerperfect issue.
If you want to see the issues filed with OOo "wp" component, it is
enough to subscribe [EMAIL PROTECTED] It is very low-traffic
(except some proposals of remedies for enlarging certain parts of human
body from time to time :-)). It will also simplify the integration work
after 2.0 is released, since every CWS based on a milestone of a
production release has to have an agreement of "gatekeeper" before
integration and the argument that it solves a bunch of issues from OOo's
IssueZilla is a powerful argument indeed.
As for the reporter of the bug. It is necessary to file ONE BUG REPORT
PER BUG. With test documents and good description, naturally. For
reports with many issues inside, it is very likely that eventual fixes
of some of them will not be integrated untill ALL the other are fixed as
well.
marbux, please file issues from your e-mail according to Smokey's
suggestion. I am trying to push through a refactoring of libwpd that
should fix quite some of them.
I think I wrote enough for now.
Cheers
Fridrich
--
Please avoid sending me Word, Excel or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
