Comment 75 for bug 244353

As I said before, vanilla OOo do not show the problem. Only way to test if this fix the problem is to have a Novell build based on that vanilla build, and I don't have access to it now. Correct me if I'm wrong, but I think the "unstable" OOo branch for Novell build is based on OOO320_mX (X = 4 now) while the linked issue is solved for OOo 3.3, that is OOO300_mY with Y > 60