View Single Post
Old 06-05-2017, 02:23 PM   #30
Gregg Bell
Gregg Bell
Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.
 
Gregg Bell's Avatar
 
Posts: 2,068
Karma: 3741360
Join Date: Jan 2013
Location: Itasca, Illinois
Device: Kindle Touch Sony PRS300
Quote:
Originally Posted by Hitch View Post
Yes, that's what I'm saying, IF the new material actually has the doctype declaration, etc. The example you showed us, above/earlier, didn't have that, which is what flipped me out. But there's no reason not to go to the new material, CTRL+A (select all, or, whatever you're copying), then go to the new ePUB, CTRL+A (select all in the new "empty"-ish HTML file) and then CTRL+V, paste.
Thanks Hitch. So your way overwrites what's there in the xml stuff? I can do that. But what if the xml stuff in the old epub is old? Maybe the epub check will tell me?


Quote:
Originally Posted by Hitch View Post

Well, for one thing...didn't you just have a catastrophic failure, with doing it your way? Why keep doing that, given what occurred? How do you know that deleting everything in that file wasn't what caused it?
I'll do it your way from now on.

Quote:
Originally Posted by Hitch View Post
My philosophy is always somewhat medical: first do no harm. If you leave the doctype, etc., in the newly-created HTML file, and replace it with identical coding, in theory, there'd be less chance for it to crash
But your way overwrites the xml coding at the top. Again, what if the xml coding in the new .epub doc is different than what was in the old epub? I'd be overwriting old code into the new .epub.

Quote:
Originally Posted by Hitch View Post
Yes, well, that's the only way that I can see for you to have lost the prior-saved file on the disk. Otherwise, this makes NO sense at all. For future reference, in case you didn't already get this from all the other guys, if you get the PSO'D (Pink Screen O'Death), or anything bizarro-world, like that, EXIT. Don't bloody well save.
Gotcha.

Quote:
Originally Posted by Hitch View Post
I suppose. You know, you could also simply unzip the ePUBs, and use the "insert existing file" functionality,
Is that the same as "Add Existing Files" when you right click on a file? (I couldn't find "insert existing file.")

Quote:
Originally Posted by Hitch View Post
to add the "leave a review" HTML file from one ePUB to another. Working in ePUB parts is also good experience. Instead of that copy-paste stuff. Since you don't do this stuff all day long, make a COPY of the ePUBs that you're going to unzip, etc. (n.b.: we do this all day long, run RAIDS, plus do all our work on Dropbox [another level of backup], plus version everything, plus run nightly backups, plus run full weekly backups), and we still make copies of any files we'll be working on or using. If we do, you probably really ought.

Good luck.

Hitch

Thanks Hitch. I usually do good backing up. This was just kind of a perfect storm sort of thing.

I can do the unzip thing, but really your first suggestion (your way of copying and pasting) will save time as I can see what's in the files. As long as that works I think I'll do it that way.

I really appreciate the help.
Gregg Bell is offline   Reply With Quote