Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336796 - BIRT 2.6.2 RC2 doesn't apply font mappings defined in fonts*.xml
Summary: BIRT 2.6.2 RC2 doesn't apply font mappings defined in fonts*.xml
Status: RESOLVED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: 2.6.2   Edit
Hardware: PC Windows Vista
: P3 major with 1 vote (vote)
Target Milestone: 3.7.0   Edit
Assignee: Birt-ReportEngine-inbox@eclipse.org CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-10 05:30 EST by Dmitry Balzer CLA
Modified: 2011-05-26 13:32 EDT (History)
2 users (show)

See Also:

Attachments
Instructions with screenshots (103.50 KB, application/msword)
2011-02-10 05:35 EST, Dmitry Balzer CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry Balzer CLA 2011-02-10 05:30:18 EST 
Build Identifier: M20110119-0834

The current RC2 doesn't apply font mappings that are defined in the *.xml files under plugins\org.eclipse.birt.report.engine.fonts_2.6.2.r262_v20110127.
This bug doesn't occur in BIRT 2.6.0.

Reproducible: Always

Steps to Reproduce:
1. Create a report with some elements with Sans Serif font (which is default).
2. Sans Serif is mapped to Arial on Win32 by default. 
3. Preview this report - the font is not Arial.
4. If you change the font mapping, the font won't change when the report is previewed.
Comment 1 Dmitry Balzer CLA 2011-02-10 05:35:00 EST 
Created attachment 188670 [details]
Instructions with screenshots
Comment 2 Dmitry Balzer CLA 2011-02-10 05:36:11 EST 
Please fix this before 2.6.2 goes live
Comment 3 Dmitry Balzer CLA 2011-02-10 06:25:46 EST 
Same issue with 2.6.2Stable build (2_6_2-S20110209)
Comment 4 Xiaoying Gu CLA 2011-02-10 22:13:45 EST 
This is a expected result in 2.6.2 build.
DOC output will use the user specified font rather than the mapping font in 2.6.2.
Comment 5 Dmitry Balzer CLA 2011-02-11 04:52:27 EST 
Can you please elaborate on why this decision has been made?
It will cause reports to have different fonts in PDF and DOC - how is this avoidable then?
Comment 6 Jianchao Li CLA 2011-02-11 05:34:58 EST 
We use the user defined font directly and ignore the font mapping configuration. It is reasonable, because unlike PDF, WORD does not embed fonts. The server side font mapping configuration may be not suitable for the client side. We rely on WORD to convert the font. Unfortunately, the rules by which Word automatically selects substitute fonts are not provided. All the generic fonts are converted into "Times new roman" in my machine. In WORD 2010, the font substitution can be configured through options-> Advanced-> Show document content -> Font Substitution... It can be a workaround.