You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have had an issue reported where the CSV export for the REF2 report opened up in Excel, but did not correctly represent some UTF-8 characters in a title for an eprint. Confusingly, the CSV opened up in notepad looked just fine. Apparently this is a known issue in Excel and has been discussed here: https://stackoverflow.com/questions/39086988/setting-bom-to-unicode-u-code-utf8-perl
In the function output_list() in REF_CSV.pm I added this line:
print"\N{BOM}";
... just before the headers are rendered. This seemed to cure the issue with Excel 2016 at least. I thought it would be worth raising here in case you wanted to incorporate the same fix.
Thanks
Liam
The text was updated successfully, but these errors were encountered:
Hi,
I have had an issue reported where the CSV export for the REF2 report opened up in Excel, but did not correctly represent some UTF-8 characters in a title for an eprint. Confusingly, the CSV opened up in notepad looked just fine. Apparently this is a known issue in Excel and has been discussed here: https://stackoverflow.com/questions/39086988/setting-bom-to-unicode-u-code-utf8-perl
In the function output_list() in REF_CSV.pm I added this line:
... just before the headers are rendered. This seemed to cure the issue with Excel 2016 at least. I thought it would be worth raising here in case you wanted to incorporate the same fix.
Thanks
Liam
The text was updated successfully, but these errors were encountered: