Werner LEMBERG <[EMAIL PROTECTED]>:
> Do you see any disadvantage? Can you check your man page corpus
> whether authors ever use a combination of .IP/.LP/.PP/.P/.HP just for
> the purpose of getting two empty lines?
I have *never*, in fact, seen this done. If it were to happen, the doclifter
tr
"Eric S. Raymond" <[EMAIL PROTECTED]>, 2007-02-04 03:14 -0500:
> Werner LEMBERG <[EMAIL PROTECTED]>:
> > Do you see any disadvantage? Can you check your man page corpus
> > whether authors ever use a combination of .IP/.LP/.PP/.P/.HP just for
> > the purpose of getting two empty lines?
>
> I ha
Michael(tm) Smith <[EMAIL PROTECTED]>:
> is valid. It's not required to have content.
> A instance won't generate validation errors.
Huh? About a week ago I tried a change to the way I handled list terminations
and xmllint complained biiterly about .
--
http://www.catb.org/~esr
> > I suspect the .SCRIPT-INPUT-BEGIN .SCRIPT-INPUT-END could
> > be implemented as macros which map onto a similar escape
> > technique as the suppression escapes \O etc. In any event
> > the obvious advantage to this approach is that one can
> > harness the ability of a scripting language to m
Tadziu Hoffmann <[EMAIL PROTECTED]>:
> We also just _might_ write a *roff interpreter in Python and
> skip groff altogether.
doclifter has large portions of a troff interpreter inside it,
because it has to :-).
> Ah, but it's not quite as trivial as it initially appears.
> You can't just transla
I'd like to have all eqn terms appear in a single colour.
gfont chooses the eqn font, but there appears no easy way to have all
en terms appear in a specific colour.
Any suggestions?
Thanks,
Bob
--
Robert MARKS, Australian Graduate School of Management,
UNSW SYDNEY, NSW 2052, Austr
