Hi Deri, I've owed you a reply to a message since last month, but you went and made it easy for me to address one point so I'mma do that.
At 2025-01-21T16:31:17+0000, Deri wrote: > On Tuesday, 21 January 2025 05:59:41 GMT G. Branden Robinson wrote: > [...] > > The good news is, that's sorted out now, and comes with a "NEWS" > > item.[1] Deri was really helpful in sorting out the issues > > here. (As you're aware, there are knock-on issues not yet > > resolved to his satisfaction.[2]) > > > [Rearranged] > > > [2] https://lists.gnu.org/archive/html/groff/2024-12/msg00168.html > > I think this was in a discussion on what should be sent in the grout > file AFTER you make groff UTF-8 aware (without preconv), should grout > continue with the \[uXXXX] form, or pass the character data as UTF-8. Yes. > Given onf and Peter were generally supportive of seeing UTF-8 in > grout, and your defence of it was described as "making it perfect for > most people would make it horrible for a small minority, so let's > rather keep it bad for everyone", I rather think the consensus would > be to use UTF-8 in grout. Except I can't envision a way forward to achieving it without biting off way more trouble in the formatter than I want to. At least at this point. I feel pretty weak at the node production and printing logic. Give me another couple of years to increase my facility with it. But it _did_ occur to me that a "grout2utf8" Perl script is probably a really straightforward thing to do. We've all agreed that few people look at grout in the first place. If those few can be arsed to type "| grout2utf8", then they'll be happy, and I'll be happy I made them happy. > For people using an ascii locale it is unlikely their documents will > contain anything but ascii so would be perfectly readable in UTF-8 > grout. Yeah, but I won't have to go sticking my hand into unfamiliar places in the formatter, and we get to keep the output language ASCII-simple. > Other issues in the message have yet to be answered. Acknowledged. It's on my list. > Keith added a hyperlink macro to -mspdf:- > > .XR destination <post> <pre> > > Which I am supporting because it follows the style other ms macros, The argument order is silly, but deviating from established groff ms ordering would be sillier. > however I have simplified formatting of the hyperlink text, borrowing > Peter's (mom) idea of using "expandos" as part of the hyperlink text. Okay. I don't know what "expandos" means in this context; can you (or a mom(7) maven) point me to the part of Peter's docs that explains it? > > Let's see, is that everything? When I'm brain-dumping, sometimes > > it's hard to tell whether I'm finished. An affliction of age, > > maybe... > > Not the only age related issue with detecting if a flow has finished! You picked up what I'm puttin' down... Regards, Branden
signature.asc
Description: PGP signature
