Hi DiapDealer's,
Yes, I am never a fan of using titles as file names because of all that nonsense. I will go grab a file name sanitizer routine. Also, I agree with you in changing the base name of the file to match what we do with KF8 to prevent these difficulties in the first place.
Feel free to fix those in KindleUnpack any way you like (as well as any other related changes you need) and I will add them to the next KindleUnpack release to keep things in sync.
Thanks,
KevinH
Quote:
Originally Posted by DiapDealer
@KevinH
Unrelated to (and regardless of) what I decide to do for the newly opened epub's temporary name, I think we need to examine KindleUnpack's file naming methods for mobi-only kindlebooks. We're technically creating invalid OPF/NCX files whenever the original file name has an ampersand in it. Which means I'm, in turn, creating an invalid container.xml file when trying to man-handle KindleUnpack's output into an epub structure with this plugin.
It's either that, or I need to sanitize all filenames with my plugin (when unpacking mobi-only kindlebooks) and replace all references to them in all the KindelUnpack-produced files with those sanitized versions. A thought I don't really relish, needless to say. 
The KF8 portions of Kindlebooks, don't suffer this file naming "problem." |