how to automatize routine modifications to epubs?

[Terisa de morgan]

Originally Posted by Rev. Bob

I am unfortunately not running from source; depending on the machine, I'm running either a Portable build or the Win64 compile. Any idea what file that module ends up in?

I think as pyc file (compiled python) inside pylib.zip.

[BetterRed]

@Rev. Bob - why don't you ask Kovid if the titlepage.xhtml code could be exposed in the install resources folder, then it could be overridden in the configuration resources folder - a'la jackets.

BR

[Rev. Bob]

Originally Posted by BetterRed

@Rev. Bob - why don't you ask Kovid if the titlepage.xhtml code could be exposed in the install resources folder, then it could be overridden in the configuration resources folder - a'la jackets.

Probably not a bad idea. From what I see, it wouldn't take much to add an "if override file found, use it, else use this" logic to the current source, although validating the override file would add some overhead. A straight-up "use this file as the template" flow would be more direct, but then there's the problem of what to do if the file is missing or corrupt. Leaving a known-valid version in the script avoids that kind of issue.

[sbin]

Sorry to backtrack a little, but here's another little question: would it be possible to automagically remove the starting point from the <guide> in the opf?
Searches/replaces made with the calibre converter only work within the html and css files.


(Why publishers want me to skip the maps, the epigraphs and all the front matters is beyond me… )

[JSWolf]

Originally Posted by sbin

Sorry to backtrack a little, but here's another little question: would it be possible to automagically remove the starting point from the <guide> in the opf?
Searches/replaces made with the calibre converter only work within the html and css files.


(Why publishers want me to skip the maps, the epigraphs and all the front matters is beyond me… )

That's only an issue if you are using a Kindle. ePub does not use the guide. Kindles are just odd. They don't start at the cover and if you have no guide, they can start at some seeming random place.

[sbin]

Originally Posted by JSWolf

That's only an issue if you are using a Kindle. ePub does not use the guide. Kindles are just odd. They don't start at the cover and if you have no guide, they can start at some seeming random place.

I'm using a Kobo Aura One and it does use the guide with epubs.
Having to go back every time I started a book drove me crazy, so I added "removing that single line from the opf" to my list of fixes. If I could get calibre to do it for me would be great

[JSWolf]

Originally Posted by sbin

I'm using a Kobo Aura One and it does use the guide with epubs.
Having to go back every time I started a book drove me crazy, so I added "removing that single line from the opf" to my list of fixes. If I could get calibre to do it for me would be great

I do remove the guide entries. I find no need for them. I do this using the Calibre eBook editor.

I'll have to leave them in and see if there is a problem.

[BetterRed]

Originally Posted by Rev. Bob

. . .but then there's the problem of what to do if the file is missing or corrupt. Leaving a known-valid version in the script avoids that kind of issue.

At some stage the onus of responsibility for shooting oneself in the foot has to he laid at the feet of the person holding the gun

In other words if your override (code, image, whatever) is garbage then it's up to you to clean up the resultant mess - see Alice's Restaurant Massacree

BR

[jackie_w]

Originally Posted by sbin

I'm using a Kobo Aura One and it does use the guide with epubs.
Having to go back every time I started a book drove me crazy, so I added "removing that single line from the opf" to my list of fixes. If I could get calibre to do it for me would be great

I don't think epubs use the <guide> section. If your Kobo is opening a new book at something other than the page 1 Cover page, it's much more likely that its ToC (the toc.ncx file) doesn't include an entry for the Cover page. Kobos open new books to the first entry in the ToC ncx - don't ask me why?

I can't remember whether this is true for both epub and kepub or just one of them.

[Rev. Bob]

Originally Posted by BetterRed

@Rev. Bob - why don't you ask Kovid if the titlepage.xhtml code could be exposed in the install resources folder, then it could be overridden in the configuration resources folder - a'la jackets.

Well, that didn't pan out. I may look into running calibre in dev mode so I can mod the file myself, but it's a question of whether that's going to be more trouble than it's worth.

[BetterRed]

@Rev. Bob - I solve my issue with titlepage.xhtml with the Modify PI, by removing them, along with all non DC metadata Maybe you could do what you want in the Modify plugin, which you now 'more or less' own.

BR

[JSWolf]

Originally Posted by jackie_w

I don't think epubs use the <guide> section. If your Kobo is opening a new book at something other than the page 1 Cover page, it's much more likely that its ToC (the toc.ncx file) doesn't include an entry for the Cover page. Kobos open new books to the first entry in the ToC ncx - don't ask me why?

I can't remember whether this is true for both epub and kepub or just one of them.

Good point. I forgot about that. I make sure to have the cover as the first entry in the ToC. In most cases, it already is.

[sbin]

Originally Posted by jackie_w

Kobos open new books to the first entry in the ToC ncx - don't ask me why?

You're right

Well, now I have to switch from "deleting a line from the <guide>" to "adding an entry in the toc"

[JSWolf]

Originally Posted by sbin

You're right

Well, now I have to switch from "deleting a line from the <guide>" to "adding an entry in the toc"

It's very easy to do using the Calibre eBook editor.

[sbin]

Originally Posted by JSWolf

It's very easy to do using the Calibre eBook editor.

Yes, I know.
But it'd be nice to have a just-push-a-button solution that could do al my fixes at once. I'm just lazy like that