> This reminds me of another question I'd wanted to ask about groff's
> italic-correction escapes.
>
> Why are these escapes something that a user must insert manually,
> rather than groff handling italic corrections automatically?
I think this is good old Unix philosophy...
> It is hard to imag
On 10/11/13 09:53:23, Dave Kemper wrote:
This reminds me of another question I'd wanted to ask about groff's
italic-correction escapes.
Why are these escapes something that a user must insert manually,
rather than groff handling italic corrections automatically? It is
hard to imagine a ca
> I want the typography that *I* set, not someone else's. If the price
> of this freedom is more manual intervention then it is a price I shall
> gladly pay.
Robert,
This is absolutely a worthwhile principle.
However, if you are using groff, you are already using typographic
principles that some
On 11/6/13, I wrote:
> In a number of cases, switching between Libertine Italic and Libertine
> Roman requires an italic correction. But the \/ and \, escapes, groff's
> mechanism to handle this, have no effect on the output when using the
> Libertine family.
This reminds me of another question I
Thanks, Tadziu, for all the info and the demo file! A few followups
below.
> I think this is because afmtodit assumes these ligatures will be
> called "fi", "fl", "ff", "ffi", and "ffl", but in the new fonts
> they are called "f_i", "f_l", "f_f", "f_f_i", and "f_f_l".
I see. It looks like afmto
