On 24/10/2020 21:41, HamApps Support (VK3AMA) wrote:
As for the UTF-8 naming issue, I am investigating why that is occurring. The underlying code that retrieves all the audio endpoints defined on the PC fully supports UTF-8. Something is being lost in getting that data over to the main JTAlert executable.
this may not be relevant and your comment above just be using incorrect terminology, but wide-strings in Windows are not utf-8, they are 16-bit characters encoded with utf-16 little-edian Unicode values. You might convert them to multi-byte Unicode strings, utf-8 for example, to send over the network, store in a file, or other space constrained media.