From: Alejandro Colomar <alx@kernel.org>
To: tech@mandoc.bsd.lv
Subject: Re: mandoc -man -Thtml: unwanted line break after bullet (.IP)
Date: Wed, 18 Oct 2023 20:52:03 +0200 [thread overview]
Message-ID: <ZTApVCoBgpH9XqSV@debian> (raw)
In-Reply-To: <ZTAF0ysU9+HIi+uM@asta-kit.de>
[-- Attachment #1: Type: text/plain, Size: 2210 bytes --]
On Wed, Oct 18, 2023 at 06:20:35PM +0200, Ingo Schwarze wrote:
> Hi Alejandro,
>
> Ingo Schwarze wrote on Wed, Oct 18, 2023 at 02:04:46AM +0200:
>
> > 3. teach list_continues() that \[bu] is the same as \(bu.
>
> This part is now fixed, too, see the commit below.
>
> The guesswork required to deal with .IP certainly isn't perfect yet,
> but lets walk one step at a time, and let's start with issues that
> actually cause inconvenience in real-world manual pages.
>
> Yours,
> Ingo
>
>
> Log Message:
> -----------
> Support the GNU-specific syntax ".IP \\[bu]" for bullet lists in man(7)
> pages that Alejandro Colomar recommends in the "Lists" subsection of
> https://man7.org/linux/man-pages/man7/man-pages.7.html#STYLE_GUIDE .
>
> For example, this will improve HTML formatting of the first list in
> the subsection "Feature test macros understood by glibc" on the page
> https://manpages.debian.org/bookworm/manpages/ftm.7.en.html .
>
> Issue reported by Alejandro Colomar <alx at kernel dot org>.
LGTM. Thanks,
Alex
>
> Modified Files:
> --------------
> mandoc:
> man_html.c
>
> Revision Data
> -------------
> Index: man_html.c
> ===================================================================
> RCS file: /home/cvs/mandoc/mandoc/man_html.c,v
> retrieving revision 1.185
> retrieving revision 1.186
> diff -Lman_html.c -Lman_html.c -u -p -r1.185 -r1.186
> --- man_html.c
> +++ man_html.c
> @@ -433,10 +433,12 @@ list_continues(const struct roff_node *n
> s2 = n2 == NULL ? "" : n2->string;
> c1 = strcmp(s1, "*") == 0 ? '*' :
> strcmp(s1, "\\-") == 0 ? '-' :
> - strcmp(s1, "\\(bu") == 0 ? 'b' : ' ';
> + strcmp(s1, "\\(bu") == 0 ? 'b' :
> + strcmp(s1, "\\[bu]") == 0 ? 'b' : ' ';
> c2 = strcmp(s2, "*") == 0 ? '*' :
> strcmp(s2, "\\-") == 0 ? '-' :
> - strcmp(s2, "\\(bu") == 0 ? 'b' : ' ';
> + strcmp(s2, "\\(bu") == 0 ? 'b' :
> + strcmp(s2, "\\[bu]") == 0 ? 'b' : ' ';
> return c1 != c2 ? '\0' : c1 == 'b' ? '*' : c1;
> }
>
> --
> To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-18 18:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 13:17 Alejandro Colomar
2023-10-16 14:52 ` Ingo Schwarze
2023-10-16 15:20 ` Jan Stary
2023-10-16 15:43 ` Ingo Schwarze
2023-10-16 16:03 ` Ingo Schwarze
2023-10-16 17:10 ` Alejandro Colomar
2023-10-16 17:16 ` Alejandro Colomar
2023-10-16 17:28 ` Alejandro Colomar
2023-10-17 19:02 ` Ingo Schwarze
2023-10-17 21:39 ` Alejandro Colomar
2023-10-18 0:04 ` Ingo Schwarze
2023-10-18 11:32 ` Alejandro Colomar
2023-10-18 14:48 ` Ingo Schwarze
2023-10-18 14:56 ` Alejandro Colomar
2023-10-18 16:20 ` Ingo Schwarze
2023-10-18 18:52 ` Alejandro Colomar [this message]
2023-10-19 11:59 ` Ingo Schwarze
2023-10-19 12:48 ` 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=ZTApVCoBgpH9XqSV@debian \
--to=alx@kernel.org \
--cc=tech@mandoc.bsd.lv \
/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).