🚀 go-pugleaf

>2.  Fixed the various ligature bugs.  Most of these haven't even been fixed
>	in the newest ditroff, by the way.  Getta loada these:
>
>	% troff -a
>	.nr f 1
>	xx\nfyy
>	.fl
>	xxy1y

In n4.c, function setn(), you see code like:

	if((i=getch() & CMASK) == '+')f = 1;
		else if(i == '-')f = -1;
			else ch = i;

Change this to:

	lgf++;
	if((i=getch() & CMASK) == '+')f = 1;
		else if(i == '-')f = -1;
			else ch = i;
	lgf--;

>	% troff -man
>	.TP
>	.BI \-f fontname
>	.TP
>	\fB\-f\fIfontname\fP
>
>	The above produces an ff ligature in bold instead of an f in bold
>	then an f in italics.  The bug apparently results from .TP's use
>	of the rare .it request.

Actually, it's not the .it request, but the diversion that .TP uses.  The
problem is in t6.c, in getlg().  What getlg() needs to do is check the size
and font bits of the next letter with the current letter (which was the
letter f) and fail if they don't match.  You need something like:

#define	SFMASK	077000
#define	fontmismatch(i,j)	(((i) & SFMASK) != ((j) & SFMASK))

In getlg(), each time you do a getch0(), do a fontmismatch() test on the new
character with the original (f) character.  If there is a mismatch, you stop
where you are (either with just an f, or with a two character ligature).
Remember to push back the new character into ch0.

Edward Moy
Academic Computing Services
University of California
Berkeley, CA  94720

edmoy@opal.Berkeley.EDU
ucbvax!opal!edmoy