Re: [PROPOSAL] Generating consistent papersizes

2023-08-17 Thread Alexis
On Thu, Aug 17, 2023 at 02:16:14AM -0500, Dave Kemper wrote: > The best course of action is patience. \-: You've created a patch, > and a developer has to evaluate it and decide to either apply it or to > ask for changes. Unfortunately, groff developers are in short supply, > so this may take som

Re: [PROPOSAL] Generating consistent papersizes

2023-08-17 Thread Dave Kemper
On 8/12/23, Alexis wrote: > What is a good course of action to move forward with this? The best course of action is patience. \-: You've created a patch, and a developer has to evaluate it and decide to either apply it or to ask for changes. Unfortunately, groff developers are in short supply,

Re: [PROPOSAL] Generating consistent papersizes

2023-08-11 Thread Alexis
On Sat, Aug 05, 2023 at 10:21:06PM -0500, Dave Kemper wrote: > This is the topic of the open Savannah ticket > http://savannah.gnu.org/bugs/?62344#comment0. Thank you for the very helpful context, Dave. What is a good course of action to move forward with this? Should I create an account for myse

Re: [PROPOSAL] Generating consistent papersizes

2023-08-05 Thread Dave Kemper
On 8/5/23, Alexis wrote: > Being an avid proponent of single sources of truth I set out to prototype > a solution that defines dimension-based paper formats in a single place > and can be used to generate code for where the paper sizes are needed > in groff. This is the topic of the open Savannah

[PROPOSAL] Generating consistent papersizes

2023-08-05 Thread Alexis
Hi folks, in brief: while looking into paper sizes available in GNU troff I noticed some inconsistencies in the device support, e.g.: grops(1) accepts the dl paper size, yet gropdf(1) does not recognize it and gropdf accepts l-suffixed paper size variants, e.g. a4l yet grops does not. In detail: