On 2/28/17, Scott Robison <sc...@casaderobison.com> wrote:
>
> The SQLite database storing the repository is UTF-8, or blobs in the
> database are using UTF-8 encoded data that won't be transparently
> transcoded by SQLite?
>

Neither.  The problem is that the Fossil implementation sometimes
accesses string values using sqlite3_column_blob().  That works fine
as long as the database encoding is UTF8, but falls down badly when
the database encoding is UTF16.

This isn't all that hard to fix.  The main challenge is finding every
instance where it occurs.  And I have bigger fish to fry at the
moment.
-- 
D. Richard Hipp
d...@sqlite.org
_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev

Reply via email to