Update of bug #64166 (group groff):
Status: None => Fixed
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #4:
Re-closing.
The behavior of the formatter vis รก vis generated output was indeed fixed.
What was not fixed, and appears to have been a bug or oversight going way, way
back, was the behavior of the `.b` register.
Observe _groff_ Git master branch output.
$ groff -Z
foo
x T ps
x res 72000 1 1
x init
p1
.bd TR 10
bar
x font 5 TR
f5
s10000
V12000
H72000
md
DFd
tfoo
wh2500
cbh9
tb
cah9
ta
crh9
tr
n12000 0
x trailer
V792000
x stop
We can see here "foo" not getting overstruck (emboldened), whereas "bar" is.
But if we ask the `.b` register how much emboldening to expect on the next
glyph we write, we get misleading output.
$ printf 'foo\n.tm .b=\\n(.b\n.bd TR 10\n.tm .b=\\n(.b\nbar\n' | groff -z
.b=0
.b=0
$ printf 'foo\n.tm .b=\\n(.b\n.bd TR 10\n.tm .b=\\n(.b\nbar\n' |
~/groff-1.23.0/bin/groff -z
.b=0
.b=0
$ printf 'foo\n.tm .b=\\n(.b\n.bd TR 10\n.tm .b=\\n(.b\nbar\n' |
~/groff-1.22.4/bin/groff -z
.b=0
.b=0
$ printf 'foo\n.tm .b=\\n(.b\n.bd TR 10\n.tm .b=\\n(.b\nbar\n' |
~/groff-1.22.3/bin/groff -z
.b=0
.b=0
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64166>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
