On 8 Mar 2014, at 09:42, Torsten Dreyer <Torsten@t3r.de> wrote:

So I can just lay back and assume everything I get from a properties 
getStringValue() is utf-8, at least sooner or later.

I think yes, but if you start pushing Arabic or Chinese strings into properties this way, donít be surprised if you find areas that break, especially if the strings go anywhere near PUI or FNT - e.g., the property inspector :)

BTW, forgot to say in my last email, Expat loads various encodings, and I /think/ (hope) output UTF-8, but it would be worth double-checking that.