[Top][All Lists]

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

[bug #55155] [troff] .tr is applied to the RHS of .char definitions

From: Bjarni Ingi Gislason
Subject: [bug #55155] [troff] .tr is applied to the RHS of .char definitions
Date: Wed, 12 Apr 2023 17:56:15 -0400 (EDT)

Follow-up Comment #15, bug #55155 (project groff):

[comment #13 comment #13:]
> [comment #12 comment #12:]
> > Further musings:
> > 
> > All the example usages in the email thread appeared to be contrived for
this thread; no one responded with a clear real-world case that would be
affected by the change one way or the other.
> I can address that.
> Format Kernighan & Cherry's "Typesetting Mathematics -- User's Guide (Second
Edition)" for PostScript or PDF and watch the page header bounce back and
forth between hyphens and minus signs.
> Procedure:
> 1. Obtain the paper's source files. 
> 2. Apply the attached patch.
> 3. make eqnuser.pdf
> 4. Compare, e.g., the page headers on pages 2 and 3.
> Optional step 2a--review the patch file and verify that there is nothing up
my sleeve.  The sources of the user's guide are the files starting with "g".
> (file #54594)

  This is a bug in the input source.  The transliteration is absent if
the formatting is for an A4 page (groff ... -dpaper=A4 ...)

  The cause of the visibility of the bug is a page break between the
macros P1 and P2 in file "g1".

  Adding a test before macro P1:

.\" Added to avoid a page brake before .P2
.if \n(.t<4v .bp

resolves the problem.

  So, it is the responsibility of the writer to ensure that the
transliteration is reversed in time.

  Ergo: no need to mess with the code of the request "tr".


Reply to this item at:


Message sent via Savannah

reply via email to

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