The export (CSV) function is terrific! Just what I needed, so easy to set up... many thanks!
Just one problem though, I'm not even sure that it is possible to do anything about this.
All content in Drupal is held in UTF-8 format and if you don't work in English (I work in French) then the chances are you will have some "non-Latin" characters in your output. But when you produce a CSV export file it is in Latin-1 (ISO8859-1) by default. If I open the file in OpenOffice then this is not too bad since OO prompts for the format and then remembers the last format I used. However if I download to Excel this option is not available apparently and all the non-Latin characters are displayed incorrectly. Is there any way around this?

Comments

druvision’s picture

druvision commented

As a bypass, I've succeeded to open such a file with Hebrew UTF-8 data in my OpenOffice 2.0.4 spreadsheet program - it asks for the encoding during the CSV file open process.

Then, I've saved the file to Excel.

There were only a few glitches, seemingly when there are quotes inside the data, but the Hebrew went OK.

Amnon
-
Professional: Drupal Israel | Drupal Development & Consulting | Eco-Healing | Effective Hosting Strategies | בניית אתרים
Personal: Hitech Dolphin: Regain Simple Joy :)

martink’s picture

martink commented

I have had the same experience. The only drawback is it means that my users MUST have OpenOffice installed which is far from being the case always. Also, strangely, I discovered that OpenOffice on Ubuntu seems to "remember" that I asked for UTF-8 the last time, but on Windows it forgets so that on Windows the user must make the same choice of UTF-8 each time.

kingandy’s picture

kingandy
he/him
commented

I've come across this myself and there seem to be a few others - there's a fix suggested on #167537: UTF8 - diacritical marks (umlaute) (presented as both a hack and a theme-level workaround).

pomliane’s picture

pomliane commented
Status: Active » Closed (won't fix)

This version of Views Bonus Pack is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.

This issue has been automagically closed by a script.