Hi Arne,
okay, this is an interesting fact. Thanks for the info, I really did not have any idea why one would like to explicitely use decomposed UTF-8 strings. We encountered a problem with our new plug-in internal preset management system, we currently develop. The problem was that when a user created a preset with some meta information, for example Author: “Andreas Schröder”, on a Windows system and afterwards created some new presets on Mac also with the same author name, the preset management system was unable to match the string “Andreas Schröder” created on the Windows system with the same string on Mac. So, finally, the preset management system handled both versions of “Andreas Schröder” like two different authors. This was only the case, because the ö was precomposed on Windows and decomposed on Mac. But we need a platform independent handling of UTF-8 strings to ensure that typing the same word always yields the same encoding, which is now given since we switched to precomposed strings on Mac.
I hope this clarifies our issue.
Regards,
Joscha