Re: Puzzle about ms files generated by pandoc

At 2022-07-16T00:34:14-0500, G. Branden Robinson wrote: > At 2022-07-09T01:00:57-0400, Robert Goulding wrote: > > Yes, this is code generated by pandoc. I made a simple markdown > > file, ms.md: > > > > roff > > > > > > > > And then processed it with: pandoc

Re: build system: devpdf/download regression

Hi Deri, At 2022-07-16T16:21:15+0100, Deri wrote: > On Saturday, 16 July 2022 12:48:50 BST G. Branden Robinson wrote: > > [1] I think this is because it began life as, or Deri had hopes for it > > to be, an installable tool. Failing to add gropdf support for some > > crazy font that will

How groff should locate AFM files for gropdf (was: build system: devpdf/download regression)

Hi Deri, At 2022-07-16T15:56:28+0100, Deri wrote: > My understanding is that the selection of paths to search is appended > to the value of the --with-urw-fonts-dir config variable (if any). Yes. To make it clear for mailing list readers, that's determined by font/devpdf/Foundry.in, which

[bug #59290] add register to enable/disable backtraces on diagnostics

Update of bug #59290 (project groff): Status: Postponed => None ___ Follow-up Comment #5: I think I have it. backtrace. ...with the trailing dot, following Kernighan's addition of

warning on mid-input line sentence endings (was: Warn on semantic newlines)

[I've retitled the subject line to avoid misleading terminology.] At 2022-06-10T07:16:54-0500, G. Branden Robinson wrote: > At 2022-06-10T11:52:30+0200, Alejandro Colomar wrote: > > As far as I know, there's currently no tool that warns on "foo. bar" > > in filled test. Not `mandoc -Tlint`, and

[bug #62776] [troff] add optional diagnostic for sentences ending mid-input line

Follow-up Comment #1, bug #62776 (project groff): Alex, I've added you to the CC list for this ticket. ___ Reply to this item at: ___ Message sent via

[bug #62776] [troff] add optional diagnostic for sentences ending mid-input line

URL: Summary: [troff] add optional diagnostic for sentences ending mid-input line Project: GNU troff Submitter: gbranden Submitted: Sat 16 Jul 2022 03:56:33 PM UTC Category:

Re: man(7) .TH font change (was: groff man(7) `B` macro)

Hi Ingo, I've addressed your grievances with the `MR` macro at length in other mails so, apart from a few remarks at the end, I will confine my response here to your objection to the slightly changed rendering of man(7) headers and footers in groff. (For those needing a refresher, the change is

Re: build system: devpdf/download regression

On Saturday, 16 July 2022 12:48:50 BST G. Branden Robinson wrote: > [1] I think this is because it began life as, or Deri had hopes for it > to be, an installable tool. Failing to add gropdf support for some > crazy font that will be used only by the document you're about to > write

Re: build system: devpdf/download regression

On Saturday, 16 July 2022 12:02:29 BST G. Branden Robinson wrote: > Hi Ingo & Deri, > > At 2022-06-26T17:16:44+0100, Deri wrote: > > > In general, i would recommend differentiating configuration variables > > > by functionality. For example, if all you need is one font path, > > > i would expect

Re: man(7) .TH font change, was: groff man(7) `B` macro...

Hi Ingo, At 2022-06-19T17:00:47+0200, Ingo Schwarze wrote: > I'm not opposed to introducing new syntax in each and every case. That remains to be seen. What new man(7) syntax have you supported at the time it was proposed (or implemented)? > I'm merely saying new syntax needs strong

[bug #57855] doc/webpage.ms: replace with RELNOTES.ms

Update of bug #57855 (project groff): Summary: doc/webpage.ms: modify it to make it more obviously an example => doc/webpage.ms: replace with RELNOTES.ms ___ Follow-up Comment #4: Repurposing this ticket. Hollow out much

the compatibility of man(7) (was: man(7) .TH font change, was: groff man(7) `B` macro...)

At 2022-06-19T19:28:26+0200, Ingo Schwarze wrote: > Given that the base system corpora of FreeBSD and NetBSD are of the > same order of magnitude as in OpenBSD (and treating DragonFly as a > FreeBSD fork for now, which is not fair in general, but good enough > for this particular purpose because

afmtodit: both Tcommaaccent and uni0162 map to u0054_0327 (was: build system: devpdf/download regression)

Hi Ingo, At 2022-06-21T20:33:43+0200, Ingo Schwarze wrote: > >> +afmtodit: both Tcommaaccent and uni0162 map to u0054_0327 \ > >>at /usr/local/bin/afmtodit line 6555. > >> +afmtodit: both tcommaaccent and uni0163 map to u0074_0327 \ > >>at /usr/local/bin/afmtodit line 6555. I've sort

Re: build system: devpdf/download regression

Hi Ingo, At 2022-06-21T20:33:43+0200, Ingo Schwarze wrote: > G. Branden Robinson wrote on Tue, Jun 21, 2022 at 09:54:54AM -0500: > > First I want to add a regression test for this (and devhtml), so > > that we're sure all the font description files that _should_ get > > built unconditionally

Re: git-version-gen not working with Savannah/cgit snapshots

>> > I think that if GNU doesn't have the infrastructure or personnel >> > to support these, then, yes, the Savannah administrators should >> > fork (or just patch) cgit to the extent necessary to suppress the >> > exposure of these snapshot download links. I had no idea they >> > weren't truly

GROFF_URW_FONTS_CHECK and awk (was: build system: devpdf/download regression)

At 2022-06-23T15:05:29+0200, Ingo Schwarze wrote: > Deri wrote on Thu, Jun 23, 2022 at 12:56:16AM +0100: > > On Wednesday, 22 June 2022 22:29:29 BST G. Branden Robinson wrote: > >> At 2022-06-22T21:30:25+0100, Deri wrote: > > [...] > >>> I think the tests for awk and ghostscript need to just

[bug #62775] [groff.m4] lighten prerequisites of `GROFF_URW_FONTS_CHECK`

URL: Summary: [groff.m4] lighten prerequisites of `GROFF_URW_FONTS_CHECK` Project: GNU troff Submitter: gbranden Submitted: Sat 16 Jul 2022 11:29:49 AM UTC Category: General

Re: git-version-gen not working with Savannah/cgit snapshots

[dropped Bruno and bug-gnulib from distribution, added Werner] At 2022-06-25T17:45:01-0500, Dave Kemper wrote: > On 6/19/22, G. Branden Robinson wrote: > > I think that if GNU doesn't have the infrastructure or personnel to > > support these, then, yes, the Savannah administrators should fork

Re: build system: devpdf/download regression

Hi Ingo & Deri, At 2022-06-26T17:16:44+0100, Deri wrote: > > In general, i would recommend differentiating configuration variables > > by functionality. For example, if all you need is one font path, > > i would expect having one variable to configure it. Two variables > > would make sense to

[bug #62774] [mdoc] warn if any of `Dd`, `Dt`, `Os` not called

URL: Summary: [mdoc] warn if any of `Dd`, `Dt`, `Os` not called Project: GNU troff Submitter: gbranden Submitted: Sat 16 Jul 2022 10:46:19 AM UTC Category: Macro mdoc

[bug #62773] [man] warn if `TH` macro not called

URL: Summary: [man] warn if `TH` macro not called Project: GNU troff Submitter: gbranden Submitted: Sat 16 Jul 2022 10:38:30 AM UTC Category: Macro man

Re: mdoc(7) prologue regressions

[self-follow-up] At 2022-07-16T02:21:49-0500, G. Branden Robinson wrote: > groff man(7) in groff Git behaves pretty badly if `TH` is omitted, > whereas groff 1.22.4 degrades much more gracefully. I was incorrect about this. I was comparing 1.22.4's "groff -mandoc" to Git HEAD's "groff -ww

[bug #62763] [hdtbl] man page should not clobber special character names

Update of bug #62763 (project groff): Category: General => Macro - others/general Summary: [man] groff_hdtbl.1.man: do not redefine global character names => [hdtbl] man page should not clobber special character names

[bug #62763] [man] groff_hdtbl.1.man: do not redefine global character names

Update of bug #62763 (project groff): Status: Need Info => Confirmed ___ Follow-up Comment #2: Oh, I get it. I finally caught Bjarni using the UTF-8 encoding. ;-) With the `-Tascii` or

[bug #62763] [man] groff_hdtbl.1.man: do not redefine global character names

Update of bug #62763 (project groff): Status:None => Need Info ___ Follow-up Comment #1: Something stranger is afoot here. For one thing, I would not use the source versions of the man

Re: mdoc(7) prologue regressions

Hi Ingo, At 2022-06-27T00:29:08+0200, Ingo Schwarze wrote: > The first issue i identified is a group of regressions in the > behaviour of the mdoc(7) prologue macros .Dt and .Os. > The regressions aren't particularly severe because all that i found > so far only trigger when the document uses