I have read this older thread
about including case sensitive forms of certain glyphs (that thread veered a bit off-topic, and my question is a bit tangential to it, so I’m starting a new thread); it got me wondering: Is it common practice to put case specific substitutions (like for parens, dashes) into the CASE feature? I worry that this approach would be pretty fragile, considering that many people may never actually use the CASE feature but just TYPE IN ALL-CAPS, which would then not trigger the substitutions.
How about a CALT feature instead that substitutes these glyphs if they have nothing but caps, punctuation and spaces around them (or; no lowercase). Does anyone do this? Thinking it might be a bit hairy to determine the exact permissible trigger sets, but if that can be worked out such an approach could be more bulletproof? Curious to hear opinions.