bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #59795] [PATCH] troff/env.cpp: fix wrong restoration of line adjust


From: G. Branden Robinson
Subject: [bug #59795] [PATCH] troff/env.cpp: fix wrong restoration of line adjustment after '.na' and '.ad'
Date: Mon, 18 Jan 2021 03:43:28 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Update of bug #59795 (project groff):

                  Status:             In Progress => Need Info              

    _______________________________________________________

Follow-up Comment #2:

I'm dubious about this.

My observations:

1. groff as currently implemented is compatible with Heirloom Doctools troff
in this respect.  Both Heirloom and groff extend AT&T troff to expose a .j
register which reports the numerical value of the adjustment mode.  I'll bet
this was done so that you could save it; see point 3 below.

2. CSTR #54 (1992) is a bit slippery in its terminology here.  Sometimes it
uses the word "adjust" to mean adjustment to both margins, and sometimes to
the collective possible values of the .ad request.  Nevertheless it is clear
that the "initial default" for the formatter is "adj,both", and that if no
argument is given to the request, the implicit command is to "adjust".  How? 
To both margins.

3. AT&T troff was inconsistent about requests stashing state; sometimes you
got a 1-level stack to which an ".xx YY" request pushed and from which ".xx"
popped, and sometimes AT&T troff was just clobberific.  I myself had assumed
that .na caused the previous adjustment mode to be remembered, but upon
investigation that appears not to be true.

Changing this would be really disruptive, perhaps to the extent of requiring a
new request to support the desired semantics, if anything is done at all.

I'm inclined to close this as invalid, but would appreciate comments from
others.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59795>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]