public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Cc: Jon TURNEY <jon.turney@dronecode.org.uk>
Subject: Re: [PATCH v3 0/2] newlib/libc/time/strftime: fix multi-page table format issues
Date: Tue, 21 Feb 2023 10:15:34 +0100	[thread overview]
Message-ID: <Y/SLtmUi8dilWqCL@calimero.vinschen.de> (raw)
In-Reply-To: <20230221041801.51970-1-Brian.Inglis@Shaw.ca>

Jon,

I'd like your GTG on the patchset before merging it.


Thanks,
Corinna

On Feb 20 21:17, Brian Inglis wrote:
> Discussion about why 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
> 
> There does not appear to be good way to deal in docbook2man processing
> with generation of tables > "page" size, or that may not adversely affect
> other [newlib] doc man page tables, as the problem occurs solely on the
> strftime.3 man page!
> 
> The imminent groff/tbl release fixes a number of tbl issues, so may
> affect man pages with tables differently.
> 
> The following groff/grohtml release plans to change grohtml, from
> generating tables as PNG graphics, which don't work reliably on some
> "devices"/file formats, and are not searchable, to generating tables in
> searchable text form on all "devices"/file formats, and fix other
> related issues, so may also affect man pages with tables differently. 
> 
> So for the current release, localize the changes to the man page chew
> input embedded in the strftime.c source comments, and the generated
> strftime.3 man page table formatting.
> Be prepared to tweak formatting if doc generation needs it, and
> eventually eliminate custom processing.
> 
> newlib/libc/time/strftime.c: split chew table of conversion format
> specifiers as man/tbl/groff can not handle large tables on all output
> devices/file formats
> 
> newlib/libc/Makefile.inc: sed fix strftime.3 tbl/groff format issues:
> remove multiple "^l l$" tbl line formats at tops of tables;
> change remaining "^l l\.$" tbl line formats at tops of tables so second
> column is lx and extends to margin;
> remove "^.PP$" breaks before each format description as it misaligns
> text below format specifier;
> remove blank line between adjacent tables
> 
> Brian Inglis (2):
>   newlib/libc/time/strftime.c: split chew table of conversion format
>     specifiers
>   newlib/libc/Makefile.inc: sed fix strftime.3 tbl/groff format issues
> 
>  newlib/libc/time/strftime.c | 3 ++-
>  newlib/libc/Makefile.inc    | 1 +
>  2 files changed, 3 insertions(+), 1 deletion(-)
> 
> --
> 2.39.0


  parent reply	other threads:[~2023-02-21  9:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 20:49 [PATCH 0/2] newlib/libc/time/strftime: table format fix man, tbl, groff multi-page table issues 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
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   ` Corinna Vinschen [this message]
2023-02-22 20:10     ` [PATCH v3 0/2] newlib/libc/time/strftime: fix multi-page table " 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=Y/SLtmUi8dilWqCL@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=jon.turney@dronecode.org.uk \
    --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).