Hi Ingo, > > - “no-op escape” > > But this one, or a variation thereof, might perhaps sever the knot.
This is the only one which seems useful, and continues a theme I went for in another email. > It avoids both the very misleading terminology "input break" Yes, very misleading. > It is usually not inserted for some effect it might have but merely to > prevent an adjacent punctuation character from being the first > character on an input line, the last character before an input ASCII > space or tab character, or the last character on an input line. Even > when used to disable kerning (which i would expect to be rare, in > particular compared to the other use cases), thinking along the lines > of "let's have a no-op instead of kerning" or "let's insert a no-op > because there will be no kerning between the adjacent characters and a > no-op" would make sense to me. A reminder, when thinking of all \&'s uses, that tbl(1) uses it to align numeric columns. -- Cheers, Ralph.
