build identifier: i20100319-1449

===== description =====
corruption when export report data
==== 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): 	turkish


===== 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 data dialog, select region
8. click other for output encoding, and input iso-8859-9. click ok button
9. open the saved file

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

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

reproducible: always
created an attachment (id=163219)
screenshot on turkish on redhat5.4
created an attachment (id=163220)
flat_file_csv.rptdesign
created an attachment (id=163221)
sales_csv.csv
alternatively, we have also tried ibm-857, windows-1254, but none of them works.
hi,

could any one give us an update?

many thanks
it seems viewer doesn't support iso-8859-9 encoding when exporting.
(in reply to comment #6)
> it seems viewer doesn't support iso-8859-9 encoding when exporting.

hi gang,

please advice which encoding should be used when exporting data.

many thanks
hi, could we kindly get an update for the status on this bug?

many thanks in advance.

- steven.
it is better to use utf-8 encoding.
hi, the test cases which we are running specifies we select the codepage of the local encoding.  in this case we should select the turkish encoding. iso-8859-9 should be correct for the local turkish encoding, and therefore we should see turkish text without corruption.  

selecting utf-8 is not really the local encoding.  we should be selecting iso-8859-9 for turkish, but when we do so, we see corruption, there it suggests a functional issue perhaps.

we tried other codepage selections for other locales (such as chinese,japanese) and they work.  

please could you advise and have this bug investigated.  many thanks in advance.

- steven
in a terminal, what is the output of the command 'locale'

does it work with you start gedit as follow, in a terminal type:

lang=tr_tr.iso88599 && gedit

it is possible tr_tr.iso88599 is not the right name in your machine, if that is the case try 'locale -a | grep tr_tr', that will show all turkish encodings available in your machine.
created an attachment (id=163979)
turkish text is displayed correctly in csv file.

hi, the default locale was indeed set to tr_tr.utf-8, therefore calling gedit as it is will display the csv file with corruption, since it was exported by birt as iso-88599-9 codepage.

we tried calling lang=tr_tr.iso88599 && gedit <filename> and the turkish nlv text now displays correctly.  please see attached screenshot.

many thanks.  closing this bug.
closing this bug as invalid, since it was due to environment setup issue.

thanks.

- steven.