Issue 9196

Summary: GDI metafile paste fails on fonts where lfCharSet = SYMBOL_CHARSET
Product: Draw Reporter: Unknown <non-migrated>
Component: codeAssignee: Unknown <non-migrated>
Status: CLOSED FIXED QA Contact: issues@graphics <issues>
Severity: Trivial    
Priority: P3 CC: issues
Version: OOo 1.0.1Keywords: oooqa
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
Zipped WMF metafile that includes characters using Wingdings 2
none
The same metafile graphic embedded in a Word 97 DOC file none

Description Unknown 2002-11-12 22:59:34 UTC 
Using either Edit|Paste or Insert|Graphics to insert a GDI metafile object, 
any characters that use a Symbol Encocded font are not properly imported into 
the system. I would guess that only the TypeFace is considered when processing 
the metafile data. When a font is encoded with lfCharSet = SYMBOL_CHARSET, it 
is essential that this value be retained and later used when showing this 
characters in the proper font.

This can be easily reproduced by pasting a metafile that includes symbolic 
characters from a font such as Webdings, Wingdings, or Wingdings2.
Comment 1 Unknown 2002-11-12 23:03:20 UTC 
Created attachment 3577 [details]
Zipped WMF metafile that includes characters using Wingdings 2
Comment 2 Unknown 2002-11-13 06:10:43 UTC 
Created attachment 3579 [details]
The same metafile graphic embedded in a Word 97 DOC file
Comment 3 Unknown 2002-11-13 06:23:29 UTC 
This problem can also be reproduced by simply opening a Word DOC 
file that includes a metafile graphic that uses SYMBOL_CHARSET 
fonts. The behaviour is very consistent in that the SYMBOL_CHARSET 
fonts are never shown correctly.

I spent a little time with the source and note that this is a 
familiar problem. For example, a PowerPoint module 
(svdraw/svdfppt.cxx) has code in it that makes it clear that it used 
to have this same problem.

I was unable to find the exact cause of the problem. I looked over 
svtools/source/filter.vcl/wmf/winwmf.cxx for a little while. I 
gather that this is what loads the GDI metafile data. If this is 
what is used, it seems to correctly load the lfCharSet value. It is 
then translated into eCharSet = RTL_TEXTENCODING_SYMBOL in the 
WinMtfFontStyle constructor. Perhaps someone more familiar with the 
code will know the area that causes the problem...
Comment 4 wolframgarten 2002-11-13 09:22:34 UTC 
Set to new.
Comment 5 wolframgarten 2002-11-13 09:27:04 UTC 
Reproduceable on version1.0.1 but not on an actual internal version.
Reaasigned to Sven. Please have a look.
Comment 6 wolframgarten 2002-11-13 09:35:20 UTC 
Issue type set to enhancement because this is not a bug. Reassigned ot
Falko.
Comment 7 Unknown 2002-11-13 14:09:45 UTC 
>not on an actual internal version

Does this mean it is fixed in internal versions?

>this is not a bug

You and I disagree on what constitutes a bug. Does this problem 
cause the program to crash? No. Is there a defect in version 1.0.1 
when it comes to opening WMF files? Absolutely.

BTW: This problem also happens if you simply File | Open a WMF file 
that uses WingDing (SYMBOL_CHARSET) characters.
Comment 8 Unknown 2003-01-27 11:40:34 UTC 
This bug still exists in version 1.0.2.
Comment 9 falko.tesch 2003-10-15 10:38:50 UTC 
Please check with 1.1
Comment 10 Unknown 2003-10-15 14:15:49 UTC 
Confirmed as FIXED in OO 1.1
Comment 11 ace_dent 2008-05-17 21:49:19 UTC 
The Issue you raised has been marked as 'Resolved' and not updated within the
last 1 year+. I am therefore setting this issue to 'Verified' as the first step
towards Closing it. If you feel this is incorrect, please re-open the issue and
add any comments.

Many thanks,
Andrew
 
Cleaning-up and Closing old Issues
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 12 ace_dent 2008-05-17 23:53:27 UTC 
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew