Quote:
Originally Posted by davidfor
Others have commented, but personally, I see the last few pages as a healthy discussion about the plugin. Someone reported a possible problem, and the discussion has been about how useful it is to fix the bug. I like seeing this level of involvement as it helps to work out the best solution.
|
A discussion about word counting without any discussion about when hyphenation should be used is a somewhat barren discussion. The latter is to some degree a matter of style, it's also a matter where there are no hard and fast rules. Google 'when to use hyphens' and read what the writerly commentariat and grammarians have to say on hyphenation.
The existing algorithm is NOT a bug - putting a Whitworth nut on a Metric bolt is a bug. But that JSWolf regards all opinions, other than his own, as bugs, is a proven fact
It's an issue of which algorithm to use. The one that has stood
those who use it in good stead for nigh on 5 years. Or one that has only become available in recent times. There would be no discussion, from me at least, if the proposal was to
add an option to use the existing or the ICU algorithms when computing word counts. IMO, adding an option would be in the 'spirit' of the original developer, who usually (always ?) protected 'legacy' features. If at all possible, existing 'installs' would set the option to use the 'legacy' algorithm, new installs would default to the 'ICU' algorithm.
Support forums are riddled with complaints about Apple, MS, Google etc blithely clobbering/discontinuing existing features. Less so with IBM, if you're minded you can definitely run IEBGENER and probably DISSOS or PROFS on your shiny new z/OS system.
Facetiously, one might suggest an option to include the components of hyphenated words in the word count if they are present in designated dictionaries. Thus, the compound word 'so-called' would likely be counted as two words, whereas 'topsy-turvy' would likely be counted as one. But
realistically one wouldn't — would one?
===============
An unrelated feature I'd like to see in Count Pages, is an option to use the format file with the latest
file system modification date as the basis for counting. In my workflow that would avoid in-flight conversions to EPUB - because in 99% of cases, I Convert from non-EPUB to EPUB immediately prior to running Count Pages.
NB: EPUB is not even close to being near the top of my preferred input format list, although it is my designated output format. I rarely need to convert from EPUB, when I do it's unlikely I would then run Count Pages. I would typically attach the output format file to an email, send it, and then remove the format from the library.
BR