C.UTF-8 is not glibc, even few distributions added it (historically Debian and Ubuntu, more recently Fedora).

:(

Though worst case it'll fallback to C which is no worse than where we started.

@ltoscano Do you know of any other solution?

In D7732#144105, @davidedmundson wrote:

:(

Though worst case it'll fallback to C which is no worse than where we started.

@ltoscano Do you know of any other solution?

Pass the locale from the kauth caller? or is it too late to set up LANG at that point?

It's too late*, if we're processing stuff from the user we've already instantiated our qapp and set our locale/test codec.

• It would be possible to do this and then have this helper spawn another helper ... but that gets messy

Then invoke locale -a and get one of the utf locales from there? It sucks but i didn't find a way to do what locale -a does from C[++]

I'm not sure changing the codec for all kauth stuff is the best, but if we're going to do that i think we should add it to the documentation, something like "Forces UTF-8 text codec" or something

I'm not sure changing the codec for all kauth stuff is the best

I did it in just my one helper initially, but in review it was suggested to make it global as it affects everyone. I'm content with either as long as I'm not deadlocked between them.

In D7732#425077, @davidedmundson wrote:

I'm not sure changing the codec for all kauth stuff is the best

I did it in just my one helper initially, but in review it was suggested to make it global as it affects everyone. I'm content with either as long as I'm not deadlocked between them.

Ok, then get whoever told you yo do it for all to review this ;)

LGTM +1
I've dealt with such issues when working on samba-mounter, there we ended up encoding everything as base64 and using QString::fromUtf8 like maniacs.