Sigil Nuisance Message "Files exist ...."

[DNSB]

Originally Posted by JSWolf

My problem is that a lot of the books I do want to read need fixing. So I go in to fix them. Most are not too bad under the hood. But any made with Vellum are terrible under the hood.

Whereas I find that while Vellum's CSS looks like crap, it takes relatively minor changes to clean it up though I will admit to having a copy of Vellum's media.css with all the media queries relevant to Amazon removed entirely and the remainder with the media query section removed and a simple body/p/.subsq change that are a copy/paste away.

This still leaves the ghods forsaken strings of divs but since they don't have much effect on the main text of the document, I really don't care about them. More precisely, my wife doesn't care about them.

[rkomar]

Originally Posted by st_albert

...At the time, I just wrote a script file to handle it so I wouldn't have to think about it. Now, I've lost the script file.

It takes two steps: first, add the uncompressed mimetype file to a new zip file, then add the rest of the files in compressed format to that zip file (omitting the mimetype file). Something like:

zip my-epub-file -0 mimetype
zip -r my-epub-file * -x mimetype

[JSWolf]

Originally Posted by DNSB

Whereas I find that while Vellum's CSS looks like crap, it takes relatively minor changes to clean it up though I will admit to having a copy of Vellum's media.css with all the media queries relevant to Amazon removed entirely and the remainder with the media query section removed and a simple body/p/.subsq change that are a copy/paste away.

This still leaves the ghods forsaken strings of divs but since they don't have much effect on the main text of the document, I really don't care about them. More precisely, my wife doesn't care about them.

I'll dump the empty div and span. I use Diap's Editing Toolbag to do it.

Depending on the book, I'll take a scroll trough HTML to see how it looks in the preview. Usually it's OK and sometimes a few fixes here and there.

[JSWolf]

Originally Posted by rkomar

It takes two steps: first, add the uncompressed mimetype file to a new zip file, then add the rest of the files in compressed format to that zip file (omitting the mimetype file). Something like:

zip my-epub-file -0 mimetype
zip -r my-epub-file * -x mimetype

Or just load the ePub into Calibre's editor or Sigil and save and it should be fixed.

[rkomar]

It never hurts to know what is going on under the hood.

[DiapDealer]

Originally Posted by rkomar

It never hurts to know what is going on under the hood.

No, it does not.

[CubGeek]

Originally Posted by DiapDealer

No, it does not.

So.... how do those <i> and <em> tags work again?



....flees

[CubGeek]

Okay, I just got bit by this phantom iTunesMetadata.plist message. This is on an EPUB3 that I created from scratch in Sigil, and I have not loaded this book into iTunes to test yet (but I did a different book). this is weird.

[Martinoptic]

In my experience if you put an epub in books(iOS) you automatically get an iTunesMetadata.plist file put into your epub. But if you’ve created your epub in Sigil and not gone near iTunes or iOS then I’m stumped.
Are you using Mac, windows or Linux ?

[CubGeek]

Never mind. I just opened my iPad and it seems I must have loaded the book last night because voila! there it is (PSA: don't ebook distracted, kids!). My apologies.