Re: public inbox for groff

[CC trimmed; keep just groff@] Hi, On Mon, Mar 31, 2025 at 09:55:20AM -0400, Frank Ch. Eigler wrote: > Hi - > > > Many GNU projects have a public inbox at . > > That's significantly more comfortable to follow threads than archives > > like

Re: public inbox for groff

On 2025-03-31 Alejandro Colomar wrote: > Hi! > > Many GNU projects have a public inbox at . > That's significantly more comfortable to follow threads than archives > like , so it would be > interesting to have a public inbox

Re: public inbox for groff

Hi - > Many GNU projects have a public inbox at . > That's significantly more comfortable to follow threads than archives > like , so it would be > interesting to have a public inbox for groff too. Would you mind adding > i

Re: Translating manpages into several idioms (gettextization)

On Mon, Mar 24, 2025 at 06:29:35PM -0300, Jamenson Espindula wrote: From: Colin Watson Are you aware of po4a? It has its problems, but it's the best tool I'm aware of in this area. Thank you for your reply, Colin Watson. Yes, I am aware of the 'po4a' (PO for anything) tool. Unfortunately, '

Groff tutorials & multipage. [Was: Re: More stuff solved.

On 14.03.25 13:45, G. Branden Robinson wrote: > At 2025-03-14T09:00:50+, dvalin--- via GNU roff typesetting system > discussion wrote: ... > > Yes, at "4.6.5.3 Paragraphs" I read "Alternatively, a blank input line > > breaks the output line and vertically spaces by one vee." There was no

Re: public inbox for groff

Hi Alejandro, Alejandro Colomar writes: > Who in GNU/FSF should we talk to? Emailing savannah-hackers-pub...@gnu.org is probably a good place to start [1]. They can contact relevant FSF people if needed. Collin [1] https://lists.gnu.org/mailman/listinfo/savannah-hackers-public