On 4/4/23, G. Branden Robinson wrote:
> At 2023-04-04T16:26:30+, Michał Kruszewski wrote:
>> pdfroff has .pdfinfo, how to achieve the same with groff?
>
> groff's pdf output driver supports it as well, with the same syntax I
> think; but to my surprise it is not documented in the gropdf(1) man
Hi Alex,
I endorse Dave's critique of your measurement. But it was interesting
to me to observe the performance of GNU troff and grotty with literally
billions of lines of input.
At 2023-05-09T15:37:16-0500, Dave Kemper wrote:
> (I can already hear the questions. "Why is the terminal basic unit
On 5/10/23, G. Branden Robinson wrote:
> But it was interesting
> to me to observe the performance of GNU troff and grotty with literally
> billions of lines of input.
I agree, though it wasn't a completely realistic test, with each line
having only one word on it: no filling, no adjusting (thoug
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 AT&T
troff's .ss units, which are a fixed 1/36 em.
This dif
On 5/8/23, Douglas McIlroy wrote:
> K-P would not be a mere add-on to groff. K-P knows in advance the
> shape of the space into which a paragraph must fit, but groff doesn't.
> This means a whole lot of groff state must be carried along with the
> K-P dynamic program.
I don't doubt your analysis
