build identifier: i20100319-1449

===== description =====
corruption in report when previewing in pdf format
==== environment =====
build level: 		i20100319-1449 
component: 		birt
platform: 		redhat5.4
jre: 			jre-1_5_0_22-windows-i586-p.exe (sun java 5)
affected locale(s): 	schinese


===== steps to reproduce =====
1. open new project dialog from eclipse file menu, select business intelligence and reporting tools, and click next.
2. type any project name on report project dialog and click finish. open associated perspective dialog is displayed. 
    click yes to display birt perspective.
3. on navigator view, right click the project and select import, select file system, and select the flat_file_csv.rptdesign. then, click finish.
4. double click the flat_file_csv.rptdesign on navigator view. the report design is displayed. 
5. double click the data source and set the “select folder” to the path where sales_csv.csv has been copied.
6. preview the report in web viewer from run->view report->in web viewer
7. open export report dialog, select pdf for export format. click ok. then, click open the file

===== expected result =====
the text should be displayed correctly without corruption

===== actual result =====
the text are corrupted.

reproducible: always
created an attachment (id=163376)
schinese on redhat5.4
created an attachment (id=163377)
flat_file_csv.rptdesign
created an attachment (id=163378)
sales_csv.csv
please go to fontsconfig_pdf.xml,
find <composite-font name="all-fonts">
<font font-family="msung-light" catalog="chinese" />, replace msung-light with stsong-light for simplified chinese characters.

you can also divide catalog "chinese" into two subset as "tchinese"and "schinese",
define <font font-family="msung-light" catalog="tchinese" />
<font font-family="stsong-light" catalog="schinese" />

and then define the search-sequence distinguished by locale "zh_cn" and "zh_tw" in fontsconfig.xml.
we have reopened 307329 for tracking.  we still see an issue when we modified the fonts config file.  require further advice from developer.

closing this bug and using 307329 for tracking.

- steven.