Quote:
Originally Posted by chaley
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 ?