[Koha-bugs] [Bug 33635] New: CSV export display broken diacritics in Excel

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33635

            Bug ID: 33635
           Summary: CSV export display broken diacritics in Excel
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5 - low
         Component: Staff interface
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: katrin.fischer at bsz-bw.de
        QA Contact: testopia at bugs.koha-community.org
                CC: clemens.tubach at kit.edu, gmcharlt at gmail.com,
                    michaela.sieber at kit.edu

This has been a re-occurring support issue:

When using one of Koha's many CSV download options, the exported CSV file
doesn't open as UTF-8 in Excel, resulting in broken diacritics. LibreOffice
doesn't show the issue.

The only way to fix it right now is not to open the file directly, but to use
the import functionality in Excel as it lets you pick the encoding and
separators. This means a lot of extra steps and clicks, which make the CSV
export functionalities in Koha hard to use.

It turns out that Excel will import the CSV correctly, if we convert the
encoding of the exported CSV file from UTF-8 to UTF-8-BOM.

Problematic CSV exports include:

* Exporting a basket summary page as CSV
* Using CSV profile based exports in general, including: lists, basket, lost
items report
* ...

Can we 'fix' the encoding to use BOM?

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.