10-17-2013, 10:42 AM | #736 | |
Generally Awesome Person
Posts: 1,061
Karma: 2178845
Join Date: Jan 2013
Location: /dev/kmem
Device: Kobo Clara HD, Kindle Oasis
|
Quote:
Option 3 is just not feasible. |
|
10-17-2013, 11:04 AM | #737 | |
Zealot
Posts: 140
Karma: 82382
Join Date: Jan 2013
Device: Kindle Paperwhite, Kobo Glo, Kobo GloHD
|
Quote:
Do you used the kobo patcher for adjusting some settings like the footers etc? That was one of my first ideas, but I am not sure. Anyone else having these issues and comments? Norbert |
|
Advert | |
|
10-17-2013, 03:01 PM | #738 | |
Watching the Sky
Posts: 234
Karma: 634112
Join Date: Sep 2012
Location: Winnipeg, MB
Device: Kobo Aura
|
Quote:
It does seem odd that they're putting the effort in to make the distinction. I heard it was due to "inaccurate" stats but I know with all the ones I've read they seem to be bang on. And if they were inaccurate why just hide the display instead of just disabling them outright on non-Kobo kepubs? It seems to be all sorts of effort into something that they have no obligation to support anyways. That being said, I'm not going to put too much effort into it. The part I'll miss the most is the bar-graphs of chapter lengths because I actually found that really helpful when planning out reading times. The rest was just "neat." I do recognize that it has to be tough for Kobo to be dealing with features across two separate rendering engines. I wonder if one day they'll just drop the Adobe engine and use the Access completely once it has full Adobe DRM support. |
|
10-17-2013, 03:04 PM | #739 | |
Watching the Sky
Posts: 234
Karma: 634112
Join Date: Sep 2012
Location: Winnipeg, MB
Device: Kobo Aura
|
Quote:
1. The firmware is more sensitive to errors so if the book has poor construction it's causes problems. 2. Kobo has changed something in how it parses .kepubs and jgougen's plugin isn't making quite-compatable files (although you'd probably see the problem significantly more widespread than it seems to be if that were the case) 3. There's something borked in my database. I might scan my database for errors tonight just to try and rule #3 out. I doubt #2 although in theory it could be possible. We'll see if a "fixed" book eliminates the problem. |
|
10-17-2013, 04:08 PM | #740 |
Generally Awesome Person
Posts: 1,061
Karma: 2178845
Join Date: Jan 2013
Location: /dev/kmem
Device: Kobo Clara HD, Kindle Oasis
|
Well, I've not yet made a fully-compatible file, so you may be mostly right on #2 even if it's not all of the problem
|
Advert | |
|
10-17-2013, 08:05 PM | #741 | |
Watching the Sky
Posts: 234
Karma: 634112
Join Date: Sep 2012
Location: Winnipeg, MB
Device: Kobo Aura
|
Quote:
My only hesitation to saying that's the problem is that it doesn't seem to be widely reported among users of your plugin. Hmm… Either way I wouldn't lose too much sleep over it. You have better (little breathing) things to spend your time on |
|
10-17-2013, 11:28 PM | #742 |
Grand Sorcerer
Posts: 12,168
Karma: 73448616
Join Date: Nov 2007
Location: Toronto
Device: Nexus 7, Clara, Touch, Tolino EPOS
|
@jgoguen: I tried copying a kepub to a name based on an UUID and placed it in the .kobo/kepub directory directly. On unplugging the device, book did not appear on the unit.
Out of curiosity I used Desktop to add a new kepub and on unplugging, no scan for new material but the book did appear. I sense that the kepub directory is not actually scanned for material; rather the process of adding books (either via Desktop or Nickel itself) adds the books to the database and the scan process only looks for sideloaded ePubs (and of course sideloaded kepubs with the .kepub.epub name). If so, I think this takes one down the path that DavidFor has been nervous about; updating the contents table from calibre. One experiment that might be worth trying.
Now see if
|
10-18-2013, 12:21 AM | #743 | |
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:
I just did a little test with the current beta firmware. I tried three books: a purchased kepub with embedded font, the epub version of this which has also has an embedded font and a known good epub that doesn't have embedded fonts. I sideloaded the epubs using the current version of the extended driver. For both the purchased and sideloaded kepub, I saw (roughly) what you are seeing. Changing the font to something other than "Document default", and there were no problems. The book with no embedded font had no problems with any font settings. The "roughly" is because the problem has been partly fixed in the beta. When using the embedded font, opening the book took a long time to display the text. But, it does get displayed. |
|
10-18-2013, 12:26 AM | #744 | |
Watching the Sky
Posts: 234
Karma: 634112
Join Date: Sep 2012
Location: Winnipeg, MB
Device: Kobo Aura
|
Quote:
|
|
10-18-2013, 01:30 AM | #745 |
Watching the Sky
Posts: 234
Karma: 634112
Join Date: Sep 2012
Location: Winnipeg, MB
Device: Kobo Aura
|
So I was playing around tonight to see if I could narrow down what the problem is, and I'm becoming more and more convinced it has to do with how span tags are added. In particular, when looking at a few of the books I have on my device compared to ones that I have problems, there seems to be a difference in how the Kobo spans are sequenced.
Specifically, the books I have problems with tend to have Kobo span numbers skipping values. For example, I'll have 6.1, 6.2, 6.3, 6.4 in a <p></p> block, then the next <p> block starts with a kobo span numbered 9.1. I'm not sure where the missing spans are going (perhaps blank paragraphs or something) but that seems to be one of the few differences I can pick out between books working correctly vs. not. I'm not sure how "normal" span numbering is in .kepubs, but if the spans are as critical as I've gotten the impression they are while watching the development, is it possible that this could be the issue? Or is it fine if certain span numbers are skipped? If it is indeed an issue, I'd be more than happy to open an official bug. EDIT: So, silly me. I started to wonder if there could be other problems, so I went looking through the instructions for the plugin. Did the location required for the reference.kepub.epub change at some point, because I had it in a KoboTouchExtended folder inside Calibre's plugin folder and I saw in the instructions that it was to be in the root of the plugin folder. I feel almost certain it wasn't like that at some point in the past...either way, I moved it into the root plugin folder and now it works like a charm. Now I sure feel silly! Last edited by buffaloseven; 10-18-2013 at 02:03 AM. |
10-18-2013, 02:22 AM | #746 | ||
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:
Quote:
Is there any chance of seeing the books? I can see if they behave the same on the beta firmware. And I think would manually fix the span count just to see what happens. One thing I did just see when comparing a DRM free purchased kepub and a sideloaded kepub is where the space is between sentences and spans. For the purchased kepub, the space after the full stop is inside the span. For the sideloaded, it is between the spans. The examples are: Code:
Purchased: tomb. </span><span class="koboSpan" id="kobo.3.2">He awoke Sideloaded: indifferently.</span> <span class="koboSpan" id="kobo.8.2">“It would The other problem it could cause is with highlighting. If it starts or ends on the space, that could cause a problem. Last edited by davidfor; 10-18-2013 at 02:23 AM. Reason: Later edit by buffaloseven nullified a lot of this. Must no let work interfere with MR. |
||
10-18-2013, 04:04 AM | #747 | |
Watching the Sky
Posts: 234
Karma: 634112
Join Date: Sep 2012
Location: Winnipeg, MB
Device: Kobo Aura
|
Quote:
|
|
10-18-2013, 05:02 AM | #748 | ||
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:
Quote:
The case I was thinking of was starting or finishing the highlight on the space. Testing just now and it would select the text, but didn't save the highlight. |
||
10-27-2013, 03:02 PM | #749 | ||
Junior Member
Posts: 2
Karma: 10
Join Date: Oct 2013
Device: Kobo Glo
|
I just uploaded my Kobo glo to the 2.8.1 and Calibre to the 1.8 (I do not remember the order probably in parallel) and now I can not update the plugin.
This message is displayed: Quote:
Quote:
Last edited by nicolacdnll; 10-27-2013 at 03:09 PM. |
||
10-27-2013, 03:53 PM | #750 |
Generally Awesome Person
Posts: 1,061
Karma: 2178845
Join Date: Jan 2013
Location: /dev/kmem
Device: Kobo Clara HD, Kindle Oasis
|
Delete the plugin and reinstall. It won't affect your books or settings, those are stored separately.
What version of calibre and the extended plugin did you start at before upgrading? |
Tags |
error, kobo aura one |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Kobo Device Driver Update | davidfor | Devices | 284 | 05-24-2019 05:24 PM |
[Device Plugin] Kindle 2, 3, 4, Touch Device Interface MBP Update Mod | cryzed | Plugins | 7 | 10-28-2012 04:58 PM |
[Device Interface Plugin] Update for Nook Color Driver | jmricker | Plugins | 0 | 10-22-2011 10:11 AM |
Touch Kobo Touch Extended 2 Year Warranty - Is it worth the $34.99? | EverC | Kobo Reader | 11 | 08-31-2011 11:47 PM |
Touch Kobo Touch Extended Warranty Program | SensualPoet | Kobo Reader | 1 | 07-17-2011 04:08 AM |