From: Alejandro Colomar <alx@kernel.org>
To: Deri <deri@chuzzlewit.myzen.co.uk>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org, Brian.Inglis@shaw.ca
Subject: Re: No 6.05/.01 pdf book available
Date: Mon, 14 Aug 2023 19:37:26 +0200 [thread overview]
Message-ID: <04e326c5-1bfa-357f-cce1-d3315615fe86@kernel.org> (raw)
In-Reply-To: <21985157.EfDdHjke4D@pip>
[-- Attachment #1.1: Type: text/plain, Size: 4633 bytes --]
Hi Deri, Branden,
On 2023-08-14 18:06, Deri wrote:
[...]
> Line missing in the bespoke an.tmac I provided, new version attached.
Thanks; will try.
> I know
> Alex wants to run against a stock version of groff, with minimal
> customisation, and, once my branch is merged, there will be further pruning,
> but unless you add to Branden's wish list to include an ability to control the
> hierarchy of the bookmark panel, you will need a customised an.tmac. The
> reason is because the stock an.tmac has a hard coded hierarchy where the .TH
> line is given level 1 but as you want to have separate sections these need to
> be level one and everything else is moved up a level. Of course this just
> means making the starting level configurable on the command line, i.e.
> -r startbkmk=2 or some such.
Deri's wish is my wish :)
> 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.
[...]
>
> Fonts
>
> There are 2 reasons I included fonts in the build environment:-
>
> A) The man pages which define the various iso-8859 pages contain many glyphs
> which are not defined in the standard groff fonts, so I used the Tinos font
> from google which improves the coverage. If you want to get rid of the fonts,
> and rely on just the fonts in groff, you can change line 4 of anmark.tmac to:-
>
> .special S U-TR
>
> Which is an improvement on the standard fonts, and should be available as
> standard if the URW fonts were found when groff was built. You will see
> differences in iso-8859-7 and iso-8859-8 for example.
I'll try. I wouldn't want to make those ISO-8859 pages useless, though.
>
> B) If you build the LinuxManBook using the 1.23.0+ flavour (with the newer
> gropdf that produces a substantially smaller pdf) it requires a slightly
> different font format so needs the embedded font directory. If you have
> installed groff from the deri-gropdf-ng the new format fonts will have been
> installed, so the embedded font directory can be removed.
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?
>
> 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. :)
>
> 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
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-08-14 17:38 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 [this message]
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
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=04e326c5-1bfa-357f-cce1-d3315615fe86@kernel.org \
--to=alx@kernel.org \
--cc=Brian.Inglis@shaw.ca \
--cc=deri@chuzzlewit.myzen.co.uk \
--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 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).