>On 4/18/17, Hick Gunter <h...@scigames.at> wrote: >> I don't see any calls to sqlite3() functions in your "isolated test case". >> Maybe you are having problems with character encoding outside of sqlite? > >I think the OP is referring to a problem that comes up because the field width >and precision of a printf() format are measured in bytes, not characters, and >if the input is multi-byte UTF then it is possible for a single character to >>be cut in half, resulting in goofy output. > >I checked in a fix for this yesterday. See >https://www.sqlite.org/src/timeline?c=f508aff8 >
Damn UTF8 ... my "favorite" error is a data source defined as having ISO encoding actually containing (2 byte) UTF8 characters, which, after calling iconv() ISO->UTF8, yield invalid codepoints (2 x 2 bytes) that produce goofy output on terminals and cause mysterious crashes within XML parsers, preferably called from within perl procedures that silently terminate without any indication of the cause. ___________________________________________ Gunter Hick Software Engineer Scientific Games International GmbH FN 157284 a, HG Wien Klitschgasse 2-4, A-1130 Vienna, Austria Tel: +43 1 80100 0 E-Mail: h...@scigames.at This communication (including any attachments) is intended for the use of the intended recipient(s) only and may contain information that is confidential, privileged or legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication. Thank you for your cooperation. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
