units used in `ss` request (was: device-dependent warnings)

2023-05-13 Thread G. Branden Robinson
At 2023-05-10T12:28:02-0500, Dave Kemper wrote: > On 5/10/23, Dave Kemper wrote: > > Nonintuitively, .ss's units aren't in fractions of standard > > typographical measurements, but 1/12 of the current font's ordinary > > space. > > And I just learned (or maybe relearned) this is a deviation from

Re: units used in `ss` request (was: device-dependent warnings)

2023-05-13 Thread G. Branden Robinson
[self-follow-up] At 2023-05-13T02:03:11-0500, G. Branden Robinson wrote: > At 2023-05-10T12:28:02-0500, Dave Kemper wrote: > > On 5/10/23, Dave Kemper wrote: > > > Nonintuitively, .ss's units aren't in fractions of standard > > > typographical measurements, but 1/12 of the current font's > > > or

a CSTR #54 erratum with `ps` request

2023-05-13 Thread G. Branden Robinson
In case anyone never noticed, > Any positive size value may be requested; if invalid, the next larger > valid size result, with a maximum of 36. Judging by the behavior of DWB 3.3 troff, this is incorrect in two respects. 1. The maximum type size is determined by the "sizes" directive in the

a bold challenge for anti-deviationists

2023-05-13 Thread G. Branden Robinson
CSTR #54 says this: > .bd F N > > The characters in font F will be artifically emboldened by printing > each one twice, separated by N - 1 basic units. A reasonable value > for N is 3 when the character size is near 10 points. If N is missing > the embolden mode is turned off. The emboldening v

Re: units used in `ss` request (was: device-dependent warnings)

2023-05-13 Thread Dave Kemper
On 5/13/23, G. Branden Robinson wrote: >> At 2023-05-10T12:28:02-0500, Dave Kemper wrote: >> > And I just learned (or maybe relearned) this is a deviation from >> > AT&T troff's .ss units, which are a fixed 1/36 em. > > I am beginning to think that it was only Ossanna troff for which that > was tr