On Monday, 14 August 2023 21:01:46 BST Alejandro Colomar wrote: > On 2023-08-14 19:37, Alejandro Colomar wrote: > >> Another change which would need to be accepted is > >> to allow a fourth parameter to .MR which is the destination name. > >> Normally the name of the destination is derived from the first two > >> parameters concatenated with "_", but if the name part of the .MR call > >> to the man page includes non- ascii characters (such as ".MR > >> my\-lovely\-page 7 ,") then it needs to provide a "clean" destination > >> name. > > I just re-read this, and am confused. '\-' is an ASCII character, isn't it? > In fact, all of the Linux man-pages pathnames are composed exclusively of > ASCII characters, aren't they? Hi Alex, You are correct, but it is not relevent since we are talking about the LinuxManBook. In this context .MR is a pointer to another page in the pdf, this is termed an internal reference, it could be forward or backwards within the pdf. If you look at the keyrings(7) man page you see examples such as:- .SH SEE .ad l .nh .BR keyctl (1), .BR add_key (2), .BR keyctl (2), .BR request_key (2), .BR keyctl (3), .BR keyutils (7), .BR persistent\-keyring (7), .BR process\-keyring (7), .BR session\-keyring (7), .BR thread\-keyring (7), .BR user\-keyring (7), .BR user\-session\-keyring (7), .BR pam_keyinit (8), .BR request\-key (8) .PP Which when converted to .MR calls looks like:- .SH SEE ALSO .ad l .nh .MR "keyctl" "1" "," "keyctl" .MR "add_key" "2" "," "add_key" .MR "keyctl" "2" "," "keyctl" .MR "request_key" "2" "," "request_key" .MR "keyctl" "3" "," "keyctl" .MR "keyutils" "7" "," "keyutils" .MR "persistent\-keyring" "7" "," "persistent-keyring" .MR "process\-keyring" "7" "," "process-keyring" .MR "session\-keyring" "7" "," "session-keyring" .MR "thread\-keyring" "7" "," "thread-keyring" .MR "user\-keyring" "7" "," "user-keyring" .MR "user\-session\-keyring" "7" "," "user-session-keyring" .MR "pam_keyinit" "8" "," "pam_keyinit" .MR "request\-key" "8" "" "request-key" .PP On the keyrings(7) page in the pdf you should be able to see the difference between HYPHEN (U+2010), which is what \- becomes, and HYPHEN-MINUS (U+002D) which is the ascii character. The problem is that the MR request is a bit naughty in that it uses the first two parameters for two purposes, first it is used as a destination, but it is also output as text. So as text it may contain escapes to enhance the typography, for example using \- for a better looking hyphen. It is not my job to impose artificial restrictions on how a man page author wants his creation to look, better to separate the two purposes, so there is no restriction. > > Is this really needed? Can't gropdf just translate them internally? Say, > > do unconditionally the equivalent of `| tr - _ |` or something like that. > > > > [...] This is all happening in groff macros way before it gets to gropdf. Cheers Deri
