From: Deri <deri@chuzzlewit.myzen.co.uk>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, Brian.Inglis@shaw.ca
Subject: Re: No 6.05/.01 pdf book available
Date: Mon, 14 Aug 2023 22:40:31 +0100 [thread overview]
Message-ID: <8264634.T7Z3S40VBb@pip> (raw)
In-Reply-To: <04e326c5-1bfa-357f-cce1-d3315615fe86@kernel.org>
On Monday, 14 August 2023 18:37:26 BST Alejandro Colomar wrote:
> Hi Deri, Branden,
>
[...]
>
> > 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.
>
> Is this really needed? Can't gropdf just translate them internally? Say,
> do unconditionally the equivalent of `| tr - _ |` or something like that.
See other email.
[...]
>
> Do you have an estimate of how long your branch could take to merge?
> As in, more than a month or less than a month?
I'm really hoping Branden's going to help me with that, I think he intimated
that he might when he suggested I start a branch for the work. I have one more
push to the branch to do, but I need to contact Peter since there is a minor
tweak to om.tmac to make expandos work in mom.
> > Makefile
> >
> > The simplest option would be to add a new rule to the Makefile which is
> > dependent on all the man pages have been built, and cd's into the scripts/
> > LinuxManBook directory and calls the program with the location where the
> > man pages exist. However, I suspect Alex fancies something more
> > complicated by replacing the perl with a hybrid of shell command and make
> > magic.
>
> You suspect well. :)
Just like my wife, she often tells me I'm "No longer required on the
journey!". :-)
Cheers
Deri
> > I attach a new copy of BuildLinuxMan.pl which is an amalgam of mine and
> > Brian's code. This has the new -paper flag.
> >
> > Alex's MR branch
> >
> > The new program now recognises existing .MR's in the document and provides
> > the "clean" destination name, so it should run against the new branch.>
> >> nodemask ... on-
> >> ...
> >> line, ...
> >>
> >> There appear to be 24 single word instances of online and 12 outdated
> >> hyphenated compound word instances of on-line across all man pages.
> >>
> >> UI: I also noticed, while looking for tables to compare, that pages are
> >> ordered by filename not like rpmvercmp/ls -v/RPM::VersionSort e.g
> >> ISO_8859-2 is after ISO_8859-16 which may not be as expected.
> >> Used rpmvercmp in last line of perl sub sortman and works as expected.
> >
> > I have used Sort::Versions (see above), thanks for the suggestion.
> >
> >> Tech nitpick: .Z is still recognized by GUIs as compress output
> >> (UNIX-compressed file) - is there no other file type suffix used for
> >>
> >> ditroff intermediate output? Aha - Alex says .set:
> >> https://lists.gnu.org/archive/html/groff/2023-04/msg00213.html
> >
> > Well, that's settled.
> >
> >> Added variables and changed those also in BLM-letter.pl: copy attached.
> >>
> >>> Thanks for your help.
> >>
> >> Happy to help in any way.
> >
> > Hope you're happy with this version.
>
> Let's open the improved Christmas present! :D
>
> Cheers,
> Alex
next prev parent reply other threads:[~2023-08-14 21:41 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 15:01 ` 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 [this message]
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
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-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=8264634.T7Z3S40VBb@pip \
--to=deri@chuzzlewit.myzen.co.uk \
--cc=Brian.Inglis@shaw.ca \
--cc=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--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 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.