Here's what I think is happening.
Each element of a row appears to be typeset on the same baseline.
It looks as if the baselines of adjacent rows are separated by the
maximum of the separations that would be needed in each column. This
assures that no entries collide with each other--the tightest
At 2023-06-28T22:05:06+1000, Damian McGuckin wrote:
> On Wed, 28 Jun 2023, G. Branden Robinson wrote:
>
> > Can I trouble you to file Savannah tickets for these issues?
>
> Sure. I will have to learn how first.
Shouldn't be too tortuous. :D
We have the following in INSTALL.extra:
If that do
On Wed, 28 Jun 2023, G. Branden Robinson wrote:
Can I trouble you to file Savannah tickets for these issues?
Sure. I will have to learn how first.
Thanks - Damian
Pacific Engineering Systems International . 20D Grose St, Glebe NSW 2037
Ph:+61-2-8571-0847 .. Fx:+61-2-9692-9623 | unsolicit
Hi Damian,
At 2023-06-28T14:49:56+1000, Damian McGuckin wrote:
> I know that the old troff on SUNs in the 1990s worked OK on these
> matrices
>
> OK, looks like the problem is GNU eqn.
Well, we'll have to do better!
Can I trouble you to file Savannah tickets for these issues? Your work
on a ne
On Tue, 27 Jun 2023, G. Branden Robinson wrote:
Heirloom keeps the good layouts of A and B, but also the bracket
alignment problem. It emits no diagnostics and lacks the horizontal
botch, but I find its rendering of vector C to be excessively crowded
vertically.
I know that the old troff on S
At 2023-06-28T12:21:47+1000, Damian McGuckin wrote:
> It has been said by someone more knowledgable than I that:
>
> A critical property of the 'matrix' construct is that elements in
> a row are aligned, which is not necessarily true in a sequence of
> piles.
That is consistentl
It has been said by someone more knowledgable than I that:
A critical property of the 'matrix' construct is that elements in
a row are aligned, which is not necessarily true in a sequence of
piles. The point is that vertical spacing in columns is adjusted
in conce
