Hawaiian, along with English, is an official language of the US state of Hawaiʻi.

https://www2.hawaii.edu/~rtoyama/pubs/diacritics.html

Hawaiian Diacritical Marks and Other Special Characters

You can insert special characters into a web page by typing an ampersand, a number or letter sequence, and a semicolon.

These are the codes for rendering diacritical marks in Hawaiian words:

• ʻ — ʻokina or glottal stop

• Ā — Ā

• ā — ā

• Ē — Ē

• ē — ē

• Ī — Ī

• ī — ī

• Ō — Ō

• ō — ō

• Ū — Ū

• ū — ū

Other frequently used codes:

• & — ampersand (because the ampersand is an "escape character", this is the safest way to display an actual ampersand)

• – — n-width dash

• — — m-width dash

• ¢ — ¢

•   — non-breaking space (used between words you don't want separated at line breaks)

A Note on Accessibility: The ʻokina is known to throw off screen reading programs that read out text for blind people. To address this, University of Hawaiʻi Office of Communications recommends using the aria-label attribute within a span tag to supply the word (without diacrical marks) to the screen reader.

  <span aria-label="Hawaii">Hawai&#699;i</span>

+1 on allowing different file formats on imports - mac based shop here TY!!

And, as I forgot to mention it, there's always the Terminal way:

iconv -t UTF-8 {blackbaud export CSV file} > {new CSV file}

UTF-8 is for direct Mac > Excel import (without using the Text Import Wizard); if you have a solution that uses another encoding, specify that encoding. If you need a listing, use iconv --list to see how to specify that encoding to iconv -t.

As an aside for this (and seeing as how this has languished for 6 years now):

Blackbaud's observed encoding (because of course they don't document it or anything) is ISO-8859-1.

It is, however, not very difficult to change encodings. Tedious and unnecessary, perhaps, but not difficult.

FOR IMPORTS TO BLACKBAUD

In Windows:

1. Open your CSV file in Notepad, which will automatically detect the correct encoding, unlike Excel);

2. Select "File > Save as..."

3. At the bottom, where the "Encoding" drop down is, select "ANSI" (this is Microsoft's ISO-8859-1, and seems close enough to be usable)

4. Either save over the existing file or enter a new name, make sure your File Type is "All Files", include your .CSV extension and save it as a new file

5. Upload to Blackbaud for import (and hope they haven't changed the format or messed it up in a novel fashion)

In macOS:

1. Open Terminal

2. Run the following command:
   iconv -t ISO-8859-1 {your CSV filename and path} > {new CSV filename and path}

3. Upload to Blackbaud for import (and hope they haven't changed the format or messed it up in a novel fashion)

FOR BLACKBAUD EXPORTS

On a Windows system, you shouldn't have to do anything; Blackbaud's standard encoding should work just fine.

If you want to import into Google Sheets, Blackbaud's standard encoding also works...because Google Sheets checks the encoding of the file before importing it.

On a macOS system, Numbers will also auto-detect the encoding properly.

With Excel for Mac:

1. Open an empty spreadsheet file

2. Select "File > Import"

3. Select "CSV", then click "Import"

4. Locate and double-click the Blackbaud export file

5. At "Text Import Wizard - Step 1 of 3", select "File origin: Windows (ANSI), then click Next
   NOTE: Western (ISO Latin 1) or Western (Windows Latin 1) will also work; however, "Macintosh" will NOT...and of course it can't auto-detect.

6. At "Text Import Wizard - Step 2 of 3", select "Delimiters: Comma and click Finish OR click Next and make any additional changes in "Text Import Wizard - Step 3 of 3", then click Finish