On Sat, Mar 07, 2015, Doug McIlroy wrote:
> I was surprised to learn that distributed macro packages
> aren't the "real thing", but only shadows left by a complex
> build process. The given reason was unpersuasive, so I ran an
> experiment.
>
> I made a copy of s.tmac with 10 spaces after each ini
>> So it looks to me as if the policy of distributing mildly
>> compressed macro packages has only two perceptible effects: it
>> complicates maintenance and it complicates understanding. I am
>> thus led to believe that this is yet another instance of ungainly
>> galloping gnus departing from Uni
> [...] that this is yet another instance of ungainly galloping
> gnus departing from Unix's original path of simplicity and
> transparency.
Not really. Unix nroff had an option to create a "compacted"
version of a macro package, which was used because the compacted
file had a significantly redu
Hi Peter,
I see that UNDERSCORE macro definition has been made shorter in code
repository. But it still brings an extra unwanted space after the
underscored text, which becomes more visible and annoying especially when
followed by a punctuation, e.g.
one
.UNDERSCORE "uno"
, two
My suggestion is
I'm writing a document parser which outputs to groff to be processed with
gropdf.
When the parse document contains unicode ellipsis (u+2026), it goes fine
with few groff fonts, namely Times, Helvetica, Courier.
But with Palatino and the rest, the document breaks when processed with
gropdf, emits th
> I'm writing a document parser which outputs to groff to be processed
> with gropdf. When the parse document contains unicode ellipsis
> (u+2026), it goes fine with few groff fonts, namely Times,
> Helvetica, Courier. But with Palatino and the rest, the document
> breaks when processed with gro
