Audio2Csv fails with certain characters in file name

[peichins]

audio2csv fails with the following characters in the file name. Below are the paths that I tried and the log files.

/temp/in/dir_/REC_C_20180616_185529🤷‍♂️🤷‍♂️_1_1.wav to /temp/out/ This failed, here is the log: log_20181102T012216Z.txt

However, I tried it with different characters in the filename, and it worked /temp/in/dir_/REC_C_20180616_185529_1_1.wav to `/temp/out/`` This worked, here is the log: log_20181102T013828Z.txt

And I tried the following (only one of that character): /temp/in/dir_/REC_C_20180616_185529🤷‍♂️_1_1.wav This failed, here is the log: log_20181102T014439Z.txt

• Operating system: MacOS Sierra Mac Pro
• AP.exe version: 18.10.2.6
• The data used can be found: Y:\WesternGhatsCentralIndia\201809\SAT_MANG_3\Recordings\REC_C_001\REC_C_2018-06-16\REC_C_20180616_145526.wav (This was the file that was renamed with the bad character to test #201)
• The command I used: mono AnalysisPrograms.exe -l 7 audio2csv "/temp/in/dir_with_unicode__/REC_C_20180616_185529🤷‍♂️_1_1.wav" "ConfigFiles/Towsey.Acoustic.yml" "/temp/out"
• The config file I used: Towsey.Acoustic.yml that shipped with that release.

Originally posted by @peichins in https://github.com/QutEcoacoustics/audio-analysis/pull/201#issuecomment-435245354

[atruskie]

This is a problem with System.Drawing that occurs while drawing a line. Need to debug further.

We might be able to just bypass fixing this if we stop using System.Drawing - see #158

[atruskie]

Another related but separate problem with the Windows Console is that because GDI is used to render Console’s text, and GDI does not support font-fallback, Console is unable to display glyphs for codepoints that don’t exist in the currently selected font!

https://blogs.msdn.microsoft.com/commandline/2018/11/15/windows-command-line-unicode-and-utf-8-output-text-buffer/