Re: [BUG] "\fC" macro in ox-man.el [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)]

2024-12-18 Thread G. Branden Robinson
[looping in groff list; please reply to it as well, as I am not subscribed to emacs-orgmode] Hi Xiyue, Ihor, and Jeremy, I stumbled across this thread while researching problems have encountered with groff, which I maintain for the GNU Project. At 2024-02-29T23:51:29-0800, Xiyue Deng wrote: > "m

Re: "pdf: pdfpic" and "pdf: import" (was: Novel use of .char)

2024-12-18 Thread G. Branden Robinson
Hi Deri, At 2024-12-18T16:51:59+, Deri wrote: > Import is not ready for primetime, its not finished. It was originally > conceived for non-standard import of images. Typically where you want > the rendered image to be a precise size (i.e. fill to the edges of an > A4 page), ignoring the XY rat

Re: synchronous and asynchronous grout (was: Novel use of .char)

2024-12-18 Thread G. Branden Robinson
Hi Deri, At 2024-12-18T17:41:59+, Deri wrote: > On Wednesday, 18 December 2024 01:07:45 GMT G. Branden Robinson wrote: > > This is an extremely helpful presentation. I have some questions. > > > > 1. Where was the foregoing distinction documented in, say, the > > groff 1.22.3 era? > >

"pdf: pdfpic" and "pdf: import" (was: Novel use of .char)

2024-12-18 Thread G. Branden Robinson
Hi Deri, At 2024-12-18T11:10:52+, Deri wrote: > I wrote "pdf: pdfpic" to mimic the behaviour of .PSPIC, render image > down from current point, not realising (until now!) that "ps: import" > renders the image up from the current point. This difference in > behaviour is somewhat masked because

Re: synchronous and asynchronous grout (was: Novel use of .char)

2024-12-18 Thread G. Branden Robinson
At 2024-12-18T20:28:17+, Deri wrote: > On Wednesday, 18 December 2024 18:12:01 GMT G. Branden Robinson wrote: > > [1] You already know what's coming. My hobnail boots and swagger > > stick say "you get code points 0x20 to 0x7E in your > > uninterpreted stream and nothing else". > > And

Re: synchronous and asynchronous grout (was: Novel use of .char)

2024-12-18 Thread Deri
On Wednesday, 18 December 2024 01:07:45 GMT G. Branden Robinson wrote: > This is an extremely helpful presentation. I have some questions. > > 1. Where was the foregoing distinction documented in, say, the groff > 1.22.3 era? > > 2. How confident are you that these distinctions were consci

Re: Novel use of .char

2024-12-18 Thread Deri
On Wednesday, 18 December 2024 12:36:13 GMT Tadziu Hoffmann wrote: > > I wrote "pdf: pdfpic" to mimic the behaviour of .PSPIC, > > render image down from current point, [...] > > The above difference means this works for pdf:- > > > > .char \[gnu] \v'-9p'\X'pdf: pdfpic GNU-head-small.pdf -L 10p'

Re: Novel use of .char

2024-12-18 Thread Deri
On Wednesday, 18 December 2024 00:14:38 GMT Tadziu Hoffmann wrote: > If the former, then it seems a pretty roundabout way of achieving > the purpose. For example, using the ps device, the following is > sufficient: > > .char \[gnu] \X'ps: import GNU-head-small.ps 0 0 25 22 1'\h'10p' > A G

Re: "pdf: pdfpic" and "pdf: import" (was: Novel use of .char)

2024-12-18 Thread Deri
On Wednesday, 18 December 2024 15:29:43 GMT G. Branden Robinson wrote: > Could the existing (but undocumented) "pdf: import" be changed in the > same way, to emphasize the equivalence of the features? > > https://git.savannah.gnu.org/cgit/groff.git/tree/src/devices/gropdf/gropdf.p > l?h=1.23.0#n11

Re: Novel use of .char

2024-12-18 Thread Tadziu Hoffmann
> I wrote "pdf: pdfpic" to mimic the behaviour of .PSPIC, > render image down from current point, [...] > The above difference means this works for pdf:- > > .char \[gnu] \v'-9p'\X'pdf: pdfpic GNU-head-small.pdf -L 10p'\h'10p' > A GNU head \[gnu] image. Thanks for the feedback! This solut

Re: Proposed: QS/QE macros for quotation in man(7)

2024-12-18 Thread G. Branden Robinson
[self-correcting follow-up] At 2024-12-18T20:00:53-0600, G. Branden Robinson wrote: > Pro: > * People may discover that quotation marks are properly available in > the man(7) language, a fact that has been obscure for 45 years. > (The `\*(lq` and `\*(rq` syntax has been available since day one

Re: synchronous and asynchronous grout (was: Novel use of .char)

2024-12-18 Thread Deri
On Wednesday, 18 December 2024 18:12:01 GMT G. Branden Robinson wrote: > Mmmm. Good objective for 1.25. > > Regards, > Branden > > [1] You already know what's coming. My hobnail boots and swagger stick > say "you get code points 0x20 to 0x7E in your uninterpreted stream > and nothing el

Re: Proposed: QS/QE macros for quotation in man(7)

2024-12-18 Thread Dave Kemper
On Mon, Dec 16, 2024 at 8:28 AM G. Branden Robinson wrote: > I don't feel I have sufficiently broad knowledge of what man-parsing > tools are out there besides *roffs and mandoc(1). Fair enough, and perhaps a decent reason on its own to be conservative with language additions. > Plan 9 troff is

Re: Proposed: QS/QE macros for quotation in man(7)

2024-12-18 Thread Alejandro Colomar
Hi Dave, On Wed, Dec 18, 2024 at 02:48:35PM -0600, Dave Kemper wrote: > One final point unrelated to the macro names: > > > B2. It would be trivial to support the British, who use the wrong > > quotation marks^W^W^W^W^Wdrive on the wrong side of the > > road^W^W^W^W^W^W^W^Whave a differen

Re: Proposed: QS/QE macros for quotation in man(7)

2024-12-18 Thread G. Branden Robinson
Hi Dave & Alex, I started out off-topic and then wandered back onto it. To remedy that, I've moved the on-topic part to the top of this message. Replies to your messages follow below. There seems to be no objection to the core proposal (so far). Nobody addressed the initial-word-hyphenation-su