Re: Warn on semantic newlines

On 4/27/23, Douglas McIlroy wrote: > "Semantic newline" warnings are relatively innocuous. The occasional > pitch on this mailing list for paragraph awareness is far less so. If you're referring here to changing groff's line-by-line processing to paragraph-at-once processing (via Knuth-Plass or s

Re: Count number of spaces at beginning of line?

Hi Oliver, Dave wrote: > > Is there any possibility to count leading spaces in groff? > > See the documentation for the \n[lsn] register. Which can be seen with info groff 'Leading Spaces Traps' | cat I'd been playing with an input trap, ‘.it’, so you might be interested to learn about thos

Re: Perl and linguistics. (Was: neatroff for Russian.)

Hi Oliver, BTW, are you subscribed to groff@gnu.org? If so, I'll stop mailing you directly too. > and from there directly jumped to Perl the moment I familiarized > myself with X11 workstations at our university, due to its wonderfully > elliptical style (I am a linguist by training, and many of

Re: Behaviour of .so differs between mandoc and groff

At 2023-04-30T09:24:42+1000, Alexis wrote: > Ping. Does anyone have any thoughts on this? It's a small but > persistent irritation on my system. :-) Hi Alexis, The groff(7) man page is pretty terse about this request. Our Texinfo manual says more. 5.33 I/O 'gtroff' has several request

Re: Multi-columns in ms

Hi Deri, At 2023-04-30T00:46:40+0100, Deri wrote: > You could .unformat the footnote before outputting at the current line > length. > > .\" keep.trf : groff -Tpdf keep.trf | okular - > .sp 1i > .de addtxt > .ev add > .nf > .boxa keep > \\$* > .boxa > .unformat keep > .ev > .. > .addt

Re: Warn on mid-input line sentence endings

At 2023-04-30T03:04:27+0200, Alejandro Colomar wrote: > On 4/30/23 02:05, G. Branden Robinson wrote: > > I should have said "_Warn on_ semantic newlines" is a terrible > > instruction/summary. > > That's why I used the phrase (at least I tried to do it consistently > recently) "warn on S. N. viola

Re: Behaviour of .so differs between mandoc and groff

On Sun, Apr 30, 2023 at 07:05:55AM -0500, G. Branden Robinson wrote: > The latter choice is a better one from a design perspective, in my > opinion, because it is more general. On the other hand, man pages > sourcing the text of pages from other sections on the manual seems about > as unlikely as

Re: Count number of spaces at beginning of line?

At 2023-04-29T21:22:00-0500, Dave Kemper wrote: > On 4/29/23, Oliver Corff wrote: > > Is there any possibility to count leading spaces in groff? > > See the documentation for the \n[lsn] register. I've never used it, > but its description sounds like what you're looking for. Indeed, a preproces

Re: Behaviour of .so differs between mandoc and groff

[dropped the mandoc list; they won't let me post] At 2023-04-30T13:44:09+0100, Colin Watson wrote: > On Sun, Apr 30, 2023 at 07:05:55AM -0500, G. Branden Robinson wrote: > > The latter choice is a better one from a design perspective, in my > > opinion, because it is more general. On the other ha

Re: Warn on mid-input line sentence endings

Hi Branden, G. Branden Robinson wrote on Sun, Apr 30, 2023 at 07:34:57AM -0500: > Hmm, I see that was Bjarni's doing. Being from Iceland, he perhaps has > more of the spirit of Loki than most... Please do not jump to conclusions. I know at least one Icelander personally and he is a very pleasa

Re: neatroff for Russian. (Was: Questions concerning hyphenation patterns for non-Latin languages, e.g. Russian)

At 2023-04-29T21:38:53-0500, Dave Kemper wrote: > On 4/29/23, Oliver Corff wrote: > > Would it be a feasible option to use UTF-8 throughout the inner > > workings of a future groff, I'm going to phrase this more confrontationally than it needs to be just to make a point about software design: It

[tbl] [regression] Formatting glitch in table separators

Hi Branden, This one seems serious, and not just a minor inconvenience. You can reproduce it in the current ascii.7 page from the Linux Manual Pages. The table separator is gone (except for some aberration at the end, which even invades the following subsection). Here's the code:

Re: [tbl] [regression] Formatting glitch in table separators

Hi Alex, At 2023-04-30T16:40:11+0200, Alejandro Colomar wrote: > This one seems serious, and not just a minor inconvenience. You can > reproduce it in the current ascii.7 page from the Linux Manual Pages. > The table separator is gone (except for some aberration at the end, > which even invades t

Re: Inter-paragraph separation modified by HP

Hi Alex, At 2023-04-29T21:32:48+0200, Alejandro Colomar wrote: > > I'm not seeing a difference in vertical space among the 3 PDF > > exhibits. > > Indeed; it seems I sent the wrong files. I'll copy here what I did > now. > > > $ uri.HP.new.pdf > $ uri.HP.old.pdf > $ >uri.PP.new.pdf > $ >uri.

an.tmac with Japanese man page

When viewing Japanese man pages it used to be necessary to pass the flag -f setting the default font family to a Japanese font which affected both the body of a man page and the headings, in bold, when viewing the grops output of a japanese man page. In 1.23.0-rc4 this no longer works, for headi

Re: an.tmac with Japanese man page

Hi Deri, At 2023-04-30T21:21:11+0100, Deri wrote: > When viewing Japanese man pages it used to be necessary to pass the > flag -f setting the default font family to a Japanese font which > affected both the body of a man page and the headings, in bold, when > viewing the grops output of a japanese

Re: [tbl] [regression] Formatting glitch in table separators

Hi Branden, On 4/30/23 17:00, G. Branden Robinson wrote: > Hi Alex, > > At 2023-04-30T16:40:11+0200, Alejandro Colomar wrote: >> This one seems serious, and not just a minor inconvenience. You can >> reproduce it in the current ascii.7 page from the Linux Manual Pages. >> The table separator is

Re: Warn on mid-input line sentence endings

Hi Branden, On 4/30/23 14:34, G. Branden Robinson wrote: >> Well, formally yes. And a regex can't find C function definitions in >> a source tree; at least if you try to fool it by writing the most >> horrible code in the universe. But I wrote a relatively small >> script[1] that finds a lot of