Should I be defining both of these symbols for full compatibility with foreign-language OSes? Currently I define only JUCE_STRINGS_ARE_UNICODE.
I notice that juce_launchFile() calls ShellExecute instead of ShellExecuteW, regardless of the fact that JUCE_STRINGS_ARE_UNICODE is defined. Is this intentional? We use this to launch external viewers, and I suspect that this could fail on multibyte systems.
We also use File::loadFileAsData(), which seems to use wchar_t all the way through, and that operation is failing for our Japanese tester as well. Any ideas what could be going wrong? Is there any way to test and debug multibyte support, without switching my system to a language I don’t speak?