Issue 9866 - WMF graphic truncated on right
Summary: WMF graphic truncated on right
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC3
Hardware: PC Windows NT
: P4 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: ms_interoperability, oooqa
Depends on:
Blocks:
 
Reported: 2002-12-05 15:45 UTC by Unknown
Modified: 2013-08-07 14:38 UTC (History)
2 users (show)

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


Attachments
Windows metafile (.wmf) that was included in document (4.42 KB, application/octet-stream)
2002-12-05 15:49 UTC, Unknown
no flags Details
Illustrator 10 file that was used to create the .wmf file (179.94 KB, application/octet-stream)
2002-12-05 15:51 UTC, Unknown
no flags Details
word processor file displaying the bug (8.72 KB, application/octet-stream)
2002-12-05 15:52 UTC, Unknown
no flags Details
screenshot (32.34 KB, image/png)
2003-09-30 07:18 UTC, Rainer Bielefeld
no flags Details
screenshot (20.01 KB, image/png)
2003-09-30 07:19 UTC, Rainer Bielefeld
no flags Details
screenshot (16.92 KB, image/png)
2003-09-30 08:07 UTC, Rainer Bielefeld
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-12-05 15:45:32 UTC
When you include a graphic from a Windows metafile (.wmf) sometimes it is 
truncated on the right.  This happens when the rightmost object is piece of 
text.  All you get for the last character, both on screen and when you print, 
is the first (leftmost) column of pixels.  It looks like the right edge of the 
extent is being calculated based on the position of the last character rather 
than (position + width) of the last character.
It's easy to reproduce in a small document (bug1.sxw attached).  The .wmf was 
generated by Adobe Illustrator 10 ("Scope Match.ai" and "Scope Match.wmf" 
attached), with crop marks in Illustrator set beyond where it is being 
truncated.  The printer is a Xerox Document Centre 440/432/420 PS3 with 
PostScript driver version 2.04.08 01.02.22 for NT 4.0.
Interesting - if select the graphic then right-click on it and go into 
graphics, then crop, it displays a thumbnail image with the crop rectangle 
running through the last character.  A partial workaround is to set a negative 
right crop using the crop control; this fixes the printed graphic but not the 
one displayed on screen.
Comment 1 Unknown 2002-12-05 15:49:57 UTC
Created attachment 3922 [details]
Windows metafile (.wmf) that was included in document
Comment 2 Unknown 2002-12-05 15:51:00 UTC
Created attachment 3923 [details]
Illustrator 10 file that was used to create the .wmf file
Comment 3 Unknown 2002-12-05 15:52:26 UTC
Created attachment 3924 [details]
word processor file displaying the bug
Comment 4 Unknown 2002-12-05 20:43:31 UTC
MORE INFO: It is font-sensitive.  The problem occurs with Myriad 
Roman but not with Microsoft Sans Serif.  If you need a copy of my 
system's font files you'll have to tell me where they are (NT 4.0).
Oh, and it doesn't always cut the character off at the first column 
of pixels, sometimes it is farther to the right.
Comment 5 h.ilter 2002-12-09 14:54:02 UTC
This task seems fonts sensitive.
Comment 6 Rainer Bielefeld 2003-09-30 07:18:37 UTC
Created attachment 9818 [details]
screenshot
Comment 7 Rainer Bielefeld 2003-09-30 07:19:04 UTC
Created attachment 9819 [details]
screenshot
Comment 8 Rainer Bielefeld 2003-09-30 07:47:32 UTC
I checked with 1.1RC3 German version WIN98SE: 645m15(Build8669)
[CWS:ooo11rc3]

I can see the problem with the attached example document (pls. see
attached screenshots). To me it seems to be interesting that the
wmf-image looks different in the various applications I tried.

It works more or less if I import the wmf to Corel Draw, export it to
a wmf file and import the new wmf into a OOo document.

I get complete garbage if I save my WORD2000 testfile with the wmf in
it and open it with OOo.

Rainer

Comment 9 Rainer Bielefeld 2003-09-30 08:07:00 UTC
Questions:  
All OS?
More info from a wmf- specialist: why do the images look so different in 
the various applications on my PC (might also have to do with missing
fonts / different standard fonts for the applications?

Rainer
Comment 10 Rainer Bielefeld 2003-09-30 08:07:45 UTC
Created attachment 9822 [details]
screenshot
Comment 11 ulf.stroehler 2003-09-30 11:05:41 UTC
hmm, MS Word 2002 the same as OOo 1.1 on Solaris have cropped the very
last character a bit. On my Linux box there are more characters cropped.
Keeping in mind that WMF graphics are font sensitive, they are just
not suitable for document exchange over different platforms. Why not
exporting to a different (vector) or even pixel based graphics format?
Looks more as an 'Invalid' to me.

us->hdu: regarding the font substitution aspekt in WMF files. My
understanding is that from vcl perspective there is no different
handling of fonts in WMF files than e.g. in regular text files, right?
Thus a font is set as document property and gets substituted by vcl,
if not available on the system. Now, if the graphic boundaries remain
fixed, the text inside the wmf may get cropped. Thus this is more a
limitation of the graphics file format than a bug in OOo, correct?
Pls. close if invalid. Thx.
Comment 12 Rainer Bielefeld 2003-09-30 11:46:43 UTC
I believe Comments From us@openoffice.org 2003-09-30 meet the point
concerning the suitability of WMF for document exchange over different
platforms.

On the other hand it seems, that there might be WORD documents with
WMF-images, which will cause problems for people, who changed from
MS-OFFICE to OOo. So I set keyword "ms_interoperability". Can someone
please check this aspect?

Additionally (as far as I know) the reported problem happened in a
document created with OOo, and I think there should be no limitations
concerning WMF- images. Can someone check whether the image is correct
and in accordance to WMF- specifications?

My experiance is that WMF is not used by so many people, so I reduche
priority to "4"; do you agree?

Reporter, did you create the WMF on the same PC on which you use OOo?


Rainer
Comment 13 Rainer Bielefeld 2003-09-30 11:55:24 UTC
Is there any relation to issue 4258 ?

Rainer
Comment 14 hdu@apache.org 2003-09-30 12:51:50 UTC
HDU->SJ: thank you for volunteering for this issue.
Comment 15 sven.jacobi 2003-09-30 18:36:02 UTC
accepted
Comment 16 sven.jacobi 2004-01-14 13:05:15 UTC
SJ->THB: You are already familiarised with our wmf/emf filter, currently I have
too many issues and too less time, so can you please takeover this issue, thanks.
Comment 17 ace_dent 2008-05-16 02:38:41 UTC
OpenOffice.org Issue Tracker - Feedback Request.

The Issue you raised has the status 'New' pending further action, but has not
been updated within the last 4 years. Please consider re-testing with one of the
latest versions of OOo, as the problem(s) may have already been addressed.
Either use the recent stable version: http://download.openoffice.org/index.html
or consider trying the new OOo 3 BETA (still in testing):
http://download.openoffice.org/3.0beta/
 
Please report back the outcome so this Issue may be Closed or Progressed as
necessary - otherwise it may be Resolved as Invalid in the future. You may also
wish to search for (and note) any duplicates of this Issue that may have
advanced further by checking the Issue Tracker:
http://www.openoffice.org/issues/query.cgi
 
Many thanks,
Andrew
 
Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 18 Rainer Bielefeld 2008-05-16 06:21:40 UTC
I checked with "3.0.0 Beta Multilingual version English UI WIN XP: [300m2
(Build9301)]" and still see the reported effect.
Comment 19 thb 2008-06-27 15:30:27 UTC
@sf: please take this one back.
Comment 20 jackschmidt 2010-09-17 04:04:59 UTC
OOo-dev-3.3.0 (build9519) Impress.

This bug bit me today.  Lost about lost about 20 mm of the right hand side of a
"16-bit placeable WMF".
Comment 21 jackschmidt 2010-09-17 04:21:08 UTC
Hm.  I restarted Impress and the bug is gone.  No wonder this bug is still
unresolved after 8 years.