Written by James McDonald

September 23, 2015

Just had an issue in glabels when I pointed it at a CSV file one of the fields was missing.

The cause was glabels intelligently determining the CSV encoding to be non-unicode (ISO-8859) and then dutifully skipping the  display of a field with the ? beta  character in it.

Here you can see the file before and after I opened it in TextWrangler and then saved it as UTF-8.

mypc:custom_labels myuser$ file 50025
50025: ISO-8859 text, with very long lines, with no line terminators
mypc:custom_labels myuser$ file 50025.utf8.txt 
50025.utf8.txt: UTF-8 Unicode text, with very long lines, with no line terminators

I also had to re-insert the ? beta character using the mac character map…beta_char_map


Once the file is in UTF-8 format glabels correctly parses and displays the CSV file



So the fix in this case was to check the encoding and convert it to UTF-8


Submit a Comment

Your email address will not be published. Required fields are marked *

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

The reCAPTCHA verification period has expired. Please reload the page.

You May Also Like…

Ubuntu on Hyper-v

It boils town to installing linux-azure # as root or sudo apt-get update apt-get install linux-azure...