bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 3/6] doc/bash.1: Revise "BUG REPORTS" section.


From: Grisha Levit
Subject: Re: [PATCH 3/6] doc/bash.1: Revise "BUG REPORTS" section.
Date: Sat, 4 Oct 2025 21:12:42 -0400

On Sat, Oct 4, 2025 at 6:58 PM G. Branden Robinson
<g.branden.robinson@gmail.com> wrote:
>
> Hi Grisha,
>
> At 2025-10-04T18:49:38-0400, Grisha Levit wrote:
> > On Sat, Oct 4, 2025, 09:59 G. Branden Robinson 
> > <g.branden.robinson@gmail.com>
> > wrote:
> > > -bug reports to \fIbug-bash@gnu.org\fP or post them to the Usenet
> > > +bug reports to \fIbug\-bash@gnu.org\fP or post them to the
> > > +.SM USENET
> >
> > Is there some trick that Bash needs to adopt to get groff to use
> > HYPHEN-MINUS for \- when setting HTML or PDF?
>
> Yes.  This was a bug in groff; it's been fixed in our Git repository's
> master branch, and the fix is expected to ship in groff 1.24.0.
>
> https://cgit.git.savannah.gnu.org/cgit/groff.git/commit/?id=1de7cff46dec169d9611f054ef0666bc2cfcef93

Thank you, I built groff from git and \- looks fine in HTML output now.

I see the note in the commit above:

    \" PDF's "CMap" feature solves this problem so we don't have to.

but I found the PDF output kind of strange: \- certainly _looks_ like
it is still being rendered as MINUS SIGN. When the text is copied from
some viewers it becomes a HYPHEN-MINUS but when copied from others it
remains a MINUS SIGN. Is that to be expected?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]