At 2019-06-30T18:43:31+0200, Ingo Schwarze wrote:
> Sure, paper teletypes is what backspace encoding historically comes
> from. But that doesn't mean its usefulness is restricted to
> paper teletypes. In fact, modern pagers handle it just fine.
Yes, but the simple fact is that groff supports app
[redirecting to discussion list]
At 2019-07-01T16:42:10+0200, Ingo Schwarze wrote:
> I know this is a really minor point - but i don't understand this change:
>
>$ LC=C printf "a\nA\n" | sort
> A
> a
>$ LC=en_US.UTF-8 printf "a\nA\n" | sort
> A
> a
Well, (1) LC is not a POSIX-sta
I agree with Ingo about proposed descriptions of \& and sentence
spaces. Elaboration is not explanation.
\& is simply a zero-length character. Its primary use is to disguise
sequences that groff would otherwise unwantedly interpret. For example,
"\&." at the beginning of an input line will be take
> Now, conversely, the backspacing semantic model supports arbitrary
> character composition, which glass TTYs and their emulators never do.
> (Almost never? I'd love to hear of any exceptions.)
Tektronix (storage scope) terminals allowed arbitrary overprinting.
The Tek emulation in xterm stil
Hi Branden,
G. Branden Robinson wrote on Tue, Jul 02, 2019 at 01:03:04AM +1000:
> At 2019-07-01T16:42:10+0200, Ingo Schwarze wrote:
>> I know this is a really minor point - but i don't understand this change:
>>
>>$ LC=C printf "a\nA\n" | sort
>> A
>> a
>>$ LC=en_US.UTF-8 printf "a\n
I agree with Ingo about proposed descriptions of \& and sentence
spaces. Elaboration is not explanation.
\& is simply a zero-length character. Its primary use is to disguise
sequences that groff would otherwise unwantedly interpret. For example,
"\&." at the beginning of an input line will be take
