Hi Bertrand,
I'm running out of things I can think of to do before RC2.
Below, I'll excerpt the FOR-RELEASE file and annotate it.
* Increment the version number. groff requires an explicit three-part
version, major.minor.revision, due to the .Y register.
Can you do the "git tag 1.23.0.rc2"?
Hi John,
> > Or at best, gives it through some clunky ‘treat it as a string’
> > mechanism.
>
> How is that clunky? Text is text. It's opaque, honest, and
> universal. The foundation of the Unix Philosophy… you know this as
> well as I do. ;-)
It's an escape hatch to handle things not yet tho
Hi Ralph,
Or at best, gives it through some clunky ‘treat it as a string’ mechanism.
>
How is that clunky? Text is text. It's opaque, honest, and universal. The
foundation of the Unix Philosophy… you know this as well as I do. ;-)
One could look at shoehorning evermore complexity through to the
Hi John,
> > Support of modern font technologies and of course languages which
> > aren't left-to-right.
>
> Agreed. But for everything else you've mentioned: it's just a matter
> of writing another PDF postprocessor (or some other adapter for a
> particular format). Postprocessors are where the
Hi Ralph,
> Support of modern font technologies and of course languages which aren't
left-to-right.
Agreed. But for everything else you've mentioned: it's just a matter of
writing another PDF postprocessor (or some other adapter for a particular
format). Postprocessors are where the real beauty o
Hi Igno,
> We actually do have partial control over a significant portion of
> existing manual pages, by virtue of some relevant people participating
> in the list .
...
> Admittedly and for good reasons, huge numbers of individual, portable
> software packages also provide manual pages, and we ha
