This is the correct answer. There's no need for UTF-16 unless you're fixing up code that uses UCS-2. UTF-32 doesn't buy you anything other than bloat. In all

This is the correct answer. There's no need for UTF-16 unless you're fixing up code that uses UCS-2. UTF-32 doesn't buy you anything other than bloat. In all cases you have to deal with graphemes that consist of multiple codepoints, so even UTF-32 is a sort of variable length encoding, which is why it buys you nothing but bloat. UTF-8 is reasonably easy to deal with and very interoperable.