Support UTF-16 CSV files as a merge source
Brought to you by:
evins
CSV files are just text files. They can be stored as wide chars e.g. UTF-16, and so gLabels should support these encoding formats as well as its usual 8-bit formats such as UTF-8 or iso-8859-1. However, if I point gLabels at a UTF-16 file, it fails to convert the text properly (though does not actually reject the file).
This came up recently because exporting contacts from GMail is now being done as UTF-16, apparently. In order to use the file, I found I first had to convert it to UTF-8 after which gLabels was quite happy with it. I chose the Google csv format. The Outlook format is apparently still UTF-8.