Quote:
Originally Posted by AlanHK
So I am curious--what situations would you not want to "select all"?
I use TM on epubs that have been generated by, e.g. Calibre converter, or MSWord HTML, InDesign, etc; dense with often redundant code and huge quantities of spans and divs that I can't make sense of or revise until I simplify the code. Those have the same codes in all files.
|
I tend to use plugin primarily on actual book content.. i.e. chapter files. I rarely include backmatter/frontmatter in my processing (or I don't do it at the same time as every thing else). Plus it's common practice for me to test out an expression on one file before committing to turning it loose on large swathes (but still very rarely all) of a book.
As a result of those above scenarios, I almost never select all files before launching the plugin. I have accidentally selected
no files before and had to relaunch, but I can assure you that I'm happy to redo those extra steps whenever that happens. It means I did no potential damage. *shrug*
And seriously (to all, not just AlanHK)... I'm going to start deleting posts (including some of my own). Not because I hate everyone (or the discussion), but because I hate clutter. And this thread is starting to get seriously cluttered.
As I've mentioned several times already, my mind is
entirely made up on how users (including myself) need to select the files that they want this plugin to process. Users will learn that, or they won't. Their choice.