View Single Post
Old 12-05-2015, 10:21 PM   #22
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by dgatwood View Post
It is pretty much guaranteed. The string "application/epub+zip" is only 20 bytes long. Using the DEFLATE algorithm more than doubles its length to 42 bytes. No zip tool worth its weight in manure is going to choose to use the DEFLATE output if doing so would more than double the length of the file.
Understood...
But even a zip tool that isn't worth its weight in manure but is technically creating a perfectly valid ZIP, might exist.

Since I would anyway suggest scripting the EPUB zipping (much less typing of exclusions plus various magical incantations, and you can pass a directory + auto-name the EPUB), there is no loss in adding an extra line, and it doesn't really take longer to zip... so why rely on "should"s? It is just generally a bad idea to rely on undocumented assumed (rightly so) behavior, but especially when there is literally no downside to being extra careful!
eschwartz is offline   Reply With Quote