Reply To: Handling UTF/ISO 8859-1 characters in SQLite3

#16930
Anonymous
Inactive

here is an option in firefly that specifies the format. It’s in the advanced preferences, under “Scanning”.

True, but the default is ISO-8859-1 anyway (andI assume that’s Latin-1 too).

I went digging around the trac site and there’s a bug open about this but no progress toward a resolution. The SQLite3 database is getting loaded with the tag information correctly, full character set and all, from the individual media files. I think the problem is coming when Firefly then scans the M3U files, it’s failing to parse the entries with extended set chars: it ends up counting X less items per playlist (X being songs/files with extended set chars). Accordingly, the playlistitems table is then missing the matches between files and playlist item IDs. It’s easy to hack it back together for a dozen or so files.