Thanks for the nominations, onf. At 2024-11-14T21:15:32+0100, onf wrote: > eqn > --- > > * The "gifont" primitive replaces "gfont" as the means of configuring > the global italic face in preprocessed equations. "gfont" remains > recognized as a synonym for backward compatibility. The new name is > intended to ease acquisition of the eqn language in light of GNU > eqn's thirty-year-old extensions "gbfont" and "grfont". > > A breaking change that should definitely be included.
Breaking? I hope not! The item does say: >> "gfont" remains recognized as a synonym for backward compatibility. There _are_ backward-incompatible changes in groff 1.24.0--which I generally float to the top of the relevant section of the "NEWS" file--but this is not one of them. > * New parameters tunable with the GNU eqn "set" primitive, "half_space" > and "full_space", [...] > > Seems like a nice addition to me, but might not interest others. The point of the survey is to measure individual contributors' and users' assessments of noteworthiness, and take the union of expressed preferences. I suggest not worrying about the opinions of others in this context. If a change is important to you, I want to hear about it. Should the "highlights" part of the announcement grow too long, only then will painful editorial culling be necessary. I'll then either take up the Maintainer's Burden and do it myself, or submit the union of nominated items to the list for an approval voting process.[1] > I always considered the fact .ps didn't accept the p unit weird. There is lingering terminological confusion in our documentation over points versus scaled points, and it itches me worse the better I understand the formatter. It's so prurient that I'm considering another terminological reform: scaled points -> subdivided points "p" is points, "s" is subdivided points. Whether such a change takes place for 1.24 depends on how much time I have to kill waiting on RC feedback. In the short run, the remaining RC tickets will keep me plenty busy. > * GNU troff now performs some limited processing/transformation of > the argument to the `\X` escape sequence and its counterpart > `device` request, to address the requirement that some documents > have to pass metadata that must encode non-ASCII characters in > device extension commands. (For example, a document author may > desire a document's section headings containing non-ASCII code > points to appear correctly in PDF bookmarks. Further, GNU troff > encodes its output page description language only in ASCII.) This > change is expected to be of significance mainly to developers of > output drivers for groff; groff_diff(7) describes the > transformations. If you have been using `\X` or `.device` to pass > ASCII data to the output driver as a device extension command and > require that it remain precisely as-is, use the `\!` escape > sequence or `output` request, and prefix your data with "x X ", the > device-independent troff means of expressing a device extension > command (see groff_out(5)). > > TL;DR PDF bookmarks now support Unicode, which is nice. An excellent summary. One of my objectives for the highlights is to boil each item down to, ideally, one line of text in the message. Here's the 1.23.0 announcement, for example. https://lists.gnu.org/archive/html/info-gnu/2023-07/msg00001.html We had 8 highlights, one occupying 3 lines, two 2 lines, and the rest one line each. Regards, Branden [1] https://en.wikipedia.org/wiki/Approval_voting
signature.asc
Description: PGP signature
