Open PortAudio-admin opened 12 years ago
Comment by @RossBencina
TRAC migration: propagating ticket status from TRAC
This can be closed now
@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?
Would be also nice for API documentation to reflect this.
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:
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:
OS support code: