07-31-2014, 12:39 AM | #796 | |
Grand Sorcerer
Posts: 24,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
Good luck with the surgery. |
|
07-31-2014, 10:03 AM | #797 |
Resident Curmudgeon
Posts: 73,983
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
|
07-31-2014, 11:27 PM | #798 | |
Wizard
Posts: 1,759
Karma: 30063305
Join Date: Dec 2006
Location: Singapore
Device: Boyue
|
Quote:
|
|
08-01-2014, 01:39 AM | #799 |
Wizard
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
|
Okay, the time for bug reports and comments has officially run out; I'm getting ready to shut the computer down and get some sleep before cuttin' time happens. The code is now locked; the attached version is what I'm sending to kiwidude for ratification as an official update. (It shouldn't be any different from the last beta, but this way it's unambiguous.)
EDIT, 8/13: When I posted this, I hadn't realized that v1.13.10 had been released a couple of days earlier. The only change that I can quickly identify is that 1.13.10 adds qt5 compatibility, looking forward to Calibre 2.0. That means that the 8/1 code's version number needs to be updated to 1.13.11, which I've now done. I've also added v1.13.10 to the changelog and, since I was in there anyway, tinkered with unpretty a little bit to improve its results in certain uncommon cases (tables, primarily). The 8/1 version was fine, but this one's a shade better. Last edited by Rev. Bob; 08-13-2014 at 08:00 PM. |
08-13-2014, 08:17 PM | #800 |
Wizard
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
|
Incremental update:
I hadn't heard from kiwidude since releasing the locked "gold" code to him a couple of weeks ago, so I checked the first post to see if he'd released it. Only then did I discover that a 1.3.10 update (which this was intended to be) had been released, but that it was apparently a "make it work with qt5" update. If the current version is 1.3.10, then the new version must be 1.3.11, and that meant I had to go in and make that change to the theoretically-locked code. I've just done that, replacing the prior gold version in the above post. Since I had to unlock the code to make that change, I also made some other small adjustments, mainly to improve unpretty but also adding BIG and SMALL to the list of elements that the two "strip" routines will remove if they lack both content and attributes. (In other words, the 8/1 code would remove <b/> but not <small/>; today's code will remove both.) This does not mean that I'm reopening the code or "taking it back" to do more work on it. Think of it as mailing someone a gift, realizing that you really should've enclosed a card, and doing so at the mailbox. |
08-13-2014, 08:19 PM | #801 | |
Resident Curmudgeon
Posts: 73,983
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
Last edited by JSWolf; 08-13-2014 at 08:24 PM. |
|
08-13-2014, 08:52 PM | #802 | |
Wizard
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
|
Well, let's see:
Quote:
"In what instances" - if they lack both content and attributes, just as the example shows and just as the code did before. The only change I made was to add BIG and SMALL to that list...exactly as I said above. <b>blah</b> - not affected (has content). <b class="blah"/> - not affected (has attribute). <b class="foo">bar</b> - not affected (has both). <b/> - removed. <b></b> - turned into <b/> and then removed. It's that simple. None of the listed elements have any effect on the document if they have neither content nor attributes, so stripspans and stripkobo remove them as being bloated, useless code. While it is true that some ebook formatters may choose to style those elements in such a way that their absence will affect the book's display, the same is true of <span> with no attributes; it's possible but unwise. (And that's why you should always keep a backup before applying a plugin, anyway.) |
|
08-13-2014, 09:01 PM | #803 |
Resident Curmudgeon
Posts: 73,983
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
What about something like <a page="10"/> or <a page="10"></a>? do those get removed? Sometimes they are used for a page-map or when links in another XML wants to refer back to a specific place.
|
08-13-2014, 10:16 PM | #804 |
Wizard
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
|
|
08-14-2014, 01:59 AM | #805 |
Wizard
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
|
And 1.3.11 appears to be live.
"Free at last, free at last..." |
08-14-2014, 05:02 PM | #806 |
Resident Curmudgeon
Posts: 73,983
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
|
08-20-2014, 10:01 AM | #807 |
Guru
Posts: 668
Karma: 929286
Join Date: Apr 2014
Device: PW-3, iPad, Android phone
|
Thanks.
In its "Help", under "Smarten punctuation" the "How to detect" column is blank; however that is detected by the Quality Check plugin option "Check smarten punctuation". And of course it's pretty obvious visually, though many seem oblivious to the typographic vulgarity of using straight quotes in a book. Last edited by AlanHK; 08-20-2014 at 10:14 AM. |
08-20-2014, 01:09 PM | #808 |
Wizard
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
|
|
09-10-2014, 06:31 AM | #809 |
Fanatic
Posts: 509
Karma: 60774
Join Date: Aug 2013
Device: Kobo Glo, GloHD
|
Html files go missing ...
Using version 1.3.11
I don't know if that was happening before also. I use 'Modify ePub' plugin as the last step in a series of things I do when I'm preparing an epub for reading. The settings are in the snapshot. When there is any file (html, jpeg ...) inside the epub, with a space in its filename, the plugin will remove it. Any ideas for avoiding this? TIA |
09-10-2014, 07:08 AM | #810 | |
null operator (he/him)
Posts: 20,570
Karma: 26954694
Join Date: Mar 2012
Location: Sydney Australia
Device: none
|
Quote:
From this I deduce that its 'bad form' to have files with spaces in the name in an EPUB. But that said it would be better if Modify either bailed out, or left the file with the dubious name and issued a warning. Seems a tad harsh to just delete the file. I wonder if the Quality Check PI can help detect and prevent this situation. Can't see anything, maybe someone knows better. Could be an enhancement to QC. There are other EPUB Checkers around, maybe one of them can detect and maybe correct - anyone? BR Last edited by BetterRed; 09-10-2014 at 07:13 AM. |
|
Tags |
modify epub |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[GUI Plugin] Quality Check | kiwidude | Plugins | 1184 | 04-17-2024 06:17 PM |
[GUI Plugin] Open With | kiwidude | Plugins | 403 | 04-01-2024 08:39 AM |
[GUI Plugin] Manage Series | kiwidude | Plugins | 166 | 02-13-2024 11:31 AM |
Modify ePub plugin dev thread | kiwidude | Development | 346 | 09-02-2013 05:14 PM |
[GUI Plugin] Plugin Updater **Deprecated** | kiwidude | Plugins | 159 | 06-19-2011 12:27 PM |