[GUI Plugin] Modify ePub

[Perkin]

Just looked at source of this PI and I think you could hi-jack the smarten-punctuation function, in modify.py - line 497 calls the smarten routine for each of the raw html files, so if you called a 'span-trim' function instead, that should manage it.

Edit: Backup your existing PI, and any testing epubs beforehand.

[Rev. Bob]

Originally Posted by Perkin

Just looked at source of this PI and I think you could hi-jack the smarten-punctuation function, in modify.py - line 497 calls the smarten routine for each of the raw html files, so if you called a 'span-trim' function instead, that should manage it.

Edit: Backup your existing PI, and any testing epubs beforehand.

I'm not seeing that file...where did you find it?

[Perkin]

Inside the 'modify epub.zip' - the actual plugin.

Unzip
Edit/modify.
re-zip.
Test
repeat

[Perkin]

@Rev. Bob
This is a modified 'modify epub' plugin that contains the changes.
Please note that I haven't tested it as I haven't got a file that needs modifying.
Backup your original 'modify epub.zip', then replace with this version.
run the modify epub plugin on required file ONLY with 'smarten punctuation' option set, it will do the strip-spans instead.

Check output.

When needed, restore original plugin.

N.B. THIS IS A MODIFIED VERSION OF THE PLUGIN, DO NOT USE UNLESS YOU HAVE READ THE THREAD AND SEEN WHAT THIS DOES.

[Rev. Bob]

Originally Posted by Perkin

Inside the 'modify epub.zip' - the actual plugin.

...which I can't bloody find.

Yes, I know there's a copy of the ZIP in the first post of this thread. I'm saying that I installed it through Calibre's interface, and I can't find where Calibre stashed it. Obviously it's installed, but for the life of me I can't see where it's installed.

[eschwartz]

Originally Posted by Rev. Bob

...which I can't bloody find.

Yes, I know there's a copy of the ZIP in the first post of this thread. I'm saying that I installed it through Calibre's interface, and I can't find where Calibre stashed it. Obviously it's installed, but for the life of me I can't see where it's installed.

Preferences ==> Advanced ==> Miscellaneous

Open calibre configuration directory.

But I'd assume the copy at the beginning of this thread works just as well.

[Rev. Bob]

Originally Posted by eschwartz

Preferences ==> Advanced ==> Miscellaneous

Open calibre configuration directory.

No wonder I couldn't find it - why the hell is it in AppData/Roaming?

And as for why I was hunting for the installed version - I'd kinda like to be able to strip spans and smarten punctuation at the same time, should a book need it, so I'd prefer to find a way to expand the feature set. Maybe I can, now that I know where everything is...

[eschwartz]

Originally Posted by Rev. Bob

No wonder I couldn't find it - why the hell is it in AppData/Roaming?

And as for why I was hunting for the installed version - I'd kinda like to be able to strip spans and smarten punctuation at the same time, should a book need it, so I'd prefer to find a way to expand the feature set. Maybe I can, now that I know where everything is...

Where else would it be? Roaming IIRC is for most appdata besides for caches, to facilitate network domains in business usage.

Also, if you load the (modified) plugin through preferences, it should overwrite/update the current copy. So you could d/l from this thread, update/modify, and reinstall.

[Perkin]

Originally Posted by Rev. Bob

No wonder I couldn't find it - why the hell is it in AppData/Roaming?

It likes to stretch it's legs once in a while

You would need to add another option to the options pane, and then duplicate the smarten option function code, rewriting to do the strip spans instead.

Can you test to see if that stripping works?

Then we'll see about adding the extra option and associated code.

[BetterRed]

Originally Posted by Rev. Bob

No wonder I couldn't find it - why the hell is it in AppData/Roaming?

Because that's where optional PI's and most other configurable data is stored - keeps the install location (Program Files) pristine - some config data is kept in library databases

If you want to put config data elsewhere then see CALIBRE_CONFIG_DIRECTORY at http://manual.calibre-ebook.com/cust...ment-variables

BR

[Rev. Bob]

Originally Posted by eschwartz

Where else would it be? Roaming IIRC is for most appdata besides for caches, to facilitate network domains in business usage.

Hardly the case here...

Originally Posted by Perkin

You would need to add another option to the options pane, and then duplicate the smarten option function code, rewriting to do the strip spans instead.

Way ahead of ya; I've pretty much got that done, but I'm running some test cases to fine-tune things. Mods so far:

- remove_drm_meta_tags now removes the trailing newline as well, so the Adobe line completely goes away instead of leaving a blank line.
- "Smartify punctuation" routine restored.
- New code renamed "strip_spans" and available through the --strip_spans command line option.
- strip_spans expanded to remove "rights.xml" and "kobo.js" - both remnants of the Kobo DRM scheme - from the book and manifest.
- strip_spans expanded to remove the koboSpan CSS rule and references to kobo.js from the (X)HTML files.
- Basic documentation for the new code added to the HTML file.
- Version number bumped to 1.3.10 to avoid any confusion, although 1.3.9b would be more accurate.

In short, strip_spans is now more like a "deKoboify" routine that also happens to remove SPAN elements that have no attributes. I'm almost tempted to split it properly, into strip_spans and dekobo, but I don't really see the point. (Any opinions either way?)

If anyone wants to try to poke holes in the code, the current version is attached. I think I've got it properly bulletproofed, but testing is more than welcome.

EDIT: Code revised after further testing.

[Rev. Bob]

Originally Posted by BetterRed

Because that's where optional PI's and most other configurable data is stored - keeps the install location (Program Files) pristine - some config data is kept in library databases

I was wondering why it was in Roaming as opposed to, say, Local (where I looked first).

[Perkin]

Originally Posted by Rev. Bob

In short, strip_spans is now more like a "deKoboify" routine that also happens to remove SPAN elements that have no attributes. I'm almost tempted to split it properly, into strip_spans and dekobo, but I don't really see the point. (Any opinions either way?)

I'd have them separate, somebody may want to keep the kobo stuff, yet remove the empty spans.
I don't know who, but you never know, there's bound to be someone.

[BetterRed]

Originally Posted by Rev. Bob

I was wondering why it was in Roaming as opposed to, say, Local (where I looked first).

See http://windows.microsoft.com/en-us/w...appdata-folder

Like many things in Windows, Roaming is also about corporate environments. That's a major source of revenue for MS, corporates pay annual support/license fees, which in part at least, subsidize things like the 13 years of free upgrades for XP that consumers enjoy(ed).

BR

[eschwartz]

Originally Posted by Rev. Bob

I was wondering why it was in Roaming as opposed to, say, Local (where I looked first).

Originally Posted by BetterRed

See http://windows.microsoft.com/en-us/w...appdata-folder

Like many things in Windows, Roaming is also about corporate environments. That's a major source of revenue for MS, corporates pay annual support/license fees, which in part at least, subsidize things like the 13 years of free upgrades for XP that consumers enjoy(ed).

BR

Like I thought. Basically, even though AppData really should just have, well, app data, MS set up a system to segregate data depending on whether it should be synced from computer to computer (for busines users who tend to use networked login domains). This save the trouble of syncing Local\ data which has no compelling need (like the cache) to save on network usage.
Important stuff goes into the Roaming folder, including al config-type data.

And since it is default, it happens even if you don't use a network domain.