Quote:
Originally Posted by AZed
I'm not aware of any failures, but I haven't tested specifically for this issue. Can you link to the other thread, or provide access to a file that decodes incorrectly with other software so I can test it?
|
Most Feedbooks.com .mobi ebooks have this issue since they use UTF-8 encoding. Check
this post for the beginning of the discussions regarding this issue. The solution is now documented in our wiki
here .
I've included this fix in my Mobi2IMP, but still find the odd (poorly created?) UTF-8 ebooks that still don't find the exact filepos location for the <a href>'s anchor (<a name> or <a id>).