Issue 89988 - GDI Metafile VCLMTF seems to be rendered with the default fallback font
Summary: GDI Metafile VCLMTF seems to be rendered with the default fallback font
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 3.0 Beta
Hardware: Unknown Windows, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2008-05-27 02:33 UTC by tora3
Modified: 2017-05-20 11:35 UTC (History)
6 users (show)

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

Snapshots that illustrates the phenomenon (201.22 KB, application/vnd.oasis.opendocument.presentation)
2008-05-27 02:59 UTC, tora3
no flags Details
A bugdoc (15.57 KB, application/vnd.oasis.opendocument.presentation)
2008-05-27 03:00 UTC, tora3
no flags Details
Snapshot with DEV300_m14 on Windows 2000 Japanese (109.97 KB, image/png)
2008-05-28 12:06 UTC, tora3
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description tora3 2008-05-27 02:33:19 UTC
 1. Start Impress of 3.0.0 Beta on Linux.
 2. Insert a graph.
 3. Set a font name to Japanese Gothic variant one.
 4. Save the document into .odp file.
 5. Start Impress of 3.0.0 Beta on Windows.
 6. Load the .odp file.
 7. Verify what type of font is used for rendering texts.

    Apparently, texts in the graph are rendered with Mincho variant font. 
    It looks like the default fallback font of Windows 2000 Japanese. 

 8. Double-click on the graph to enter edit mode.

    All of a sudden, the glyphs of text get changed from Mincho variant to 
    Gothic one.

 See the attachment file that illustrates the phenomenon.

    Fedora 8
    /usr/sbin/getenforce: Permissive

    Windows 2000 Japanese

Quick Investigation
 1. Unzip the .odp file

    |-- Configurations2
    |   |-- accelerator
    |   |   `-- current.xml
    |   |-- floater
    |   |-- images
    |   |   `-- Bitmaps
    |   |-- menubar
    |   |-- popupmenu
    |   |-- progressbar
    |   |-- statusbar
    |   `-- toolbar
    |-- META-INF
    |   `-- manifest.xml
    |-- Object 1
    |   |-- content.xml
    |   |-- meta.xml
    |   `-- styles.xml
    |-- ObjectReplacements
    |   `-- Object 1
    |-- Thumbnails
    |   `-- thumbnail.png
    |-- content.xml
    |-- meta.xml
    |-- mimetype
    |-- settings.xml
    `-- styles.xml

 2. Delete ObjectReplacements/Object 1 and ObjectReplacements.
 3. Delete corresponding entries from META-INF/manifest.xml.
 4. Zip those files to create an experimental .odp file.
 5. Load it with 3.0.0 Beta on Windows.

    As expected, the text in the graph are rendered with Gothic variant font.

 ObjectReplacements/Object 1 seems to contain the font names specified on 
 Linux, encoded in code page 932. It seems good. The Windows, however, seems 
 not to recognize the names of the font given in the embedded GDI Metafile. 

 This phenomenon is originally reported by t-otsuki [1] in the BBS of Japanese 
 build project and is confirmed by curvirgo [2].

Comment 1 tora3 2008-05-27 02:59:15 UTC
Created attachment 53960 [details]
Snapshots that illustrates the phenomenon
Comment 2 tora3 2008-05-27 03:00:31 UTC
Created attachment 53961 [details]
A bugdoc
Comment 3 tora3 2008-05-27 03:11:25 UTC
 Texts in the embedded GDI Metafile should be rendered with appropriate, given
Comment 4 philipp.lohmann 2008-05-27 09:43:23 UTC
pl->hdu: please have a look
Comment 5 2008-05-28 09:51:18 UTC
This reminds me of chart issue 85934 (chart hardcoded a font name) which was fixed in CWS chart23 in 
versions>=DEV300_m6 (i.e. after the beta). With DEV300_m14 it looks good to me.

@iha: can you confirm that it has the same root cause as issue 85934? Else I'd need to reassign it.

@tora: can you check and confirm with something >=DEV300_m6

*** This issue has been marked as a duplicate of 85934 ***
Comment 6 tora3 2008-05-28 12:05:00 UTC
@hdu: Thank you for prompt consideration. 

I also thought the same thing that the fix related to the font issue in 
the module chart2 had been done in the cws chart23. I confirmed carefully if the 
fix had been already included in 3.0.0 Beta aka BEA300_m2 before filing this.

According to the Release Notes of 3.0.0 Beta [1],
 - Sources can be received from cvs by tag BEA300_m2.
 - It lists cws chart23 in the section Integrated Child Workspaces.

According to the EIS, 
 - BEA300's parent is DEV300_m10.
 - chart23 has been incorporated in DEV300_m6.

From those facts, this phenomenon happens under circumstances where the cws 
chart23 has been already incorporated. 


With DEV300_m14, this phenomenon can be also observed.
Comment 7 tora3 2008-05-28 12:06:08 UTC
Created attachment 54020 [details]
Snapshot with DEV300_m14 on Windows 2000 Japanese
Comment 8 2008-09-10 11:15:30 UTC
this doesn't seem to be a duplicate of issue 85934 then
Comment 9 2008-09-10 11:17:49 UTC
@iha: chart's edit mode seems to do funny things to fontnames
Comment 10 IngridvdM 2008-09-10 11:48:52 UTC
@hdu: As I understand this issue, the chart edit mode does render the font
correctly. It is the meta file that is not rendered correctly.
Comment 11 Marcus 2017-05-20 11:35:09 UTC
Reset assigne to the default "".