From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug in latest beta?
Date: Mon, 01 Jun 2015 09:28:42 +0200 [thread overview]
Message-ID: <556C09AA.4010607@gmx.es> (raw)
In-Reply-To: <A49A1099-14E3-4627-8461-C9EFE487091B@gmail.com>
On 06/01/2015 08:45 AM, Otared Kavian wrote:
> Hi Pablo,
>
> Indeed the document I was talking about has been typeset with
> various versions of mkiv, but now I observe that sometimes the
> pagebreaks are made in a very strange way. Since I can’t make a
> minimal example, I put on the following link an excerpt of the PDF
> document where the bad pagebreaks can be seen:
>
> https://dl.dropboxusercontent.com/u/4316076/bad-pagebreak.pdf
>
> (Please see pages 19 and 32). It seems that this happens, sometimes,
> but as far as I can say from my experiments the bad pagebreak happens
> always before a « proclaim » which is defined as follows:
> [...]
> However it would be better to understand why the first definition
> does not work properly, in a rather random way.
Hi Otared,
having only three theorems my guess will be probably wrong, but I’ll try it.
The theorem that doesn’t cause a wrong pagebreak is preceeded by a
single line paragraph.
In order to confirm whether this is the pattern, I would remove some
words from the last paragraph on page 19, so that there has only one
line. And I would add some words to the pagraph before theorem 2.3.2 on
page 31, so this pargraph contains two lines.
Could you check this?
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2015-06-01 7:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 20:38 Pablo Rodriguez
2015-05-28 14:59 ` Otared Kavian
2015-05-31 11:34 ` Pablo Rodriguez
2015-05-28 17:10 ` Hans Hagen
2015-05-31 11:56 ` Pablo Rodriguez
2015-05-31 22:16 ` Hans Hagen
2015-06-01 6:45 ` Otared Kavian
2015-06-01 7:28 ` Pablo Rodriguez [this message]
2015-06-01 7:41 ` Otared Kavian
-- strict thread matches above, loose matches on Subject: below --
2017-11-01 13:18 Pablo Rodriguez
2017-11-01 15:50 ` Pablo Rodriguez
2016-09-05 8:39 Akira Kakuto
2016-09-05 14:33 ` Pablo Rodriguez
2016-09-05 14:44 ` luigi scarso
2016-09-05 15:32 ` Pablo Rodriguez
2016-09-05 5:59 Pablo Rodriguez
2016-09-05 6:36 ` josephcanedo
2016-09-05 15:10 ` Pablo Rodriguez
2016-09-06 4:43 ` Pablo Rodriguez
2015-05-14 20:46 Pablo Rodriguez
2015-05-15 5:07 ` Pablo Rodriguez
2014-12-10 18:51 Pablo Rodriguez
2014-12-10 19:14 ` Hans Hagen
2014-12-10 19:59 ` Pablo Rodriguez
2014-05-26 5:47 Pablo Rodriguez
2014-05-26 8:24 ` Hans Hagen
2014-05-26 15:44 ` Pablo Rodriguez
2014-03-18 17:30 Pablo Rodriguez
2014-03-18 17:39 ` Wolfgang Schuster
2014-03-18 17:52 ` Pablo Rodriguez
2008-11-10 9:55 Chen Shen
2008-11-10 11:59 ` Wolfgang Schuster
2008-11-10 12:37 ` Chen Shen
2008-11-10 15:25 ` Hans Hagen
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=556C09AA.4010607@gmx.es \
--to=oinos@gmx.es \
--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).