Re: Tilde (~) in bash(1) is typeset incorrectly as Unicode character

On Sun, Jul 30, 2023 at 02:05:19AM +, Bjarni Ingi Gislason wrote: > Simply add > > .if t .tr ~\(ti > > to "tmac/an.tmac", > instead of changing (hard coding) it in the sources (man pages). Correction: Drop '.if t' as -Tutf8 is an nroff mode.

Re: Tilde (~) in bash(1) is typeset incorrectly as Unicode character

Simply add .if t .tr ~\(ti to "tmac/an.tmac", instead of changing (hard coding) it in the sources (man pages).

Re: missing -Tpdf (and the curious case of mandoc_roff(7))

At 2023-07-30T09:35:28+1000, John Gardner wrote: [I wrote:] > > I wonder why mandoc didn't just call its roff(7) page mandoc(7), given > > that it parallels groff(7) more than anything else. > > Strictly speaking, Groff is at fault here; the manual page dedicated > to the Roff language proper shou

Re: missing -Tpdf (and the curious case of mandoc_roff(7))

> > I wonder why mandoc didn't just call its roff(7) page mandoc(7), given > that it parallels groff(7) more than anything else. > Strictly speaking, Groff is at fault here; the manual page dedicated to the Roff language proper should have been named as such, whereas groff(1) pertains to an execut

Re: missing -Tpdf (and the curious case of mandoc_roff(7))

> > Eh? That's precisely what it is. It covers matters that are (more or > less) common to all roff implementations. Have you looked at it? Sorry, my wires got crossed. I completely misread this discussion… I'll see myself out. On Sun, 30 Jul 2023 at 09:42, G. Branden Robinson < g.branden.

Re: missing -Tpdf

Branden, I forgot to add that your diagnosis seems to explain everything. I had not noticed groff-perl among the zillion things on offer at Cygwin. Being no fan of Perl, I may continue to rely on ps2pdf. Doug

Re: missing -Tpdf (and the curious case of mandoc_roff(7))

Hi Doug, At 2023-07-29T15:16:42-0400, Douglas McIlroy wrote: > Cygwin did exclude gropdf and pdfgroff. "The accompanying man page" > that I meant was groff.1. Perhaps that man page should say that not > all groff distributions support pdf. Okay. I want to keep groff(1)'s comprehensive list of ma

Re: missing -Tpdf

Cygwin did exclude gropdf and pdfgroff. "The accompanying man page" that I meant was groff.1. Perhaps that man page should say that not all groff distributions support pdf. On Sat, Jul 29, 2023 at 1:35 PM G. Branden Robinson wrote: > > Hi Doug, > > At 2023-07-29T13:00:13-0400, Douglas McIlroy wro

Re: Tilde (~) in bash(1) is typeset incorrectly as Unicode character

Hi Chet, At 2023-07-29T13:16:55-0400, Chet Ramey wrote: > On 7/28/23 3:28 PM, G. Branden Robinson wrote: > > Sorry about that. I fat-fingered it. > > > > An 'n' is needed after the second backslash, because we're interpolating > > a register value. > > Thanks. I probably could have figured it o

Re: missing -Tpdf

Hi Doug, At 2023-07-29T13:00:13-0400, Douglas McIlroy wrote: > 1.22.4, which I got via Cygwin, lacks -Tpdf, although the accompanying > man page describes it. Is it perhaps an installation option that > Cygwin didn't set? More or less. gropdf has some prerequisites, and if they aren't met, grop

Re: Tilde (~) in bash(1) is typeset incorrectly as Unicode character

On 7/28/23 3:28 PM, G. Branden Robinson wrote: Hi Chet, At 2023-07-28T15:15:48-0400, Chet Ramey wrote: Applying the patch without any other changes to bash.1 results in $ groff -Tascii -P -c -I/usr/local/src/bash/bash-20230728/doc -man /usr/local/src/bash/bash-20230728/doc/bash.1 > bash.0 trof

missing -Tpdf

1.22.4, which I got via Cygwin, lacks -Tpdf, although the accompanying man page describes it. Is it perhaps an installation option that Cygwin didn't set? Doug

Re: Findings: just run gxditview on your system and click

* On 2023 29 Jul 07:29 -0500, G. Branden Robinson wrote: > Okay, so we see the bug on Debian 11 (bullseye), now termed > "old-old-stable". The unfortunate choice of three code names starting B strikes again! old-old-stable should be Buster (Debian 10), old-stable should be Bullseye (Debian 11) and

Re: Tilde (~) in bash(1) is typeset incorrectly as Unicode character

Chet Ramey wrote in <2fd2ed52-3272-3433-6179-164bc5122...@case.edu>: ... |> At 2023-07-26T10:47:05+0200, Thomas ten Cate wrote: |>> In the bash manual page (`man bash`), the ASCII tilde character '~' |>> (0x7e) is replaced by the Unicode character '˜' (U+02DC SMALL TILDE): |>> |>> $ ma

Re: Tilde (~) in bash(1) is typeset incorrectly as Unicode character

Steffen Nurpmeso wrote in <20230729002703.lasps%stef...@sdaoden.eu>: |Chet Ramey wrote in | <2fd2ed52-3272-3433-6179-164bc5122...@case.edu>: | ... ||> At 2023-07-26T10:47:05+0200, Thomas ten Cate wrote: ||>> In the bash manual page (`man bash`), the ASCII tilde character '~' ||>> (0x7e) is

Re: Can't embed eps image

On Saturday, 29 July 2023 13:28:39 BST Michał Kruszewski via wrote: > GNU groff version 1.23.0 > > I have some .png image. > I have converted it to the .eps file using convert img.png eps3:img.eps. > However, when I generate the pdf using groff -ms -Tpdf -Kutf8 tmp.ms > > tmp.pdf, the image is not

Can't embed eps image

GNU groff version 1.23.0 I have some .png image. I have converted it to the .eps file using convert img.png eps3:img.eps. However, when I generate the pdf using groff -ms -Tpdf -Kutf8 tmp.ms > tmp.pdf, the image is not inserted into the pdf. There is only box with the image file path (which is co

Findings: just run gxditview on your system and click

Thanks to Robert, Nate, Tadziu, Oliver, and Dale for the replies--I asked for help, and got it! I'll cover the good news first. Any system experiencing this problem can patch in a workaround (that I have already committed to groff Git's master branch) that requires only the editing of a text file