Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Special characters in DROID report #1132

Open
allieg82 opened this issue Oct 8, 2024 · 3 comments
Open

Special characters in DROID report #1132

allieg82 opened this issue Oct 8, 2024 · 3 comments

Comments

@allieg82
Copy link

allieg82 commented Oct 8, 2024

Hi,

I am getting the following characters in my DROID report export (UTF 8 encoding selected) – ’ � in place of some, but not all, of the ' ' – and sometimes spaces in my file titles. They appear correct in the GUI view

Can anyone assist me in figuring out why this is happening so I can fix it - or suggest a work around?

Thanks
A

image

image

@kathaurielle
Copy link

Hello, just to add, I tried this with the file names and WAS able to replicate it. I think we last saw this issue many years ago and fixed it manually ie by changing file names and csvs, but wonder if devs have a better fix. reports are exported as UTF-8. Kathryn.

@DavidUnderdown
Copy link

It will depend what the CSV file is being opened in. Excel still assumes everything uses the Windows encoding set in the locale so will misinterpret some characters (it looks like UTF em dashes are one thing being got wrong), and it's extremely hard to tell it to use a different encoding. If you open in LibreOffice instead where you can control the encoding used it will probably show everything fine if UTF-8 is selected at launch.

@ross-spencer
Copy link

If you open in LibreOffice instead where you can control the encoding used it will probably show everything fine if UTF-8 is selected at launch.

To add, this does look very much like Excel's mis-handling of this. In Excel you can't open it as a CSV via file->open you need to select one of the other tabs which I believe is import or import data set, then from csv. During the import process you can select the character encoding and it will import "more correctly" <-- I'd say correctly, but Excel is not a suitable tool for digital preservation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants