On Fri, Feb 12, 2016 at 8:00 PM, Igor Tandetnik <igor at tandetnik.org> wrote: > On 2/12/2016 10:44 PM, J Decker wrote: >> >> On Fri, Feb 12, 2016 at 7:37 PM, Igor Tandetnik <igor at tandetnik.org> >> wrote: >>> >>> It performs the conversion it is documented to perform. It indeed doesn't >>> perform the conversion that you, for reasons unclear, expect it to >>> perform. >>> In other words, you engage in wishful thinking, and then blame the >>> messenger >>> for failure of your wishes to materialize. >> >> >> I expect it to take any string > > > What is the basis of this expectation, other than wishful thinking? I don't think expectation and wishful thinknig have anything to do with each other.
Though I expect standards would look at what the world really needs and implement core functionality? That's hardly wishful thinking. Well I guess it is, because I repeatedly have found myself disappointed in the lack of considerations in standards. Yes there are even unicode libraries for posix; but it's a huge expense for a couple hundred lines of code. and if it's something I needed for interop, why doesn't everyone? > > Again, if you need to convert specifically between UTF-16 and UTF-8, there > are API functions that are documented to do that, and they do work. They are > WideCharToMultiByte and MultiByteToWideChar. wcstombs and mbstowcs are not > documented to do that, and, quite unsurprisingly, they don't work for that. > > -- > Igor Tandetnik > > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
