From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: newlib@sourceware.org
Subject: Re: [PATCH 0/2] newlib/libc/time/strftime: table format fix man, tbl, groff multi-page table issues
Date: Thu, 23 Feb 2023 08:12:49 -0700 [thread overview]
Message-ID: <115a1e69-4265-e1cd-afca-db6f09196ee6@Shaw.ca> (raw)
In-Reply-To: <8ec9372f-2bc9-919d-cd04-3ef3d71020d9@dronecode.org.uk>
On 2023-02-22 13:10, Jon Turney wrote:
> On 20/02/2023 23:20, Brian Inglis wrote:
>> On 2023-02-20 15:03, Jon Turney wrote:
>>> On 20/02/2023 20:25, Brian Inglis wrote:
>>>> On 2023-02-20 02:45, Corinna Vinschen wrote:
>>>>> Hi Brian,
>>>>>
>>>>> On Feb 17 13:49, Brian Inglis wrote:
>>>>>> Brian Inglis (2):
>>>>>> newlib/libc/time/strftime.c: split table of conversion
>>>>>> specifiers to fix man, tbl, groff multi-page table issues
>>>>>> newlib/libc/Makefile.inc: sed fix strftime.3 table format
>>>>>> man, tbl, groff multi-page issues
>>>>>>
>>>>>> newlib/libc/time/strftime.c | 3 ++-
>>>>>> newlib/libc/Makefile.inc | 1 +
>>>>>> 2 files changed, 3 insertions(+), 1 deletion(-)
>>>>>>
>>>>>> --
>>>>>> 2.39.0
>>>>>
>>>>> Would you mind terribly to add more text to the commit messages?
>>>>> explaining the problem, and its fix? Just the subject line is quite
>>>>> terse.
>>>>>
>>>>> For patch 1, why adding the split and what's the desired effect. For
>>>>> patch 2, what problem is the sed call fixing and what is the sed
>>>>> expression doing?
>>>>
>>>> Thanks Corinna, You're right - will redo all v3.
>>>
>>> You should also describe why this must be fixed in this ad-hoc fasion, rather
>>> than in the chew markup or makedocbook.
>>
>> I'll also ref the discussion with Branden, following comments from linux-man,
>> the newlib man generation by docbook2man is incompatible with how man is
>> incompatible with groff/tbl/grohtml:
>>
>> https://lists.gnu.org/archive/html/bug-groff/2023-02/msg00118.html
>
> Thanks, interesting reading.
>
>> via makedocbook python script which generates xml (attached), then
>> docbook generates html, man pages, PDFs, texinfo, and the latter
>> generate libc info.]
>
> This statement of yours is incorrect:
>
> The embedded documentation is processed ('chewed') by makedoc into texinfo, from
> which html, info and PDFs are generated.
>
> The embedded documentation is also processed by makedocbook into docbook from
> which manpages are generated.
I realized I switched them due to similar names and possibly ToD or coffee lack.
> Whatever you think of docbook as a pivot format for generating the manpages,
> texinfo is much worse.
Not my opinion - I don't mind GMLs or roffs - BTDT.
> In theory you could use makedocbook as a starting point for directly outputting
> groff manpages, if that's the only way to generate manpages of the quality desired.
>
>> I dug and could not find a good point to alter generation of tables > page
>> size that may not adversely affect other [newlib] doc man page tables, where
>> the problem occurs solely on that strftime.3 man page!
>
> These seem like generic problem in the docbook2man XSLT, which should be fixed
> there.
The problem is man -> tbl -> groff - see other reply.
It may be fixed in groff v + 2.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-02-23 15:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 20:49 Brian Inglis
2023-02-17 20:49 ` [PATCH 1/2] newlib/libc/time/strftime.c: split table of conversion specifiers to " Brian Inglis
2023-02-17 20:49 ` [PATCH 2/2] newlib/libc/Makefile.inc: sed fix strftime.3 table format man, tbl, groff multi-page issues Brian Inglis
2023-02-18 16:54 ` [PATCH v2 " Brian Inglis
2023-02-20 9:45 ` [PATCH 0/2] newlib/libc/time/strftime: table format fix man, tbl, groff multi-page table issues Corinna Vinschen
2023-02-20 20:25 ` Brian Inglis
2023-02-20 22:03 ` Jon Turney
2023-02-20 23:20 ` Brian Inglis
2023-02-22 20:10 ` Jon Turney
2023-02-23 15:12 ` Brian Inglis [this message]
2023-02-21 4:17 ` [PATCH v3 0/2] newlib/libc/time/strftime: fix multi-page table format issues Brian Inglis
2023-02-21 4:18 ` [PATCH v3 1/2] newlib/libc/time/strftime.c: split chew table of conversion format specifiers Brian Inglis
2023-02-21 4:18 ` [PATCH v3 2/2] newlib/libc/Makefile.inc: sed fix strftime.3 tbl/groff format issues Brian Inglis
2023-02-21 9:15 ` [PATCH v3 0/2] newlib/libc/time/strftime: fix multi-page table " Corinna Vinschen
2023-02-22 20:10 ` Jon Turney
2023-02-23 0:03 ` Brian Inglis
2023-02-23 15:33 ` Brian Inglis
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=115a1e69-4265-e1cd-afca-db6f09196ee6@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=newlib@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).