Unlike UTF-16, which uses 2 byte code units without a fixed endianess (meaning to be robust you need to account for both little and big endian encodings when reading files using it), UTF-8 uses a 1 byte code unit and thus doesn't have any endian issues or a need for a byte order mark.
On Fri, Nov 15, 2019, 1:15 PM Jose Isaias Cabrera <jic...@outlook.com> wrote: > > Shawn Wagner, on Friday, November 15, 2019 04:01 PM, wrote... > > > > If you're on Windows, which cp1252 suggests, just make sure that you > don't > > end up with a BOM at the start of the file when you convert it. Windows > > tools that output utf-8 are sometimes prone to add one even though it's > > pointless to have. > > Why do you think it's pointless? > > josé > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
