Ya, but that's not what one would call "working normally" str.charAt should just work, Utf8.whatever should only work on things which are explicitly utf8 (normal Haxe string nowadays are not). I will get to that (or I'll just bug Hugh about it).

str.charAt should work, will look into that. Utf8.whatever is only properly working after you used Utf8.encode I think. Maybe. No idea if the thing is up to date at all, docs still talk about iso strings, whatever that might be.

Wait a minute, that isn't even supposed to work. In hxcpp fancy strings are now utf16 so Utf8.charCodeAt isn't the right thing to use in your sample.

Aha. That's likely because I activated smart_strings in hxcpp (aka unicode support) which isn't much tested yet. Will have a look tonight. That "bug fix" only takes action when writing a file.

No, that in general doesn't work at all. g2 uses g4 if it's available so when you take a look at the g2 implementation you can carefully mix it with g4 but in most situation this will mess things up - in particular if you call g4.begin instead of g2.begin.

That's a bug I think. GitHub issue please.

I updated everything to the latest Android Studio things and that fixed it by itself without me having to define char16_t again. Please test.

ok, that looks straight forward enough, looking forward to the pull request.

Oh, sounds complicated. Some sources I can look at hidden somewhere?

My fault, cleaned up a bit in my hxcpp fork yesterday and didn't yet test on all targets.