Community
Participate
Working Groups
attempting to export a report to csv file, creates a file with utf-8 encoding. opening said file directly with excel xp results in gibbrish of the hebrew fields. this bug prevents me from using excel export in birt only way to correct this is open notepad select all contened open ANOTHER notepad (do no select file->new) paste it and save the file.
BIRT do not create the xls file directly, it is the browser that imports the csv into xls. Could it be a browser setting? Need to investigate.
(In reply to comment #1) > BIRT do not create the xls file directly, it is the browser that imports the > csv into xls. Could it be a browser setting? Need to investigate. the browser does not import csv to xls, it simply launches excel with csv filename in it's command line. attempting to view it in total commander lister also results in gibbrish. the csv files are being exported as UTF-8, this is what i was told the forum, however excel does not handle UTF-8 with non-western chars very well as per this post http://groups.google.com/group/microsoft.public.excel.misc/msg/7ad2b1a98f8ce760 and others the possible solutions they way i see it, are locale dependent 1. detect according to the browser setting the user's locale and change the file encoding. 2. allow the encoding to be specfied in configuration of xml 3. allow me a chance to trap the contents (an event of some sort) of the file before it's sent to browser so i would change it, maybe create an interface i can implement or something similar, in the rptdesign file
Gary, Please check out this link - http://groups.google.com/group/microsoft.public.excel.misc/msg/7ad2b1a98f8ce760 Any issue with encoding the data extraction CSV stream in other encoding?
change to enhancement to support exporting CSV file in user's locale instead of UTF-8.
seems that we have support it.
In BIRT 2.3.1 the export data dialog has a free text field where you can type the encoding name to use for the CSV file. This way is maybe not so convenient, so here is a suggestion of what we could improve: 1. Add a combobox list in the export data dialog to be able to select an encoding from a defined list. 2. The list from that combobox will be defined in viewer.properties 3. A default encoding for the export can be specified in viewer.properties, so that this one will be selected by default in the export dialog, and also used by default when no encoding is specified in the URL (for URL-mode export)
Too late to change UI in 2.5.0. Set plan keyword for future viewer UI enhancement.
