Issue 12391 - Provide true bezier clipping support or fake it where impossible
Summary: Provide true bezier clipping support or fake it where impossible
Status: ACCEPTED
Alias: None
Product: Draw
Classification: Application
Component: code (show other issues)
Version: 644
Hardware: PC Linux, all
: P3 Trivial with 2 votes (vote)
Target Milestone: AOO Later
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-16 13:45 UTC by behrends
Modified: 2013-02-07 22:17 UTC (History)
1 user (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
.tar.gz file with example files. (35.60 KB, application/octet-stream)
2003-03-26 15:35 UTC, behrends
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description behrends 2003-03-16 13:45:47 UTC
When converting curves to polygons, the approximation is fairly poor due to too
few interpolation points, and visible to the naked eye. This is a problem
especially when exporting to EPS, where circles and ellipses obtain a visibly
jagged look.
Comment 1 wolframgarten 2003-03-26 15:11:58 UTC
I have tested this in current version 1.0.2 and had no problems. Would
it be possible to attach a screenshot and a document where the problem
is visible?
Thanks in advance.
Comment 2 behrends 2003-03-26 15:33:56 UTC
Please see the attachment. It includes a .sxd file of an ellipse
converted to a polygon (created with OOo 1.1beta), a .png screenshot,
and a .pdf file obtained by printing the converted ellipose to a PDF
converter (Aladdin Ghostscript 8.00). Most critical is that the
jaggedness of the conversion is visible when printing to a printer.

I'm happy to observe that Export to EPS doesn't seem to implicitly
convert curves to polygons anymore in the 1.1 beta (Export to WMF
still does). However, various other functions do (the shape functions
for good reasons, but Connect and Combine inexplicably convert curves
to polygons, too), so the printing quality should be solid (or at
least settable).
Comment 3 behrends 2003-03-26 15:35:06 UTC
Created attachment 5244 [details]
.tar.gz file with example files.
Comment 4 wolframgarten 2003-04-01 09:34:37 UTC
Set to new.
Comment 5 wolframgarten 2003-04-01 09:35:37 UTC
Reassigned to Armin. This is reproduceable in version 1.0.2 and in a
current internal one. Please have a look if there is something to be
done about this . Thanks.
Comment 6 Armin Le Grand 2003-04-01 11:40:36 UTC
AW->THB: This seems to be a candidate for OOo 2.0 or OOo later. We 
are working on overhauling all the curve handling (and have started 
in some parts for 1.1).
Comment 7 thb 2003-04-01 12:30:14 UTC
This bug has various aspects, I'll try to explain them one by one (please add anything I 
might have missed):

1. Shape conversion to polygon always yields a line 
polygon
2. Some export filter convert even polygons containing beziers to line 
polygons
3. Polygon-polygon munging always results in line polygons

Item 1 is 
maybe a problem of terminology. The term "Polygon" at the UI level implies line 
polygon. If one converts an ellipse to "Curve", beziers are preserved. 
Nevertheless, a "Curve" is a polygon just the same, and can be used with 
Combine/Connect/whatever.

Item 2 is based on the fact that formats like WMF 
simply do not support curves at all. If you encounter exporters whose target format 
does provide curves (like EPS or EMF), please file a bug then.

Item 3 is the real bug 
(or missing feature, as I prefer to call it), as you cannot currently perform the shape 
algebra with true curves. As Armin said, this is a planned feature for 2.0, we'll have 
to have a working bezier clipping algorithm for that.
Comment 8 behrends 2003-05-19 18:23:03 UTC
Actually, while all that additional functionality would be nice, my
main concern (and why I labeled it as a defect, and not an enhancement
request) is that if I _want_ to convert a curve to a polygon (and I
mean a polygon, and not a sequence of bezier segments), the
approximation is poor. The underlying problem seems to be that
conversion (whether to polygons, or to bitmaps) occurs based on screen
resolution, and not based on any resolution that you want to print at.
Comment 9 thb 2003-09-12 18:35:35 UTC
-
Comment 10 marc.neumann 2003-10-16 08:51:19 UTC
"According to the OpenOffice.org roadmap
(http://tools.openoffice.org/releases) this issue was retargeted to
OOo Later."
Comment 11 thb 2012-07-13 20:47:55 UTC
Reset to default bug assignee.