View Single Post
Old 04-27-2013, 04:19 PM   #124
AcidWeb
KCC Co-Author
AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.AcidWeb ought to be getting tired of karma fortunes by now.
 
AcidWeb's Avatar
 
Posts: 845
Karma: 765434
Join Date: Mar 2013
Location: Poland
Device: Kindle Oasis 2
Quote:
Originally Posted by Sorenant View Post
Downloaded AWKCC 1.6.
At first it failed to create .epub but after some experimentation it run smoothly. It seems you forgot (or maybe it's intentional) to put the following files on the .zip: _ctypes.pyd, _hashlib.pyd, _imagin.pyd, _socket.pyd and _ssl.pyd.

By the way, what do you mean by "Improved handling of UTF-8 characters"? Running 1.5 on folders with japanese names it used to create .mobi with 'broken' metadata(文字化け) so I thought it would now create proper metadata but it seems like it just rejects folders with non-latin characters. Is it right?
That files are in ZIP file :-P

Yes. It is only cleaning file and directory names. Dirty workaround for Windows Python 2.x UTF-8 support. It will be fixed properly when KCC will be rewriten to Python 3.x.
AcidWeb is offline   Reply With Quote