Page tree
Skip to end of metadata
Go to start of metadata

Hyacinth can import and export UTF-8 encoded CSV files, and there are a few things to watch out for when using various CSV editing programs.

GOOD programs (which work well for importing or exporting Hyacinth CSV files):

GOOD Program


Google Sheets

BAD programs (which have known issues and should not be used for importing or exporting CSV files):

BAD ProgramReasons to avoid
OpenOfficeImporting a CSV into OpenOffice, the program will read in certain dates (e.g. 1968-04-29) and prepend a single quote before the date. This single quote is sometimes exported when you re-save the CSV, and other times we've seen that dates are converted to a different format (e.g. slash format instead of iso8601 dash format).
Microsoft Excel

You should never export a UTF-8 encoded Hyacinth CSV file from Microsoft Excel because the program doesn't encode UTF-8 properly.

You should also never open and work with a Hyacinth-exported CSV file in Microsoft Excel because the program doesn't decode UTF-8 properly.

Microsoft Excel irreparably corrupts cell data in spreadsheets. We most often see this with cells containing accented or foreign characters.

If you have existing data in a Microsoft Excel file (.xls, .xlsx), the only way to safely convert it to UTF-8 for Hyacinth is to open that file using one of the above-mentioned GOOD programs (LibreOffice or OpenRefine), and to export to UTF-8 CSV from that program.

If for some reason you must convert a Hyacinth-exported CSV to a Microsoft Excel file, you can open the CSV file in one of the above-mentioned GOOD programs (LibreOffice or OpenRefine) and export it as a Microsoft Excel file.

  • No labels