Re: [tz] Doubts about a typo fix

Paul Eggert via tz writes: > Thanks for the info about groff. You're right, tzdb man pages are supposed > to be portable to both groff and traditional troff. For the latter I test > with /usr/bin/nroff and /usr/bin/troff on Solaris 10, which is the oldest > troff I know that is still supported.

Re: Doubts about a typo fix

Hi Paul, At 2022-11-25T18:18:46-0800, Paul Eggert wrote: > Thanks for the info about groff. You're right, tzdb man pages are > supposed to be portable to both groff and traditional troff. For the > latter I test with /usr/bin/nroff and /usr/bin/troff on Solaris 10, > which is the oldest troff I kn

Re: [tz] Doubts about a typo fix

On 2022-11-25 19:20, Russ Allbery wrote: You have to be very careful with the combination of \f(CW and \fP on Solaris 10 nroff That should be OK, as \f(CW - which is now \f(CR - is used only if \n(.g is nonzero, i.e., only if it's groff and not traditional troff. I toyed with using \f[CW] in

Re: [PATCH v2 3/4] zic.8: Use correct escape sequences instead of special characters

Hi Paul, At 2022-11-25T18:31:02-0800, Paul Eggert wrote: > On 2022-11-23 10:43, Paul Eggert wrote: > > I installed that > Further testing showed that the installed patch doesn't work with > traditional troff, which doesn't support groff escape sequences like \(aq. > To fix this I installed the equ

Re: [PATCH v2 3/4] zic.8: Use correct escape sequences instead of special characters

On 2022-11-23 10:43, Paul Eggert wrote: I installed that Further testing showed that the installed patch doesn't work with traditional troff, which doesn't support groff escape sequences like \(aq. To fix this I installed the equivalent of the attached further patch to TZDB.diff --git a/zic.8

Re: Doubts about a typo fix

Thanks for the info about groff. You're right, tzdb man pages are supposed to be portable to both groff and traditional troff. For the latter I test with /usr/bin/nroff and /usr/bin/troff on Solaris 10, which is the oldest troff I know that is still supported. On 2022-11-23 13:40, G. Branden R

Re: gropdf paper format diagnostic message and rev{i,er}sion plans (was: gropdf landscape orientation support)

Hi Deri, At 2022-11-25T16:25:53+, Deri wrote: > I will be releasing change to the error message when a download font > is unavailable. Two versions, one for a non-existent file and one for > not readable, along the lines you suggested. These will also trigger a > non-zero exit code when run is

Re: gropdf paper format diagnostic message and rev{i, er}sion plans (was: gropdf landscape orientation support)

On Friday, 25 November 2022 03:20:32 GMT G. Branden Robinson wrote: > Hi Deri, > > Can you bring me up to speed with what you're working on, or what you're > waiting on me to do? My recollection of last Friday was that we were > deadlocked, but that I yielded by pushing 3 reversions. Please feel

Re: [groff] 08/21: [me]: Integrate better with papersize.tmac.

Hi Dave, At 2022-11-19T10:16:30-0600, Dave Kemper wrote: > > * tmac/e.tmac: Integrate better with papersize.tmac by no longer > > forcing line (and title) length to 6 inches for typesetters on > > initialization. > > This is largely a step forward for the -me package, but I have t

Re: Unexpected behaviour when using linenumbering and tbl

Hi Hans, At 2022-11-24T19:47:35+0100, hbezemer--- via wrote: > When I make exams I sometimes use linenumbering so I can refer to a > specific line of a source. I noticed some unexpected behaviour when > having a table after the part that has linenumbers. The table also > gets linenumbers added,