Can you share a snippet or a link where the problem with encoding can be checked ?
As for the issue in the Safari, I can confirm it. Safari doesn’t allow to define the file name for client side file downloads. This is limitation of the browser ( which actually must be already resolved in latest tech preview of Safari )
There is no beautiful workaround for the issue. As a temporary solution, It is possible to place a simple mirror script on a server, which will reflect the data from the client-side export, along with a valid file name.
In your snippet, you are using HTML-entity, not a UTF character.
Check the updated snippet, here the real Unicode char is used, and it is correctly included in the export file.
It is possible to redefine the templates for each column during export to ms-excel, but it is not convenient, as you need to hardcode which columns will be exported and all their properties.