On 1/23/24, G. Branden Robinson wrote:
> At 2024-01-23T20:52:34-0600, Dave Kemper wrote:
>> However, .bp arguably shouldn't have been affected by the change,
>> since it probably wasn't subject to the same historical ambiguity.
>
> I agree, and I wasn't happy about it.
I wonder if the proper way
Hi Dave,
At 2024-01-23T20:52:34-0600, Dave Kemper wrote:
> However, .bp arguably shouldn't have been affected by the change,
> since it probably wasn't subject to the same historical ambiguity.
I agree, and I wasn't happy about it.
> (I bet implementing that distinction would require some macro
At 2024-01-24T02:26:44+, Bjarni Ingi Gislason wrote:
> This is a regression (not backward compatible)
It's a _change_. That's why it's documented in the ChangeLog file.
It is a change that can have a significant measurable effect on user
documents. That's why it's documented in the NEWS f
On 1/23/24, Bjarni Ingi Gislason wrote:
> Macros for historical documents should be put into a separate
> directory (e.g., tmac/historical), which can then be searched
> with the '-M ' option.
As the NEWS item (posted in full a couple hours ago in this thread)
mentions, this change *increases*
This is a regression (not backward compatible) caused by
Branden acting as a developer (not as a maintainer).
This is the second case of this kind of a bug (bug #65077),
see for example "CSTR #54", chapter 5, about the 'ns' request or
the "groff.info" (info groff) and groff(7) (incomplete).
[self-follow-up]
At 2023-07-01T05:58:16-0500, G. Branden Robinson wrote:
> We could:
>
> 1. Make `INITI` recongize a "location-type" argument of 'C' (for
> "custom"), where the entry format is whatever the user supplies as
> the arguments to `IND`.
> 2. Make `IND` require two arguments
At 2024-01-23T19:10:00-0600, Dave Kemper wrote:
> On 1/23/24, T. Kurt Bond wrote:
> > I have a groff -ms source file
> [...]
> > When I groff it with version 1.23.0 the page breaks
> > corresponding to the explicit .bp requests are missing.
>
> This item in the (very lengthy) NEWS file for 1.23 p
Hi Deri,
At 2024-01-23T11:32:02+, Deri wrote:
> Just to be sure, can you confirm your intention is to return .device
> to its 1.23.0 state, and mirror that behaviour for \X,
Yes, that is my intention.
> so we will have no more red seepage.
Not sure what that is, so I can't promise it. Does
On 1/23/24, T. Kurt Bond wrote:
> I have a groff -ms source file
[...]
> When I groff it with version 1.23.0 the page breaks
> corresponding to the explicit .bp requests are missing.
This item in the (very lengthy) NEWS file for 1.23 probably explains
the change you're seeing:
The s (ms) macro
Quoth Lennart Jablonka:
I’ve attached a PDF of our favourite table.
Content-Type: application/pdf
Content-Disposition: attachment; filename="table1.pdf"
Content-Transfer-Encoding: quoted-printable
Oops. That should be application/postscript and table1.ps.
Quoth Lennart Jablonka:
and the character codes emitted are still those of the C/A/T,
resulting in the wrong glyphs being used.
The codes should probably be remapped by default, with a command-line
option to restore the original ones. I would of course recommend
writing out 'C' commands with g
On Tuesday, 23 January 2024 02:46:50 GMT G. Branden Robinson wrote:
> [self-follow-up]
>
> > Or: Should device control commands affect the environment?
> >
> > Recall the definition of the \X escape sequence from CSTR #54 (1992).
> >
> > 10.7. Transparent output. The sequence \X'anything' copi
Hi,
I just happened to notice that the PDF targets of the example documents
of mom in my /usr/share/doc/groff/examples/mom/ directory (Fedora 39)
seem to have been compiled without the -k option even though README.txt
has the example command lines as well as an explicit mention of the -k
option.
13 matches
Mail list logo
