Follow-up Comment #25, bug #66919 (group groff): This might show up twice. The Savannah bug tracker just glitched for me HTTP-wise in a kind of weird way.
Since I know that was a _boatload_ of stuff to read, here's a simpler
illustrator of one of my claims.
> we might retitle this ticket "[troff] behavior change in some
> .hcode calls when an ordinary character is the second argument",
> and you can guess what my proposed resolution is.
Here's my evidence. Let's throw out the confounding factor of a special
character altogether.
$ iconv -f iso-8859-1 EXPERIMENTS/lanteronial-Z.groff
.ll 1n
lanteronial
lanterZnial
.hcode Z รต
lanterZnial
$ ~/groff-HEAD/bin/groff -a -Wbreak EXPERIMENTS/lanteronial-Z.groff
<beginning of page>
lantero<hy>
nial
lanterZ<hy>
nial
lanterZnial
$ ~/groff-1.23.0/bin/groff -a -Wbreak EXPERIMENTS/lanteronial-Z.groff
<beginning of page>
lantero<hy>
nial
lanterZ<hy>
nial
lanterZ<hy>
nial
$ ~/groff-1.22.4/bin/groff -a -Wbreak EXPERIMENTS/lanteronial-Z.groff
<beginning of page>
lantero<hy>
nial
lanterZ<hy>
nial
lanterZ<hy>
nial
$ ~/groff-1.22.3/bin/groff -a -Wbreak EXPERIMENTS/lanteronial-Z.groff
<beginning of page>
lantero<hy>
nial
lanterZ<hy>
nial
lanterZ<hy>
nial
A behavior change, yes, one that is completely symmetric with yours except for
my use of an ordinary character in place of your special one.
I claim the formatter cannot assume which hyphenation codes are valid (apart
from, arguably, a-z and A-Z, because inertia and Western-centrism).
Selection of any other valid hyphenation codes is up to the encoding macro
files and, I submit eventually, solely the localization macro files.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66919>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
