I think your "beginning of paragraph" doesn't matter -- unless, that is, there may be more than one em-space in a single paragraph.
Jongware, you were correct! You win the double-awesome award for both nailing the solution and in under one hour.
I was surprised by your solution until I realized that the positive lookahead tells the search to continue as long an em-space is 'somehwhere' up ahead, not just immediately ahead. My origninal (failed) GREP was similar, but did not include the wildcards preceding the em=space: \l+(?=~m).
Just curious, why can't you applythe small caps as part of the same style that does the Bold and Italic?
Peter, we chose to not apply primarily because we're not fond of the built-in options.
- Using the preferences>small caps runs risk of small caps being different sizes with different people doing layout (three compositors, 90+ chapters, plus multiple revision rounds creates many opportunities, along with a style-checking nightmare.)
- OTF small caps are smaller than our designers and production supervisors approve. Plus, not all fonts have small caps built in so we have to be good at constructing these another way.
- Our solution of using a character style for small caps (type is set to all caps, 85% veritcal and horizontal scaling) works well for single-line heads (without any nesting needed) until we got to this instance requiring both nested styles and GREP settings to accomplish. I could either make the text all caps, or all small caps, but not both.
I'm always seeking simpler solutions. Am I missing an option?
With all that customization, no, I don't think so, though you CAN se the prefs for waht "regular" small caps will be as a document attribute. That won't necessarily help with the OTF stuff, though.