linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Deri <deri@chuzzlewit.myzen.co.uk>,
	linux-man@vger.kernel.org, Brian.Inglis@shaw.ca
Subject: Re: No 6.05/.01 pdf book available
Date: Tue, 22 Aug 2023 00:02:35 +0200	[thread overview]
Message-ID: <54945a93-399e-620f-be6e-bbe740abb21e@kernel.org> (raw)
In-Reply-To: <3262525.44csPzL39Z@pip>


[-- Attachment #1.1: Type: text/plain, Size: 2661 bytes --]

Hi Deri,

On 2023-08-21 01:39, Deri wrote:
> Hi Brian,
> 
> I have created the tar files again with the latest sort.
> 
> Both are intended to be used with groff 1.23.0, but the plus version includes 
> the latest gropdf, so produces more compact output. It also has the narrower 
> gap between the heading on the intro(1) page, I have not investigated the 
> reason yet!
> 
> Also I have a small bone to pick with your "official" sort order - it's not 
> consistent. Most people expect a short word like "cat" to appear before a word 
> like "catatonic", and we see "hosts" does appear before "hosts.equiv", so why 
> does "man" come after "man-pages"! I've also strayed from the official sort 
> order in the 6.05.01 pdf by arranging the latin and iso character code pages 
> in proper numerical order so "latin10" comes after "latin9" rather than 
> following "latin1". I hope this makes sense.

Is "official" the Book for 6.5.1?  Or is it the scripts/sortman in git HEAD?

I've found that scripts/sortman had this problem that you report, and fixed it:

commit a04e93998bebba77ac799dd89c11042c25f2e2d2 (HEAD -> master, korg/master, alx/main, main)
Author: Alejandro Colomar <alx@kernel.org>
Date:   Mon Aug 21 23:55:18 2023 +0200

    scripts/sortman: Sort 'cat' before 'catatonic'
    
    Reported-by: Deri James <deri@chuzzlewit.myzen.co.uk>
    Cc: Brian Inglis <Brian.Inglis@Shaw.ca>
    Signed-off-by: Alejandro Colomar <alx@kernel.org>

diff --git a/scripts/sortman b/scripts/sortman
index 546a7943d..a8f70bab5 100755
--- a/scripts/sortman
+++ b/scripts/sortman
@@ -7,8 +7,9 @@ sed   -E '/\/intro./  s/.*\.([[:digit:]])/\10\t&/' \
 | sed -E '/\/intro./! s/.*\.([[:digit:]])\>/\11\t&/' \
 | sed -E '/\/intro./! s/.*\.([[:digit:]])([[:alpha:]][[:alnum:]]*\>)/\12.\2\t&/' \
 | sed -E '            s/\t(.*)/&\n\1/' \
+| sed -E '/\t/        s/\.[[:digit:]]([[:alpha:]][[:alnum:]]*)?\>.*//' \
 | sed -E '/\t/        s/\/[_-]*/\//g' \
 | sed -E '/\t/        s/[_-]/_/g' \
 | sed -E '/\t/        {N;s/\n/\t/;}' \
-| sort -fV \
+| sort -fV -k1,2 \
 | cut -f3;


$ ./scripts/sortman << __EOF__
man7/cat.7
man7/catatonic.7
man7/cat_or_dog.7
man7/cat_alike.7
man7/hosts.7
man7/hosts.equiv.7
man7/intro.7
__EOF__
man7/intro.7
man7/cat.7
man7/catatonic.7
man7/cat_alike.7
man7/cat_or_dog.7
man7/hosts.7
man7/hosts.equiv.7

Is this order a good one?  Should maybe cat_alike go right after cat?

Cheers,
Alex

[Hopefully, this email should already be signed; I've recovered my keys.]

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


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

  parent reply	other threads:[~2023-08-21 22:02 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07  1:16 [PATCH] scripts/LinuxManBook/gropdf: use symlink instead of hard coded groff version Brian Inglis
2023-08-07  2:46 ` No 6.05/.01 pdf book available Brian Inglis
2023-08-07  8:45   ` Alejandro Colomar
2023-08-07  9:16     ` Alejandro Colomar
2023-08-07 16:21       ` Brian Inglis
2023-08-12  0:02         ` Alejandro Colomar
2023-08-12  1:48           ` G. Branden Robinson
2023-08-12 21:32             ` Alejandro Colomar
     [not found]     ` <21975186.EfDdHjke4D@pip>
2023-08-11 23:51       ` Alejandro Colomar
2023-08-12  3:04         ` G. Branden Robinson
2023-08-12 21:33           ` Alejandro Colomar
2023-08-12 17:02       ` Brian Inglis
2023-08-12 20:02         ` Deri
2023-08-13 20:30           ` Brian Inglis
2023-08-13 20:47             ` Alejandro Colomar
2023-08-13 21:55               ` G. Branden Robinson
2023-08-13 22:45                 ` Alejandro Colomar
2023-08-13 22:18               ` Alejandro Colomar
2023-08-14  6:49                 ` Brian Inglis
2023-08-14 10:46                   ` Alejandro Colomar
2023-08-13 21:47             ` hyphens at ends of pages (was: No 6.05/.01 pdf book available) G. Branden Robinson
2023-08-14  5:28               ` Brian Inglis
2023-08-14 16:06             ` No 6.05/.01 pdf book available Deri
2023-08-14 17:37               ` Alejandro Colomar
2023-08-14 20:01                 ` Alejandro Colomar
2023-08-14 21:22                   ` Deri
2023-08-14 21:32                     ` Alejandro Colomar
2023-08-14 23:26                       ` Deri
2023-08-14 21:40                 ` Deri
2023-08-15  0:50                   ` groff features for hyperlinked man pages (was: No 6.05/.01 pdf book available) G. Branden Robinson
2023-08-15 10:34                     ` G. Branden Robinson
2023-08-18 13:50                     ` Alejandro Colomar
2023-08-19  4:37                       ` G. Branden Robinson
2023-10-01 12:02                         ` Alejandro Colomar
2023-08-18 10:29                   ` No 6.05/.01 pdf book available Alejandro Colomar
2023-08-15  0:34               ` Brian Inglis
2023-08-20 16:48                 ` Deri
2023-08-20 18:54                   ` Alejandro Colomar
2023-08-20 19:06                   ` Brian Inglis
     [not found]                     ` <3262525.44csPzL39Z@pip>
2023-08-21 22:02                       ` Alejandro Colomar [this message]
2023-08-21 23:10                         ` Deri
2023-08-21 23:45                         ` Brian Inglis
2023-08-28 12:17                           ` Alejandro Colomar
2023-08-28 18:24                             ` Brian Inglis
2023-08-28 21:11                               ` Alejandro Colomar
2023-08-07  8:29 ` [PATCH] scripts/LinuxManBook/gropdf: use symlink instead of hard coded groff version Alejandro Colomar
2023-08-07 15:01 ` Brian Inglis
2023-08-11 23:57 ` Alejandro Colomar

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=54945a93-399e-620f-be6e-bbe740abb21e@kernel.org \
    --to=alx@kernel.org \
    --cc=Brian.Inglis@shaw.ca \
    --cc=deri@chuzzlewit.myzen.co.uk \
    --cc=linux-man@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).