View Single Post
Old 01-16-2011, 03:29 AM   #8
pchrist7
Addict
pchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animalspchrist7 is kind to children and small, furry animals
 
pchrist7's Avatar
 
Posts: 384
Karma: 6514
Join Date: Aug 2010
Location: Denmark
Device: Kindle 3 3G+Wifi
Lightbulb Brilliant !

Quote:
Originally Posted by chaley View Post
This works with that example.
Code:
{comments:'contains($, '(?i).*?last page read: location', re($, '(?is).*last page read: location \d+ \((\d+)%\).*', '\1'), '')'}
The previous one was not checking for the numbers after the word 'location'.
Hi Chaley
That was it !
Spotted that myself but just couldn't figure out how to do it
Thank you SO much !

Now all I have to figure out is a new custom column Read, that is set to Yes if #pct_read > 94, otherwise No

Do you have the time/energy for this as well ?

This is very good news to Kindler's as we can use at least some of the annotations !



Just did a restart of Calibre.
I had no idea of the potiential performace impact of custom columns.
I guess all records are checked during startup to calculate the custom columns ?

Last edited by pchrist7; 01-16-2011 at 03:47 AM. Reason: wondering
pchrist7 is offline   Reply With Quote