Issue 101836 - Importing EMF File leads to polygons in wrong position and missing text
Summary: Importing EMF File leads to polygons in wrong position and missing text
Status: CONFIRMED
Alias: None
Product: Draw
Classification: Application
Component: code (show other issues)
Version: OOo 3.1 RC2
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-12 17:00 UTC by carlo47
Modified: 2013-01-29 21:39 UTC (History)
2 users (show)

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

Attachments
Zip with sample emf-file (11.00 KB, application/x-compressed)
2009-05-12 17:04 UTC, carlo47 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description carlo47 2009-05-12 17:00:22 UTC 
Trying to import an image in emf-format with some polygons (squares of
Pythagoras), a coordinate system and several labels shows the following defects:
1) The polygons are positioned in the wrong way (lines are vertical and
horizontal instead of rotated)
2) All text labels are missing

This happens in Writer as well as in Calc and with Windows XP as well as Mac OS
10.5.
Comment 1 carlo47 2009-05-12 17:04:51 UTC 
Created attachment 62206 [details]
Zip with sample emf-file
Comment 2 eric.savary 2009-05-12 20:27:13 UTC 
@AW: already known? One for the meta issue 79743?
Comment 3 Armin Le Grand 2009-06-03 17:16:03 UTC 
AW: Need to take a look, adding to aw073...
Comment 4 Armin Le Grand 2009-06-16 15:27:46 UTC 
AW->SJ: One more bad MetaFile visualisation (maybe import). When breaking up the
imported object, things look a lot better, but not perfect. The rectangles seem
to be wrong. When taking a closer look, each rectangle consits of three filled
polygons on top of each other; one of them being the rotated one. Looks like the
import does not look at e.g. set ClipRegin when converting/importing?
Please also find out if it's a case for the MetaIssue #i79743#.