Bug#959851: pandoc: $ in nroff table causes spurious TeX-related failure

2020-05-06 Thread Jonas Smedegaard
Control: clone -1 -2 Control: retitle -2 pandoc: please upgrade to 2.4 or newer to support parsing man format Control: severity -2 wishlist Quoting Jonas Smedegaard (2020-05-06 21:14:24) > Quoting James Youngman (2020-05-06 20:43:10) > > It seems to me that that interpretation was rather

Processed: Re: Bug#959851: pandoc: $ in nroff table causes spurious TeX-related failure

2020-05-06 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #959851 [pandoc] pandoc: no warning fallback-parsing as markdown (expected fixed since v2.8) Bug 959851 cloned as bug 959908 > retitle -2 pandoc: please upgrade to 2.4 or newer to support parsing man > format Bug #959908 [pandoc] pandoc: no warning

Bug#959851: pandoc: $ in nroff table causes spurious TeX-related failure

2020-05-06 Thread John MacFarlane
As you can see from pandoc's changelog, the man reader was only introduced in version 2.4. You're using an older version, so...

Bug#959851: pandoc: $ in nroff table causes spurious TeX-related failure

2020-05-06 Thread Jonas Smedegaard
Quoting James Youngman (2020-05-06 20:43:10) > It seems to me that that interpretation was rather optimistic (and > easily falsifiable using the provided reproduction steps): > > horizon:~$ rm -f bbcbasic.html; pandoc -f man -s -o bbcbasic.html > /tmp/minimal_nroff2.1 ; echo exit status $?;

Bug#959851: pandoc: $ in nroff table causes spurious TeX-related failure

2020-05-06 Thread James Youngman
It seems to me that that interpretation was rather optimistic (and easily falsifiable using the provided reproduction steps): horizon:~$ rm -f bbcbasic.html; pandoc -f man -s -o bbcbasic.html /tmp/minimal_nroff2.1 ; echo exit status $?; ls -l bbcbasic.html Unknown reader: man exit status 1

Processed: Re: Bug#959851: pandoc: $ in nroff table causes spurious TeX-related failure

2020-05-06 Thread Debian Bug Tracking System
Processing control commands: > severity -1 minor Bug #959851 [pandoc] pandoc: $ in nroff table causes spurious TeX-related failure Severity set to 'minor' from 'normal' > retitle -1 pandoc: no warning fallback-parsing as markdown (expected fixed > since v2.8) Bug #959851 [pandoc] pandoc: $ in

Bug#959851: pandoc: $ in nroff table causes spurious TeX-related failure

2020-05-06 Thread Jonas Smedegaard
Control: severity -1 minor Control: retitle -1 pandoc: no warning fallback-parsing as markdown (expected fixed since v2.8) Quoting John MacFarlane (2020-05-06 20:06:30) > > Thank you for your report. If you'd run a more recent version of > pandoc, you'd have seen the additional warning: > >

Bug#959851: pandoc: $ in nroff table causes spurious TeX-related failure

2020-05-06 Thread John MacFarlane
Thank you for your report. If you'd run a more recent version of pandoc, you'd have seen the additional warning: [WARNING] Could not deduce format from file extension .man Defaulting to markdown which should explain things. Add '-f man' to your command line and it should work fine. (At

Bug#959851: Acknowledgement (pandoc: $ in nroff table causes spurious TeX-related failure)

2020-05-06 Thread James Youngman
This nroff input seems to be minimal and will reproduce the problem: .TH foo 1 2020 .TS ; l l. 0xBD "CHR$" 0xBE "GET$" .TE

Bug#959851: Acknowledgement (pandoc: $ in nroff table causes spurious TeX-related failure)

2020-05-06 Thread James Youngman
The problem is unrelated to the use of the table, though, since this also reproduces the problem: .TH foo 1 2020 Both "CHR$" and "GET$" are keywords in BBC BASIC.

Bug#959851: pandoc: $ in nroff table causes spurious TeX-related failure

2020-05-06 Thread James Youngman
Package: pandoc Version: 2.2.1-3+b2 Severity: normal How to reproduce: 1. Start with this nroff input file: .TH "BBC BASIC" 5 2020-05-06 \" -*- nroff -*- .SH "SOME EXAMPLE TABLE" .TS tab(|) allbox; lb lb l l. Byte|Keyword 0xBC|"VPOS" 0xBD|"CHR$" 0xBE|"GET$" .TE 2. Run Pandoc on it like