View Single Post
Old 12-07-2014, 07:02 PM   #6
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by saoir View Post
Ok. Still. He could annotate the complete paragraph where the error occurs ... and I could then use the search function in Scrivener to track it down. May still be useful.
That's what I do when fixing books I am reading. I mark enough text to be able to find the problem and add a comment to describe what is wrong. Admittedly, I normally just work off the annotations list on the device, but this allows me to work from within calibre as well.

Thinking about how the plugin works, there is another possibility. For the Kindle devices, it reads a file called "My Clippings.txt". If he sends you that, you should get enough info to track down the problems. And it's possible that if you copy that to your Kindle, it will show the annotations in your device. I have a feeling that something else is needed, but it is worth trying. It does require that the book file names are the same on both devices. I don't have a Kindle device, so I can't test this.
davidfor is offline   Reply With Quote