> It's unfortunate that there's not more development collaboration
> between groff and Heirloom troff.
The code base is *very* different; besides that, Gunnar and I tried to
harmonize various extensions to AT&T troff.
Werner
> HT's paragraph-at-once is noticeably superior to groff's
> line-at-a-time formatting paradigm, and I'd love to see it
> implemented in groff.
Volunteers welcome. I have no longer time to real groff development,
sorry.
Werner
On Mon, Nov 11, 2013, Dave Kemper wrote:
> It's unfortunate that there's not more development collaboration between
> groff and Heirloom troff.
I concur. HT's paragraph-at-once is noticeably superior to groff's
line-at-a-time formatting paradigm, and I'd love to see it
implemented in groff.
I t
On Mon, 11 Nov 2013 12:57:31 -0600
Dave Kemper wrote:
> > There is no conflict to groff's `inability' to apply it
> > automatically. What you really want is a *macro package* which does
> > the job.
>
> Well, having a macro package which does the job is certainly better
> than not having it. A
>> You're allowing your typesetting software to paginate, to fill
>> lines, to kern, to convert character sequences to appropriate
>> ligatures, to stretch spaces for justification, to hyphenate.
>
> To be a bit pedantic here, pagination is something that's not
> completely done automatically by tr
> There is no conflict to groff's `inability' to apply it automatically.
> What you really want is a *macro package* which does the job.
Well, having a macro package which does the job is certainly better than
not having it. And thanks to those who have pointed out macros which
do the job: I can
> "Printing Style Manual" by Victor C. N. Blight, Government Printer
Thanks! Out of curiosity, I just ordered a used copy.
The book costs 12 Euros, and shipping from Australia
costs 18 Euros. :-|
> You're allowing your typesetting software to paginate, to fill
> lines, to kern, to convert character sequences to appropriate
> ligatures, to stretch spaces for justification, to hyphenate.
To be a bit pedantic here, pagination is something that's not
completely done automatically by troff its
On 11/11/13 21:16:17, Tadziu Hoffmann wrote:
> The other is a musty old tome written a half-century ago, in
> the days of hot type, by the State Government Printer. This is
> my Bible for it not only tells me How it also tells me Why. It
> does not always agree with US or UK manuals, even though
> The other is a musty old tome written a half-century ago, in
> the days of hot type, by the State Government Printer. This is
> my Bible for it not only tells me How it also tells me Why. It
> does not always agree with US or UK manuals, even though there
> are certain similarities in the three
> And here's the design error: The values in the `ligatures'
> line of a groff metrics file should be *groff entities*,
> not PS glyph names.
They were already called ffi, ffl, etc. before Postscript
was invented, so it unlikely they are PS glyph names but
rather input character sequences for whi
>> It should be fairly straightforward to add new hard-coded ligatures
>> to the groff source, and to afmtodit.
>
> Well, the concept of ligatures in the today's font world is much more
> complex than 30 years ago, so extending hard-coded values is a no-go
> IMHO.
I agree, in principle. My thinki
12 matches
Mail list logo
