Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Encoding in the XLS export | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Encoding in the XLS export

Encoding in the XLS export

Posted: August 31, 2012 at 4:16 pm

Viewing 1 reply thread


Jano Costard

August 31, 2012 at 4:16 pm

At the moment, when exporting the attendee list into the XLS file, German characters such as “ä2” are displayed wrong. Is there a bugfix to display the characters correctly?


Dean

  • Support Staff

    •

September 3, 2012 at 1:25 am

Hello Jano,

I tried a little fix (adding the UTF-8 headers to the export code if you’re interested) but it didn’t work.

I have filed a bug report to the developers.

However, there is a workaround (tested with Excel 2010). Download the xls file. Open the xls file in Notepad, copy and paste it into a new Excel workbook.

I didn’t need to do anything it all went into columns fine, but if needed, highlight the text in the spreadsheet and go to Date tab, text to columns.

This was tested with Scandinavian characters (äöå) but I assume it will be the same for German ones.
Viewing 1 reply thread

The support post ‘Encoding in the XLS export’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

The original Forum description...

Status: closed

Updated by Dean 12 years, 4 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: resolved
Event Espresso - Staging Server