The basic problem here is we are working in a multilingual world (Greek, Hebrew, local language, language of wider communication), but the editor in Paratext does not recognize that. So “everything” in project X is in the X language. And this approach is just too simplistic.
What is needed is a way to mark Greek, Hebrew, and LWC, with unique SFM styles (for each) and these be maintained separately in the “Valid/Invalid” list. And NOT be mixed in with the X Language’s character, spelling, or wordlist inventories. (Even valid LWC punctuation might be invalid for language X.)
Where we work, today we might mark some weird letter as valid found in a word from the LWC in a footnote. But does doing this open the possibility that someone may introduce a typo in X language using that “valid” character, because we marked it as valid? I.e. it is valid for the LWC, but it is INVALID if used in the X Language.
So how do we differentiate this? And why can’t we just mark these as different languages? That seems the most obvious solution. Every other reasonably powerful editor I know recognizes “language”, surely we should in this business of translation.
Granted, this isn’t needed a lot, but it is needed often enough that a solutions would be very helpful. (And I agree with anon848905 that just “ignoring” them is a less than ideal solution.) These are “valid” in certain cases; we need Paratext to be smart enough to recognize the context (the SFM brackets) and validate them based on their particular subset.