On Mon, Dec 23, 2024, Deri wrote:
> To "debug" a misbehaving roff document the first port of call is to turn
> warnings on, then stare at your document for mistakes, use groff debugging
> tools (which you have added to), judicious use of .tm to check register
> values
> are what you expect (and
Apologies, Branden and onf were firing off emails at a rapid pace, this took
rather longer to write, so some of the points below where already covered in
their discourse.
On Friday, 20 December 2024 02:45:56 GMT G. Branden Robinson wrote:
> > If that's the case, I wonder why you're concerned abo
On Fri, Dec 20, 2024 at 4:15 PM onf wrote:
> Does it have any other use nowadays besides regression testing?
The -a option is invaluable for testing in general, such as when
debugging some typesetting issues. In
http://savannah.gnu.org/bugs/?55278#comment0 some other uses I gave
are letting the
Hi Branden,
On Fri Dec 20, 2024 at 7:45 PM CET, G. Branden Robinson wrote:
> At 2024-12-20T14:15:43+0100, onf wrote:
> > On Fri Dec 20, 2024 at 3:45 AM CET, G. Branden Robinson wrote:
> > > Yes. I think we could do more to encourage people to understand the
> > > availability of the grout format
Hi onf,
At 2024-12-20T14:15:43+0100, onf wrote:
> On Fri Dec 20, 2024 at 3:45 AM CET, G. Branden Robinson wrote:
> > Yes. I think we could do more to encourage people to understand the
> > availability of the grout format as a resource on more occasions, in
> > a similar way that Dave Kemper fina
Hi Branden,
On Fri Dec 20, 2024 at 3:45 AM CET, G. Branden Robinson wrote:
> At 2024-12-19T22:48:41+0100, onf wrote:
> > > The number of people who read GNU troff output ("grout"), whether
> > > with their eyeballs or with a program they've written, is *tiny*.
> >
> > If that's the case, I wonder
At 2024-12-19T22:48:41+0100, onf wrote:
> On Thu Dec 19, 2024 at 8:43 PM CET, G. Branden Robinson wrote:
> > At 2024-12-19T20:23:56+0100, onf wrote:
> > > Although looking up Unicode codepoint numbers is arguably better
> > > than seeing gibberish, neither is a particularly good form to work
> > >
Hi Branden,
On Thu Dec 19, 2024 at 8:43 PM CET, G. Branden Robinson wrote:
> At 2024-12-19T20:23:56+0100, onf wrote:
> > Although looking up Unicode codepoint numbers is arguably better
> > than seeing gibberish, neither is a particularly good form to work
> > with. Your reasoning sounds like "mak
On Thu Dec 19, 2024 at 7:15 PM CET, G. Branden Robinson wrote:
> At 2024-12-19T17:20:09+, Deri wrote:
> > I don't mind, I just thought you considered readability of the grout
> > file important [1],
>
> I do. ISO 646/ASCII is readable practically everywhere. There remain
> places where UTF-8,
At 2024-12-19T20:23:56+0100, onf wrote:
> On Thu Dec 19, 2024 at 7:15 PM CET, G. Branden Robinson wrote:
> > At 2024-12-19T17:20:09+, Deri wrote:
> > > I don't mind, I just thought you considered readability of the grout
> > > file important [1],
> >
> > I do. ISO 646/ASCII is readable practic
Hi Deri,
At 2024-12-19T17:20:09+, Deri wrote:
> On Thursday, 19 December 2024 00:34:49 GMT G. Branden Robinson wrote:
> > Is [UTF-8-encoded characters in grout] something you want? What
> > should the consequences of invalid or incomplete UTF-8 sequences be?
>
> I don't mind, I just thought y
11 matches
Mail list logo
