@
davidfor - non breaking hyphen issue was a point of interest. They make sense in words like 'e-mail', I've seen that broken across two lines on web pages, they also make sense in identifiers such as part numbers, telephone numbers, credit card numbers etc - especially if a user wants to select for lookup etc. But can they be rendered in common-or-garden fonts on common-or-garden e-readers - maybe not?
Re the other issue of providing an option for the 'legacy' algo: I use a change in word count as an indicator - that something has changed. Sometimes it's expected, and other times not. If I'm expecting it to change and it doesn't then it usually indicates I forgot to do a change (or save the change). If I'm expecting to stay the same and it doesn't then it usually means I made some other error.
I don't want to recount my entire library, it's nudging 100,000. So absent a legacy algo option I'll rejig current Count Pages into a private Old Count Pages - I care more about consistency than I do so-called accuracy
BR