I'm following up the original query, but keeping the right
place in the thread!
A couple of years ago I posted where I had got to with
"A Guide to Typesetting Mathematics using GNU eqn".
It covered the basics then. I didn't take it much further
then, but Caleb Foong's query has prompted me to add
On Sat, Oct 26, 2013, James K. Lowden wrote:
> My basic approach is
>
> .mk
> .TS
> ... table 1 ...
> .TE
> .rt
> .DS 3i
> .TS
> ... table 2 ...
> .TE
>
> If the table is too long for the current page, and lands on the next
> one, that doesn't work well at all, so I have
>
> .KS
> .mk
> .TS
>
Follow-up: I have found the source of your pronblem (the one
to do with vertical displacement). When a table is oujtput using
the .TS macro, a "display drop" vertical spacing is added (and
the same happens for .EQ using eqn, and in other contexts).
You can get rid of this (in ms macros) by setting
On 26-Oct-2013 16:07:47 James K. Lowden wrote:
> I'm confused about how best to lay out tables side by side.
> I'm using the ms macro set. The main text stretches across
> the page (one column), but I want the tables adjacent so that
> they can be more easily compared.
>
> My basic approach is
I'm confused about how best to lay out tables side by side. I'm using
the ms macro set. The main text stretches across the page (one
column), but I want the tables adjacent so that they can be
more easily compared.
My basic approach is
.mk
.TS
... table 1 ...
.TE
.rt
.DS 3i
.TS
... table 2
> Today's obvious is tomorrow's obscure.
I agree. In particular because the code might be buggy,
and without an explanation of what the code is meant to do,
it's sometimes hard to figure out whether the code really
doesn't do what it's supposed to, or whether you're simply
not "getting" a partic
On 10/26/2013 08:17 AM, Tadziu Hoffmann wrote:
That sounds like a good comment to include in the code.
I remember reading somewhere that comments are unnecessary
because the code is "obvious":
www.usm.uni-muenchen.de/~hoffmann/roff/tmp/rpdup.pdf
(formatted using groff, so it's not comp
On Sat, Oct 26, 2013 at 04:17:22PM +0200, Tadziu Hoffmann wrote:
>
> > That sounds like a good comment to include in the code.
>
> I remember reading somewhere that comments are unnecessary
> because the code is "obvious":
>
> www.usm.uni-muenchen.de/~hoffmann/roff/tmp/rpdup.pdf
>
> (formatt
> That sounds like a good comment to include in the code.
I remember reading somewhere that comments are unnecessary
because the code is "obvious":
www.usm.uni-muenchen.de/~hoffmann/roff/tmp/rpdup.pdf
(formatted using groff, so it's not completely off-topic. :-)
On Sat, Oct 26, 2013 at 01:30:00PM +0200, Tadziu Hoffmann wrote:
> Here's a small hint on what the second version is intended
> to accomplish (see if you can recognize this in the code):
>
> If the equation does not overlap (with a safety margin of 1 em)
> with the text in the previous (partially-
> So this will be a nice bit of mental exercise.
:-)
Here's a small hint on what the second version is intended
to accomplish (see if you can recognize this in the code):
If the equation does not overlap (with a safety margin of 1 em)
with the text in the previous (partially-filled) line, then
11 matches
Mail list logo
