Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | linetype other then continous get EPS exported without width | ||||||
---|---|---|---|---|---|---|---|
Product: | Draw | Reporter: | cvogelbusch <christoph> | ||||
Component: | code | Assignee: | AOO issues mailing list <issues> | ||||
Status: | ACCEPTED --- | QA Contact: | |||||
Severity: | Trivial | ||||||
Priority: | P3 | CC: | clement.raievsky, issues, mikael | ||||
Version: | OOo 1.1 Beta2 | ||||||
Target Milestone: | AOO Later | ||||||
Hardware: | PC | ||||||
OS: | Windows 98 | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
cvogelbusch
2003-08-25 07:57:04 UTC
Set to new. This is reproducible in a current internal version, too. Reassigned to Sven. Please have a look. Created attachment 8714 [details]
The reproduction did not work as I expected, so here is the example that has problems getting exported. (it contains german letters)
changed owner, set target to OOo 2.0 again assigning the owner. Cannot currently reproduce. Will check back with Wolfram. Ah, got it now. Well, the problem is that our EPS export tries to use native PostScript primitives whereever possible. Thus, in the case of hairlines, and for solid lines of any thickness, we simply use PostScript strokes. Unfortunately, for dashed lines, this can lead to flawed output for thick lines. Therefore, we generate polygonal output in these cases, but since our polygons are integer-based internally, the line thickness is rounded to the next integer (which, in this case, was obviously zero). I could evaluate whether it's possible to clamp the stroke width for native PostScript strokes to those integer values, too. Okay, will see what's possible for OOo2.0 here. In principle, some processing steps for thick line generation are already floating point, should be possible to somehow get that data to the EPS exporter. - "According to the OpenOffice.org roadmap (http://tools.openoffice.org/releases) this issue was retargeted to OOo Later." *** Issue 21590 has been marked as a duplicate of this issue. *** *** Issue 44747 has been marked as a duplicate of this issue. *** *** Issue 76721 has been marked as a duplicate of this issue. *** *** Issue 80189 has been marked as a duplicate of this issue. *** Still there in 2.4.0 Reset to default bug assignee. |