Quote:
Originally Posted by FrustratedReader
Yes, I can resize it.
Still no use for Kindle PW3 unlike Kobo H2O every note & highlight is after the location, like in my clippings. Though the formatting is terrible the Kobo Utilities Fetch Annotation works better, it only needs a few global edits to fix it into a nice text file. Simply copying My cllppings.txt for the Kindle PW3 is faster and just as functional as this Annotations plug in.
|
The issue is that you are interpreting the contents of the My Clipping.txt file differently to the plugin, and apparently every other user of the plugin. The plugin is reading each section in the file and putting those into separate elements in the generated HTML. This means there is an element for each "Your Highlight" and "Your Note" in the file. You seem to be saying that these are actually connected together and should be treated as a highlight with a note. Looking at your examples, that doesn't seem unreasonable, but, it isn't completely obvious how they are connected. Also, the plugin has been working this way for a long time and no-one has reported an issue with this. Unless the file format has changed recently, I am loath to change the plugin without more reports that it is wrong.
Quote:
Also there is limit on how many annotations this plugin will read from Kobo. I'm up to 1352 at 51% of the book and the KoboUtilities fetch gets them all, but this Annotations Plugin truncates at some point.
|
Not that I can think of. Is the code in the field complete? If not, it is probably a limitation on the long text field being used in calibre.
Quote:
I've abandoned the idea of switching to PW3 for proofing as the imported info is poorer than Kobo Utilities which gives logical chapter, chapter title text, percent into chapter etc. The PW3 is much nicer to select, but I've found using the SD card and wider line spacing the text selection is now only a little slower on Kobo H2O than it used to be, though speed is erratic.
Selection is just wonderful on the Kindle PW3, pity the actual extracted data is poor.
|
A small correction: The extracted data is only as poor as the available data.
Edit:
I have fixed at least one of the problems you have mentioned. I just haven't gotten to finish testing it. Plus I'm still completely baffled about where the extra line you keep pointing at is coming from.