On 26 June 2013 00:37, Mateusz Loskot <[email protected]> wrote: > On 24 June 2013 17:14, Vadim Zeitlin <[email protected]> wrote: > >> So my suggestion would be: >> >> 1. Handle only UTF-8 for multibyte encodings right now and, perhaps, throw >> an error if we can detect that the database uses anything else. >> Formalize this by documenting that std::string used by SOCI is supposed >> to always be in UTF-8. > > Yes and this answers my question from the beginning.
This part is unclear thus controversial. See comments in the issue I opened for the documentation task: https://github.com/SOCI/soci/issues/166 I agree, that if we need to re-encode and source encoding is unknown, we can assume UTF-8, but we should not assume that std::string carries UTF-8 for any purpose always. As Aleksander pointer, we still want to be able to use it as arbitrary bytes container (i.e. binary data). /me 's getting confused :) Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
