Re: [Groff] Nesting font macros in man pages

[John Gardner]

>
> *By mixing low-level roff(7) syntax into your mdoc(7) document, like
> defining*

*your own macros, you gratuitiously endanger portability.*

...

*You are being selfish. If you forcefully redefine standard macros, the
> result*

*will look unnatural to *everyone else**


Some documents I write are for personal use, or written recreationally.
E.g., this
<https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/arc>
was
made for amusement when I got sick of loading the same slow-loading (and
cluttered) page in a browser. Since I've been referencing that particular
page very frequently lately, it's actually proven quite convenient. Were I
documenting a C library or system documentation in mdoc, well... I know
better than to get carried away scratching personal itches. =)

*Manuals tend to have so much font jumping anyway that they*

*are **often* *not very visually pleasing and look noisy.*


True. Unfortunately, these manuals tend to be written by programers with
little to no knowledge of typography or design. Thankfully, I'm not one of
them. =)





On 1 May 2017 at 00:58, Ralph Corderoy <address@hidden> wrote:

> Hi,
>
> Ingo wrote:
> >     Manuals tend to have so much font jumping anyway
> >     that they are often not very visually pleasing and look noisy.
>
> That's true.  And my crude understanding of typography is that
> 𝑖𝑡𝑎𝑙𝑖𝑐 is
> normally used for emphasis, with 𝐛𝐨𝐥𝐝 being kept in reserve for that
> odd
> time when the reader wants to find, or be attracted to, that term in a
> page of otherwise non-bold text.
>
> --
> Cheers, Ralph.
> https://plus.google.com/+RalphCorderoy
>
>