The issue is with internal content files having non-UTF-8 encodings and accented (or otherwise "extended") characters. The recent upload should fix that, look for it in a calibre update sometime in the next couple hours.
The issue is with internal content files having non-UTF-8 encodings and accented (or otherwise "extended") characters. The recent upload should fix that, look for it in a calibre update sometime in the next couple hours.