|
Hmm I think the second part of my statement was a bit ambiguous.
The fact that you can put spaces at the start or end of a directory is only relevant if you use some kind of zip tool for your conversion. These tools usually work by creating a zip that mirror your directory layout - and thus your invalid META-INF dir in the case of the "dumb" zip tool. More "intelligent" tools that are specifically geared for ebook creation (i've seen a window frontend flying around here somewhere, though i've no experience with it) should detect that error and warn the user. And in the former case those errors are easily detected anyway.
However most end users won't create the ebook layout themselves but let backend tools do the work (Illustrator, calibre, whatchamacalit). Meaning that the creation of the zip file and its content is in the hand of the generator software - and if something goes wrong at that part it doesn't really matter with which operation system you're working. A bug is a bug is a bug...
That being said: as i mentioned earlier the space makes the container entry a different one than the expected entry. It doesn't matter whether you put a space or an underscore or a love letter in it - it differs from the spec so if that was your intended container entry then it's missing. Apart from those two files you're pretty free to use any naming convention you prefer. And if those are to put spaces around your filename.... then by all means do just that - they're valid entries.
|