[Peter Blaise]

In response to davidfor who suggested:
[ Find: ]
\b([[[:upper:]]-]{2,})\b
... for 2+CHARACTER-CAPS-WITH-HYPHENS
\b([[:upper:]]{2,})\b
... for 2+CHARACTER-CAPS-WITHOUT-HYPHENS
... plus [✓] Case sensitive
... [ Mode: ] [ Regex-function > Title-case text (ignore tags ]
... then [ Find ] and [ Replace and Find ]
... the user making editing decisions on each found word depending on actual word contents.

Yes, thank you, that reduces 5-clicks per word in [ Check spelling ] or the resulting 5-or-so-clicks required by my alternative 2-step of ( 1 ) search and make lower, then ( 2 ) re-search and make Leading Caps, taking either routine down to 1 or two clicks per CAPS word or phrase, manually, throughout the whole ebook.

But, unlike fixing in [ Check spelling ], I must fix each occurrence of a YELLING word, or additionally make a separate series of [ Replace all ] for words that I know reoccur. such as replacing all JOHN with John.

And, unlike my 2-step, which finds entire phrases, this find one word at a time.

So, on the one hand, the \b([[:upper:]]{2,})\b suggestion works.

On the other hand, I still have to scan the entire ebook manually, make a decision on every single WORD, manually, so this is still not an automatic whole-ebook-conversion solution.

But a significant improvement nonetheless.

Thank you.

Does anyone else have any other routine that they use to change YELLING to Leading Caps or Sentence caps?

I presume a thoroughly well-developed multi-line iterative interdependent program would include lookups to leave words like US and NJ and FISA and the like - known abbreviations, and maybe have a user toggle for CAPS-WITH-HYPHEN to either Caps-with-hyphen or Caps-With-Hyphen, plus awareness of punctuation, such that titles of works and headings get Leading Caps, and first lines of paragraphs get Sentence caps.

I suppose I could use text-to-speech, then speech-to-text ... but I would lose all formatting.

Why do people STILL YELL?

Thanks everyone for exploring this and sharing.
.