On Thu, 5 May 2022 03:40:27 -0500
Dave Kemper wrote:
> To cite the example that originally launched this thread, the old
> docs termed the \& a "zero width space," which Branden has changed to
> the "non-printing input break." It may not roll off the tongue as
> easily, but it's more precise and
Hi James,
[I'm reordering one sentence in your reply.]
At 2022-06-04T15:23:36-0400, James K. Lowden wrote:
> To insert \& at the start of a line does not affect how the input is
> parsed.
Yes, it does.
$ gdb ./build/troff
GNU gdb (Debian 10.1-1.7) 10.1.90.20210103-git
Copyright (C) 2021 Free So
On 6/4/22, James K. Lowden wrote:
> A "zero width space" is perfectly clear terminology.
Not to anyone familiar with Unicode's U+200B ZERO WIDTH SPACE, which
doesn't correspond to groff's \& but to its \: (which groff currently
calls the "non-printing break point"). And regardless of who can
cla
Hi,
James K. Lowden wrote on Sat, Jun 04, 2022 at 03:23:36PM -0400:
> On Thu, 5 May 2022 03:40:27 -0500 Dave Kemper wrote:
>> To cite the example that originally launched this thread, the old
>> docs termed the \& a "zero width space," which Branden has changed to
>> the "non-printing input break
On Friday, 3 June 2022 10:04:52 BST G. Branden Robinson wrote:
> commit afa7128d7b939ca5c8cd082f2547f42e4e563674
> Author: G. Branden Robinson
> AuthorDate: Fri Jun 3 03:02:52 2022 -0500
>
> [font/devpdf]: Revise path component separation.
>
> * font/devpdf/devpdf.am (font/devpdf/util/Bu
On Saturday, 4 June 2022 22:44:10 BST Dave Kemper wrote:
> On 6/4/22, James K. Lowden wrote:
> > A "zero width space" is perfectly clear terminology.
>
> Not to anyone familiar with Unicode's U+200B ZERO WIDTH SPACE, which
> doesn't correspond to groff's \& but to its \: (which groff currently
>
Hi Ingo,
At 2022-06-05T00:19:30+0200, Ingo Schwarze wrote:
[...]
> the groff documentation uses the term "break" very
> consistently, defining it as starting a new output line even though
> the current output line is not yet full.
Yes, and I have striven to reinforce that consistency wherever pos
Some history:
The discussion that prompted the August 2020 terminology change is
consolidated in http://savannah.gnu.org/bugs/?58933 (it started
earlier on the email list, but that bug report contains links to the
relevant email discussion).
One point made therein is that the original CSTR#54 ter
Hi Deri!
At 2022-06-05T00:14:38+0100, Deri wrote:
> On Friday, 3 June 2022 10:04:52 BST G. Branden Robinson wrote:
> > commit afa7128d7b939ca5c8cd082f2547f42e4e563674
> > Author: G. Branden Robinson
> > AuthorDate: Fri Jun 3 03:02:52 2022 -0500
> >
> > [font/devpdf]: Revise path component se
