All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
	Time zone mailing list <tz@iana.org>,
	dickey@his.com, linux-man@vger.kernel.org
Subject: Re: [PATCH v2] tzfile.5: Fix indentation
Date: Mon, 18 Mar 2024 09:35:07 +0100	[thread overview]
Message-ID: <Zff8pT_1eWttIGPi@debian> (raw)
In-Reply-To: <d39d2de7-52f8-4231-8863-2706ed89c827@cs.ucla.edu>

[-- Attachment #1: Type: text/plain, Size: 3903 bytes --]

[looping in linux-man@, as we discuss about improvements in the Linux
 man pages' PDF book]

Hi Paul,

On Sun, Mar 17, 2024 at 09:59:41PM -0700, Paul Eggert wrote:
> On 2024-03-17 15:20, Alejandro Colomar wrote:
> 
> > In case you want to have a quick look at how it looks, here's an example
> > from the Linux man-pages:
> > 
> > <https://www.alejandro-colomar.es/share/dist/man-pages/git/HEAD/man-pages-HEAD.pdf#pdf%3Abm12325>
> 
> Yes, unfortunately that looks subpar to me. There's too much space between
> the bullets and the text they're bulleting. For example, in the last page of
> man-pages(7) the bullets should be indented with respect to the parent text,
> and there should be less space between the bullets and the text. Much better
> is what tzfile(5) does now (see attached); this is particularly important
> when something is nested under the bullet level, as it is in tzfile(5). The
> current tzfile(5) bulleting approach is closer to how Joe Ossanna used
> bullets in section 7.2 of the Nroff/Troff User's Manual (1976)[1], which is
> what I learned troff from. (Ossanna doesn't subindent so his larger indents
> are not that much of a problem in the manual, but tzfile(5) needs to
> subindent.)

Hmm, while Ossana's indents might be a bit excessive, TZDB's might be
too short.  Maybe I would RS 4 spaces instead of 2 before the tag.
Maybe you being used to programs with 2 spaces and me with 1 tab means
we have our brains hard-wired for different indentation width
preferences.  But I kind of do like pre-indenting bullets; in some cases
I've felt that having the bullets not indented was sub-par, but wasn't
convinced enough to go and pre-indent them, since that would add
complexity, and also allow less room for text in terminals.

> There are other things not to like about the man page PDF output. The man
> pages are confused about when to use constant-width fonts vs varying-width
> fonts.

Can you please point to an example of this?  I try to be consistent, but
probably there are still cases that I haven't fixed due to lack of time.

> The lines are too long to read comfortably; this is inherent to how a
> good font squeezes in more text.

I'm not sure I understand this.  Do you mean there are too many letters
in a line in the Linux man-pages PDF or too few?

If we compare
<https://www.alejandro-colomar.es/share/dist/man-pages/git/HEAD/man-pages-HEAD.pdf#tzfile.5>
with the PDF you attached to your email, you can see there are less
words in a line in the Linux man-pages PDF than in yours.  Also, your
PDF has slightly less margins.

When I first saw the PDF book, I had a feeling that lines were too long,
and that a larger/better font might be necessary.

> Indents are too large in general. The PDF
> man pages should be formatted for smaller pages, or with tons more margin,
> or two-column, or something. Of course I realize we can't fix all this, as
> there's long tradition of hasty and/or bad formatting dating back to 7th
> Edition Unix man pages. Still, if someone wants to make little improvements
> we should let them.

Sure.  I do accept improvements for that.  If you have more specific
suggestions, or even patches, they're welcome!

> > Surprising as it may be, Debian's man2html(1) could
> > handle (probably by ignoring them; I didn't really check) previous uses
> > of \w, but started crashing with \w in IP.  Did you receive a copy of
> > the Debian bug report?
> 
> I followed up separately to that. In short, that man2html appears to be
> unmaintained upstream and should be retired, but I sent in a patch anyway.

Thanks.

Have a lovely day!
Alex

> [1]: https://www.tuhs.org/Archive/Documentation/Manuals/Unix_4.0/Volume_1/C.1.2_NROFF_TROFF_Users_Manual.pdf



-- 
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

       reply	other threads:[~2024-03-18  8:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240317124350.96716-1-alx@kernel.org>
     [not found] ` <b01d6dcd-81ce-4da2-9186-0003069a1c33@cs.ucla.edu>
     [not found]   ` <20240317190642.qozzibfnfrqbhued@illithid>
     [not found]     ` <0d79c040-ee97-4e1b-a478-d4fceafb23ad@cs.ucla.edu>
     [not found]       ` <ZfdsoDbomdrjp5o6@debian>
     [not found]         ` <d39d2de7-52f8-4231-8863-2706ed89c827@cs.ucla.edu>
2024-03-18  8:35           ` Alejandro Colomar [this message]
2024-04-08  6:33             ` [PATCH v2] tzfile.5: Fix indentation Paul Eggert
2024-04-08  8:31               ` Alejandro Colomar
2024-04-08 15:59                 ` G. Branden Robinson
2024-04-08 17:22                   ` Alejandro Colomar
2024-04-08 17:46                 ` Paul Eggert
2024-04-08 19:56                   ` [tz] " Paul Eggert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Zff8pT_1eWttIGPi@debian \
    --to=alx@kernel.org \
    --cc=dickey@his.com \
    --cc=eggert@cs.ucla.edu \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=tz@iana.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.