That error typically can be generated deep inside the python library code when unicode data is passed between threads but somehow the default python encoding is used and on some platforms this is ascii which causes an error. I thought all of those were fixed in the very latest version of KindleUnpack. Perhaps not. Or perhaps some full unicode data is used in a filename or book title or link target, that should have been properly converted to utf-8 before being written to the opf. Either way please post a zip archive of the problem news feed ebook and I will try to track down what is happening and get it fixed.
Last edited by KevinH; 03-16-2013 at 11:29 PM.
Reason: fix typos