PortAudio should use UTF8 for character encoding of public API strings

[PortAudio-admin]

Issue created by @RossBencina

After some discussion with Rob we concluded that strings passed in PortAudio public APIs should encode multibyte characters (device names etc) as UTF-8.

PortAudio implementations may store strings internally however they like.

This applies to:

• device names
• native error messages

Relevant strings can originate from host API implementations, and from platform-specific common code. As of now, the following APIs definitely return UTF8 strings. The others I'm unsure of. Please discuss below.

Host API code:

• [ ] alsa
• [ ] asihpi
• [ ] asio
• [ ] audioio
• [ ] coreaudio
• [x] dsound
• [ ] jack
• [ ] oss
• [ ] wasapi
• [ ] wdmks
• [x] wmme

OS support code:

• [ ] unix
• [ ] win
• [ ] mac

[PortAudio-admin]

Comment by @RossBencina

TRAC migration: propagating ticket status from TRAC

[jmelas]

This can be closed now

[RossBencina]

@jmelas Before closing I'd like to be sure that the issue is resolved for all host APIs. I've added a checklist to the head of this ticket. Aside from DSound and MME do you know with confidence which other host APIs are correctly returning UTF8 strings?

[arkadijs]

Would be also nice for API documentation to reflect this.