On Thursday, 19 December 2024 00:34:49 GMT G. Branden Robinson wrote:
> For _input_ to GNU troff, maybe, if I can get it done. I'd love that.
>
> Except for one person (who doesn't contribute and no longer even
> participates on the mailing list), I don't know of anyone who's
> expressed interest
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
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
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
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,
Hi Alex,
At 2024-12-20T00:39:19+0100, Alejandro Colomar wrote:
> On Wed, Dec 18, 2024 at 08:00:53PM -0600, G. Branden Robinson wrote:
> > Synopsis:
> >
> > .QS [suppress-initial-word-hyphenation?]
> >Begin quotation. An opening quotation mark is formatted.
> >The line is not brok
Hi onf,
At 2024-12-20T02:21:00+0100, onf wrote:
> I assume the reason for using the strings `lq` and `rq` instead of
> characters of the same name is that the strings can be defined
> differently based on the current locale,
If so, that was pretty forward-looking for Berkeley in 1980.
> so that
Still current:
adjustment types: 0 1 3 5 (left both center right)
no-adjustment modes: 0 2 4
So enumeration '0' is the same for two different statuses but should be
different like
adjustment types: 0 3 5 7 (left both center right)
no-adjustment modes: 2 4 6
See more in bug #59795 (has
Hi Branden,
On Wed, Dec 18, 2024 at 08:00:53PM -0600, G. Branden Robinson wrote:
> Synopsis:
>
> .QS [suppress-initial-word-hyphenation?]
>Begin quotation. An opening quotation mark is formatted. The
>line is not broken. The optional argument is a Boolean value
>(“0” or
Hi Alejandro,
On Fri Dec 20, 2024 at 12:39 AM CET, Alejandro Colomar wrote:
> I prefer \[lq] and \[rq] over .QS and .QE. BTW, that's that '*' mean?
That's string interpolation syntax. From groff(7):
Strings
groff supports strings primarily for user convenience.
Conventionally, if one
Hi Bjarni,
Wrong enumeration? You are mistaken.
At 2024-12-19T23:04:23+, Bjarni Ingi Gislason wrote:
> Still current:
>
> adjustment types: 0 1 3 5 (left both center right)
> no-adjustment modes: 0 2 4
>
> So enumeration '0' is the same for two different statuses but should
> be di
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
> > >
12 matches
Mail list logo
