From: "Santy, Michael" <Michael.Santy@dynetics.com>
To: <ntg-context@ntg.nl>
Subject: Re: natural table splitting problems
Date: Wed, 31 Oct 2007 07:21:14 -0500 [thread overview]
Message-ID: <6703815B292B664DBAEC55EE3192386A20BC6E@poseidon.in.dynetics.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1090 bytes --]
Hagen, Hans wrote:
> it's always a problem to determine what's left on a page
>
> \def\blah{The quick brown fox jumped over the lazy stupid dog.}
> \dorecurse{62}{\blah} \synchronizeoutput
>
> this will force the otr but is not always fails safe (i.e. vertical
> spacing may be messed)
>
> ... one of the reasons why we work on luatex -)
>
> Hans
Hans,
The "\synchronizeoutput" seemed to fix this trivial example, but it doesn't seem to fix other illustrations of this behavior. Is the "\synchronizeoutput" something that I should place at the end of every block of content (paras, sections, lists, figures, equations, etc.) in order to ensure that tables split properly. If not, is there a general workaround for this table issue that I can apply in the meantime while LuaTeX is still in development? I'm generating ConTeXt from XSL, so its very easy to make a system wide change of how the content is generated.
By the way, the LuaTeX on live.contextgarden.net seems to be broken ("FatalError: Your format does not match the base files!")
Cheers,
Mike
[-- Attachment #1.2: Type: text/html, Size: 1637 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2007-10-31 12:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 12:21 Santy, Michael [this message]
[not found] <mailman.3218.1193768985.2346.ntg-context@ntg.nl>
2007-10-30 19:26 ` Santy, Michael
2007-10-31 12:23 ` Peter Rolf
2007-10-31 13:31 ` Peter Rolf
2007-10-31 13:47 ` Santy, Michael
2007-10-31 16:04 ` Peter Rolf
2007-10-31 17:57 ` Santy, Michael
2007-10-31 18:34 ` Hans Hagen
2007-10-31 18:46 ` Peter Rolf
2007-10-31 16:34 ` Hans Hagen
[not found] <C34BC556.A391%mike.santy@dynetics.com>
[not found] ` <4726F9AB.5080002@gmx.net>
2007-10-30 12:16 ` Santy, Michael
2007-10-30 13:50 ` Peter Rolf
2007-10-30 19:42 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2007-10-29 13:09 Santy, Michael
2007-10-29 14:39 ` Peter Rolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6703815B292B664DBAEC55EE3192386A20BC6E@poseidon.in.dynetics.com \
--to=michael.santy@dynetics.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).