To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=105655
------- Additional comments from [email protected] Thu Oct 8 07:03:55 +0000 2009 ------- Ok. So right off, there's no easy way. I first noticed that the shadows for fontwork type (d) consist of quite a few separate polygons; disabling that shadow though does not help - _every_ other object on the page needs to be considered, too; so the ~200k actions really count here. And that's because calculating those axis-aligned connected components is a _wicked_ problem. It would be much easier to calculate polygonal areas, which we deliberately decided against back in the day, as this would have required bitmasks in postscript. The algorithm performs so badly in this case, because for every addition to a connected component region, it's area grows in quite ill-natured ways - it requires checking the new area against _all_ other existing connected components (which can be quite a lot, when you consider the fat line emulation and some intermediate states there). There's likely no way around this, and it's also necessary to check _every_ metaaction, since it's potentially possible that they'll, all together, somehow intersect with a transparent action. Armin, Andre & myself once spent various days pondering this problem. So I have to repeat my analysis - either reduce the input set, or use polygonal regions (would also kill two birds with one stone, in that bit-masked bitmaps would not be a "transparency"-to-be-emulated-case in the first place), or push transparency directly to the printer. I'm sorry. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
