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:
OpenPGP_signature
Description: OpenPGP digital signature