Re: Proposed: make \X read its argument in copy mode

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

Re: Proposed: make \X read its argument in copy mode

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

Re: Proposed: make \X read its argument in copy mode

[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' copies anything > to the output, as a device control function of the form x X anythi

Re: Proposed: make \X read its argument in copy mode

Hi Deri, At 2024-01-20T21:03:15+, Deri wrote: > On Saturday, 20 January 2024 01:39:21 GMT G. Branden Robinson wrote: [snip] > > x X ps: exec [4849204445524920F09F9888 pdfmark2 > > > > Something pretty close to that works on the deri-gropdf-ng branch > > today, as I understand it. > > I'm afr

Re: Proposed: make \X read its argument in copy mode

Hi Deri, At 2024-01-20T21:03:11+, Deri wrote: > > can't transparently output node at top level > > > > But the reason 1.23.0 doesn't throw these errors is because I hid > > them, not because we fixed them.[7] > > It might be worth clarifying what this caused this error to appear > (befor

Re: Proposed: make \X read its argument in copy mode

On Saturday, 20 January 2024 00:56:34 GMT G. Branden Robinson wrote: > Hi Deri, > > At 2024-01-20T00:07:21+, Deri wrote: > > On Friday, 19 January 2024 21:39:57 GMT G. Branden Robinson wrote: > > > Right. Before I craft a lengthy response to this--did you see the > > > footnote? > > > > Yes,

Re: Proposed: make \X read its argument in copy mode

On Saturday, 20 January 2024 01:39:21 GMT G. Branden Robinson wrote: > [self-follow-up with correction] > > At 2024-01-19T18:56:37-0600, G. Branden Robinson wrote: > > This might be more accurately stated as: > > > > 2) \X behaves like .device used to (in groff 1.23.0 and earlier). > > [correcti

Re: Proposed: make \X read its argument in copy mode

[self-follow-up with correction] At 2024-01-19T18:56:37-0600, G. Branden Robinson wrote: > This might be more accurately stated as: > > 2) \X behaves like .device used to (in groff 1.23.0 and earlier). [correction follows] And I repeat: this is _NOT_ a _hard_ prerequisite to expressing Unicode s

Re: Proposed: make \X read its argument in copy mode

Hi Deri, At 2024-01-20T00:07:21+, Deri wrote: > On Friday, 19 January 2024 21:39:57 GMT G. Branden Robinson wrote: > > Right. Before I craft a lengthy response to this--did you see the > > footnote? > > Yes, sorry, it didn't help. I'm just comparing output now with output > in 1.23.0 and wha

Re: Proposed: make \X read its argument in copy mode

On Friday, 19 January 2024 21:39:57 GMT G. Branden Robinson wrote: > Hi Deri, > > At 2024-01-19T21:16:54+, Deri wrote: > > On Tuesday, 16 January 2024 19:22:48 GMT G. Branden Robinson wrote: > > > Or: Should device control commands affect the environment? > > > > > > I therefore propose to ch

Re: Proposed: make \X read its argument in copy mode

Hi Deri, At 2024-01-19T21:16:54+, Deri wrote: > On Tuesday, 16 January 2024 19:22:48 GMT G. Branden Robinson wrote: > > Or: Should device control commands affect the environment? > > > > I therefore propose to change this, and have the `\X` escape sequence > > read its argument in copy mode.

Re: Proposed: make \X read its argument in copy mode

On Tuesday, 16 January 2024 19:22:48 GMT G. Branden Robinson wrote: > Or: Should device control commands affect the environment? > ... > I therefore propose to change this, and have the `\X` escape sequence > read its argument in copy mode. That will make it work like the > `device` request in g

Re: Proposed: make \X read its argument in copy mode

> > This assumes you know both the desired font and the desired colour, which > might be defined at other places in the document and not under your control. Yeah, I know. I was trying to gauge how Groff's escape sequences might benefit an \X'…' sequence, and the PostScript I gave was a contrived

Re: Proposed: make \X read its argument in copy mode

> > \fB\s(12\m[red]\X'ps: big bold red text in my device command'\fP > \X'ps: exec 1.0 0 0 setrgbcolor /Times-Bold findfont \n[.s] scalefont setfont > (Text) show' This assumes you know both the desired font and the desired color, which might be defined at other places in the document and not u

Re: Proposed: make \X read its argument in copy mode

Hi John, At 2024-01-18T00:32:04+1100, John Gardner wrote: > So instead of: > > \X'ps: \fB\s(12\m[red]big bold red text in my device command\fP' > > > > one would write: > > \fB\s(12\m[red]\X'ps: big bold red text in my device command'\fP > > I believe you meant to provide an example more like thi

Re: Proposed: make \X read its argument in copy mode

Hi Branden, So instead of: > \X'ps: \fB\s(12\m[red]big bold red text in my device command\fP' > > one would write: > \fB\s(12\m[red]\X'ps: big bold red text in my device command'\fP I believe you meant to provide an example more like this? \X'ps: exec 1.0 0 0 setrgbcolor /Times-Bold findfont \n