Re: PDF book improvements

On 2023-08-12 23:46, Alejandro Colomar wrote: > Hi Deri, > > My end goal is to be able to embed the creation of the PDF book in the > Makefiles. To that end, as a first step, I'd like to reuse part of > what we already have in the Makefile. Currently, we process all files > with -Tpdf, which I

Re: PDF book improvements

On 2023-08-12 23:46, Alejandro Colomar wrote: > Hi Deri, > > My end goal is to be able to embed the creation of the PDF book in the > Makefiles. To that end, as a first step, I'd like to reuse part of > what we already have in the Makefile. Currently, we process all files > with -Tpdf, which I

[bug #63632] man pages: improve some wording and typesetting

Follow-up Comment #8, bug #63632 (project groff): [comment #7 comment #7:] > There is no hard rule against use of formatter features not > listed in _groff_man_style_(7)'s "Portability" section. True, but \| and \^ having similar uses, I presumed the one explicitly claimed to be (more) portable

[bug #57667] refer(1) rehab

Follow-up Comment #7, bug #57667 (project groff): Oliver replied outside this bug but cc:ed to bug-groff: http://lists.gnu.org/r/bug-groff/2023-08/msg00149.html > without the message to the mailing list the Savannah would have > escaped my attention Hmm, you should be on the cc list for this

Re: [PATCH v2] man*/: ffix (migrate to `MR`)

Hi Branden, Ingo, On 2023-08-01 16:12, G. Branden Robinson wrote: > At 2023-08-01T15:35:10+0200, Alejandro Colomar wrote: >> [CC += groff] >> >> Hi Jakub, Branden, >> >> On 2023-08-01 03:31, G. Branden Robinson wrote: >>> Hi Jakub, >>> >>> At 2023-08-01T00:16:41+0200, Jakub Wilk wrote: * G.

Re: PDF outline not capturing Cyrillic text

On Saturday, 12 August 2023 07:35:20 BST G. Branden Robinson wrote: > Hi Deri, > > At 2023-06-23T22:40:42+0100, Deri wrote: > > On Friday, 23 June 2023 19:17:58 BST Robin Haberkorn wrote: > > > So it seems that the main problem really lies in grops and/or gropdf > > > which should ideally work

[bug #64539] [man] add `TS` register to configure amount of space required after paragraph tags

Update of bug #64539 (project groff): Status:None => In Progress Assigned to:None => gbranden ___ Reply to this item at:

Re: problem with mm macros

Hi Andreas, At 2021-02-25T15:43:50+0100, Andreas Eder wrote: > I'm a newcomer to roff and have just begun reading the book 'UNIX > Document Processing and Typesetting'. There is an example of a letter > in there thay I enclose here, necause it shows the poblem: [...] > Now the problem is that

Re: [bug #57667] refer(1) rehab

Dear All, Branden, thank you for alerting me --- without the message to the mailing list the Savannah would have escaped my attention (I am still not *really* familiar with it). The rephrased beginning to the refer man page communicates the key concept in a much more straightforward way than

[bug #64548] [refer] want new fields: %e, %s, %c, %o, %a, %u

URL: Summary: [refer] want new fields: %e, %s, %c, %o, %a, %u Group: GNU roff Submitter: gbranden Submitted: Sat 12 Aug 2023 06:56:03 AM UTC Category: Preprocessor refer

[bug #57667] refer(1) rehab

Update of bug #57667 (project groff): Status:None => Need Info ___ Follow-up Comment #6: Oliver, can you respond to Dave's comment #5? Is the _refer_(1) man page rehabilitated to a

Re: PDF outline not capturing Cyrillic text

Hi Deri, At 2023-06-23T22:40:42+0100, Deri wrote: > On Friday, 23 June 2023 19:17:58 BST Robin Haberkorn wrote: > > So it seems that the main problem really lies in grops and/or gropdf > > which should ideally work with the Unicode escapes produced by > > preconv. I am not sure if we would still