ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: sections
Date: Sun, 01 Jun 2014 19:54:26 +0200	[thread overview]
Message-ID: <538B68D2.5010405@gmx.es> (raw)
In-Reply-To: <538B13B9.1030700@wxs.nl>

Hi Hans,

many thanks for your explanation and sorry for the trouble.

I created the test case that only contains three issues related to page
breaks.

Many thanks for the new beta, I’m afraid I’m still experiencing issues.

    \showframe\showgrid
    \setupbodyfont[pagella,15pt]
    \starttext
    \dorecurse{100}{This is a sentence. }

    \startitemize
    \dorecurse{3}{\item This is an item.\par}
    \stopitemize
    \stoptext

Previous beta located two items on the first page. Latest beta locates
only one. But when items are higher than two, the first item disappears
from the first page in the second run.

And my first sample works fine with the new beta, but not with the real
book. I’ll try to get a new sample.

Many thanks for your help again,


Pablo.


On 06/01/2014 01:51 PM, Hans Hagen wrote:
> Hi Pablo,
> 
> The section breaks are a bit of a headache. In the old mechanism (also 
> mkii) we used penalties between different section levels (different 
> values so that there is some hierarchy).
> 
> In mkiv we have a weighted penalty/glue mechanism which has advantages 
> but can also create side effects. The method of a few weeks ago could 
> deal with
> 
> \section followed by 100 \subsections
> 
> i.e. no text between this. In a strict mechanism you end up with one 
> long page fur to all the penalties. So, there was some precaution for 
> this. However that didn't work well with content following sections that 
> prefers breaks (read: section head followed by e.g. itemize or tabulate).
> 
> So, the newer mechanism tries to analyze the page stream which 
> (currently) is somewhat tricky. That's why we need to iterate to an 
> acceptable solution.
> 
> Some of these mkiv mechanisms are already a bit old and could be done 
> better using some newer luatex trickery (but i need tome to do that).
> 
> It would be nice to have a large test case for this (sort of hard to 
> make one as some trial and error is involved). As you already have some, 
> best collect them for future reference.
> 
> A new beta ...
> 
> Hans


-- 
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
___________________________________________________________________________________


  parent reply	other threads:[~2014-06-01 17:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01 11:51 sections Hans Hagen
2014-06-01 15:40 ` sections Rik
2014-06-01 16:52   ` sections Hans Hagen
2014-06-01 17:54 ` Pablo Rodriguez [this message]
2014-06-01 18:18 ` sections Pablo Rodriguez
2014-06-01 21:15   ` sections 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=538B68D2.5010405@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).