Comment 125 for bug 129403

Any chance of bumping this up to a P2 and/or changing the issue type to a
DEFECT instead? This single issue seems to be a major ongoing irritant for
much of the OOo user base. Also, if it's just an issue of human resources,
perhaps a lead implementor can be appointed and issue a call for developers on
this one. It's been almost 5 years since I did any development/integration
work with OOo -- pretty much because none of the issues I've reported have
been dealt with (I've even given up reporting new defects I've found) -- so
I'd need guidance on what part(s) of the code to chomp on (I've forgotten more
than I ever knew about the code structure), but my offer of assistance remains
open.