Re: Ping^1: Chapters of the manual (was: Bug#1018737: /usr/bin/rst2man: rst2man: .TH 5th field shouldn't be empty)

[Alejandro Colomar <alx.manpages@gmail.com>]

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

Hi Deri,

On 12/17/22 02:04, Deri wrote:
> On Friday, 16 December 2022 19:31:41 GMT Alejandro Colomar wrote:
>> Hi Deri!
>>
>> On 12/16/22 20:13, Deri wrote:
>>> On Sunday, 11 December 2022 19:21:27 GMT Alejandro Colomar wrote:
>>>> Since I'll some day (likely for 6.02, that's 2 years from now) be
>>>> publishing the Linux man-pages as a single-volume PDF, the term chapter
>>>> will regain significance.
>>>
>>> Hi Alejandro,
>>>
>>> I saw this on the groff list and wondered what would be involved, so I
>>> cloned the git from your website
>>
>> I guess you mean <//www.alejandro-colomar.es/src/>, right?  I guess so,
>> since the MR branch is only there.
>>
>>> and wrote a perl script, plus a few customisations
>>> of groff tmacs, and produced the attached pdf.
>>
>> Wow!  It looks really nice!
>>
>> I noticed a few small issues:
>>
> Hi Alex,
> 
>> -  link (.so) pages appear misplaced in the navigation.  For example
>> writev.2 appears inside man2type.
>>
>> -  intro(*) should be the first page of each section.  (So far, subsections
>> don't have intro, but I wouldn't discard that.)
> 
> Both fixed in latest version. Which you can find here:-
> 
> http://chuzzlewit.co.uk/LinuxManBook.pdf

It looks great!  We could release it already :)

> 
>>> You will notice all the internal .MR calls are working.
>>
>> Yep
>>
>>> It is not perfect yet,
>>> but I thought I would let you see how far I have got, and find out whether
>>> this is something you would like contributed.
>>
>> Sure!  We can even merge something already.  I doesn't need to be perfect at
>> the begining.  Is perl necessary, or could it be transformed into a shell
>> script? I'm not comfortable at maintaining a perl script.
> 
> I think it may be a bit beyond a shell script, but I am not an accomplished
> shell script programmer. I am hoping it will end up as part of your build.

Please send your perl script as a patch, adding it to the <scripts/> directory. 
Put your copyright and your preferred license, and we can work from there to 
transform it into something I can better understand.  I'll probably be asking 
you many questions :)

Cheers,

Alex

> 
> Cheers
> 
> Deri
> 
>>> I would welcome any views on
>>> what I have done so far.
>>
>> It looks great.  I'd like to hook it into the build system, so we can `make
>> build-pdf` and generate it.
>>
>>> In case you don't know, I'm the chap who developed the groff pdf driver.
>>
>> Yep, I know
>>
>>> Cheers
>>>
>>> Deri
>>
>> Cheers,
>>
>> Alex
> 
> 
> 
> 

-- 
<http://www.alejandro-colomar.es/>

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