12-19-2013, 01:44 AM | #46 |
Grand Sorcerer
Posts: 24,908
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
I have been remiss...
The new version of the plugin is working well. And I have a working class for the Kobo devices. It just needs a little more testing. If there is a willing guinea pig out there, please contact me. |
12-19-2013, 05:08 AM | #47 |
Grand Sorcerer
Posts: 6,211
Karma: 11766195
Join Date: Jun 2009
Location: Madrid, Spain
Device: Kobo Clara/Aura One/Forma,XiaoMI 5, iPad, Huawei MediaPad, YotaPhone 2
|
If you want I can add some annotations and test it.
|
Advert | |
|
12-19-2013, 09:23 PM | #48 |
Grand Sorcerer
Posts: 24,908
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Thanks Terisa. I have sent you code and some instructions.
|
12-26-2013, 04:17 AM | #49 |
Grand Sorcerer
Posts: 24,908
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Bug or feature?
Thanks to Terisa and gwalden who are testing the annotations for the Kobo devices, it is very close to being releasable. But, both noticed something I didn't and now I can't work out if it is a bug in my code, the plugin or whether "it's not a bug, it's feature" applies.
The problem is when an annotation is changed on the device after they have been fetched. When the annotations are fetched again, there are two entries for the annotation. The first has the original text and the second has the new text. When I do another fetch, the original version of the annotation is removed. So, I can't decide if this is a bug or not. I can see that what I describe might be deliberate. I don't think it is my code, as I am simply building the current list of annotations and passing it on to update the metadata. I did have a quick look at the code that rebuilds the annotation text, but it didn't jump out at me as to whether what is happening is deliberate or not. |
12-26-2013, 05:32 AM | #50 |
Comparer of the Ephemeris
Posts: 1,496
Karma: 424697
Join Date: Mar 2009
Device: iPad
|
The intent is to merge already-stored annotations with new annotations. Merging is done in annotations:merge_annotations() around line #229. Replication of existing annotations is avoided by comparing hashes. I'm not sure what would cause the behavior you're describing.
I am traveling with infrequent internet access until early January. When I get a chance, I will do some testing to see if I can replicate the behavior you're describing. In the meantime, if you identify an issue with the current code, please create a new issue at GitHub. G |
Advert | |
|
01-02-2014, 11:36 AM | #51 | ||
Enthusiast
Posts: 28
Karma: 10
Join Date: May 2012
Device: Sony PRS-T1
|
Quote:
text/part0000_split_005.html#point(/1/4/9:2) (one position before the beginning of the highlight) text/part0000_split_005.html#point(/1/4/10/1:1) (end of highlight) Nook must use something alike: https://www.mobileread.com/forums/showthread.php?t=99000 Quote:
I already partially figured out how this works: /1 indicates the root element (<html...) even numbers navigate through the elements. So 2 is the first child of the root (<head...), 4 is the second child of the root (<body...), /1/4/10/ is the 5th child of the body (usually the 5th paragraph or header). : idicates the offset within the element. However, I am not quite sure what odd numbers mean. They usually occur if the highlight starts at the beginning of the paragraph. So the position before the highlight is "between the paragraphs". But in case of /1/4/9:2 --> what's the second character of "between paragraph 4 and 5? Do you happen to know that, by chance? So, I am almost there, but not quite. I was hoping that looking at your code might help me to figure out the remaining gaps - and also give me an idea to write code to navigate using this kind of identifiers. Thank you very much for any ideas - or the code ... ... and of course all the very best in 2014!! - spitfire |
||
01-02-2014, 08:33 PM | #52 | ||||||
Grand Sorcerer
Posts: 24,908
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
I should add, the Kobo devices use two different readers. The other is for their own modified kepubs. The other reader uses a different bookmarking method. Quote:
Quote:
I might have a bit of a play later. It will give me something to do while hiding from the in-laws. Quote:
And my Kobo Utilities plugin won't help. It will store the current reading position, but it is the full string. I have considered trying to translate this to the method that calibre uses. That way I could update the position for the calibre viewer, but I haven't seen the need yet. I would actually be interested to know if the reading position on the Sony devices are stored somewhere accessible and in what format. Because of the common Adobe RMSDK, I have been wondering of the Kobo position could be copied to the Sony devices. Quote:
Quote:
|
||||||
01-03-2014, 03:11 PM | #53 | |
Enthusiast
Posts: 28
Karma: 10
Join Date: May 2012
Device: Sony PRS-T1
|
Thank you very much for your fast, friendly and helpful reply! That helps a great deal, I did not know it was the same system ADE uses. That opens new sources of information And, maybe even the possibility to port the annotations to ADE? I'll have to look into that. My goal is basically to translate the Sony annotations to some other system, so that I can finally export the annotations together with the book to some other reader app. I don't like depending on one physical device in order to make use of my annotations. Understanding the system Sony uses is the first step to that.
Quote:
OEBPS/9781118087459c09.xhtml#point(/1/4/2/276/1:453) If you are interested, you can pm me and I will send you the entire books.db, so that you can have a look at it first hand. Best regards, spitfire |
|
01-03-2014, 08:05 PM | #54 | ||
Grand Sorcerer
Posts: 24,908
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
The Annotations plugin might be right for you, so long as you don't want to send them back to a device. The fetching and display works well. I had a misunderstanding about an intention of how part of this works. My usual use for annotations is temporary notes for things I need to fix in the book. GRiker intends it a more permanent notes. Once he explained that, I can see the reason for some of the behaviour that had baffled me. Quote:
This is what I store for the reading position: Code:
(4)OEBPS/Text/119579.xhtml|@ @|OEBPS/Text/119579.xhtml#point(/1/4/260/1:61) I would like to see the full database to confirm this. I'll send you a PM. * "easy" - Term used by programmers to describe a programming task they haven't really looked at but will probably take months of work. |
||
01-03-2014, 08:19 PM | #55 |
Grand Sorcerer
Posts: 12,119
Karma: 73448614
Join Date: Nov 2007
Location: Toronto
Device: Nexus 7, Clara, Touch, Tolino EPOS
|
Isn't actually a term used by management to describe a task that will require a total re architecturing of the project to implement a feature that no user will ever utilize?
|
01-03-2014, 09:39 PM | #56 |
Grand Sorcerer
Posts: 24,908
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
It's all a matter of your point of view, but it sounds like you've me the managers on my last big project.
|
01-04-2014, 02:07 AM | #57 |
Grand Sorcerer
Posts: 6,211
Karma: 11766195
Join Date: Jun 2009
Location: Madrid, Spain
Device: Kobo Clara/Aura One/Forma,XiaoMI 5, iPad, Huawei MediaPad, YotaPhone 2
|
Well, you can think about a customer asking for a major feature they want for free, too.
|
02-02-2014, 01:38 PM | #58 |
Guru
Posts: 962
Karma: 568242
Join Date: Dec 2007
Device: Kindle Oasis 3, Kindle Paperwhite 1, iPad, iPhone
|
Quick question. I see a class called _iosKindle.py in Github but it's not part of the annotation plugins downloaded through Calibre. I went through the steps of adding the file to the additional_readers config in the annotations.json file but I don't see the iOS kindle device in the menu. Is there something I am missing?
|
02-02-2014, 02:36 PM | #59 |
Comparer of the Ephemeris
Posts: 1,496
Karma: 424697
Join Date: Mar 2009
Device: iPad
|
The classes preceded with a leading underscore are sample code or incomplete implementations. Kindle for iOS is incomplete because I couldn't figure out how to extract the highlight color from the database. You're welcome to work with it. If you have any implementation questions please post them in the GitHub project.
G |
02-03-2014, 09:52 AM | #60 |
Guru
Posts: 962
Karma: 568242
Join Date: Dec 2007
Device: Kindle Oasis 3, Kindle Paperwhite 1, iPad, iPhone
|
I am not a good Python developer but I might be able to hack it, having written a little calibre code in the past. I guess I'm just trying to figure out what's missing since it looks like the highlighter code is just assuming it's yellow. I'll post over at the GitHub project.
|
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[GUI Plugin] Annotations | davidfor | Plugins | 1152 | 03-22-2024 09:38 PM |
[GUI Plugin] KindleUnpack - The Plugin | DiapDealer | Plugins | 492 | 10-25-2022 08:13 AM |
[GUI Plugin] Marvin XD (closed) | GRiker | Plugins | 141 | 06-15-2014 05:36 PM |
Plugin thread closed? | BookJunkieLI | Calibre | 3 | 10-05-2013 02:56 PM |
[GUI Plugin] Plugin Updater **Deprecated** | kiwidude | Plugins | 159 | 06-19-2011 12:27 PM |