No `wstring` overloads

[reverofevil]

What about Unicode support?

[SRombauts]

Hi,

The problem is that sqlite3 only have UTF16 support (and only for some APIs) while std::wstring are UTF32 under Linux, so not really portable...

Though adding UTF16 support for Windows is really straightforward if you need it.

Cheers!

[reverofevil]

If I remember correctly, UTFnn differ only on the encoding of code points in the different quantity of different (1/2/4 bytes) code units. So the conversion should be possible with some codecvt magic. Though query preparation etc. do not support Unicode at all, the best we can do is to keep them string.

Probably I could even make a pull request when I get some time as it doesn't seem too scary right now.

[SRombauts]

Ok then, let me know!
Le 22 oct. 2014 22:17, "Polkovnikov Philip" notifications@github.com a
écrit :

If I remember correctly, UTFnn differ only on the encoding of code points
in the different quantity of different (1/2/4 bytes) code units. So the
conversion should be possible with some codecvt magic
http://stackoverflow.com/questions/7232710/convert-between-string-u16string-u32string.
Though query preparation etc. do not support Unicode at all, so the best we
can do is to keep them string.

Probably I could even make a pull request when I get some time as it
doesn't seem too scary right now.

—
Reply to this email directly or view it on GitHub
#33 (comment).