ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marcin Borkowski <mbork@atos.wmid.amu.edu.pl>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: A problem with itemizations
Date: Mon, 27 Oct 2008 09:54:19 +0100	[thread overview]
Message-ID: <20081027085419.GB13542@atos.labs.wmid.amu.edu.pl> (raw)
In-Reply-To: <20081025134204.GC21389@atos.labs.wmid.amu.edu.pl>

Dnia Sat, Oct 25, 2008 at 03:42:04PM +0200, Marcin Borkowski napisa&#322;(a):
> Hi,
> 
> I have a problem with \startitemize ... \stopitemize.
> 
> Sometimes (I have no idea when, but this effect is fully repeatable!) I
> get a page break just before a \startitemize.  It is nested (second
> level) and follows one line of another item at the 1st level.  It seems
> that adding [intro] won't help.  The problem occurs with [columns,two];
> I don't know whether this has any influence - when I change the setup
> (in the preamble) the page breaks fall in different places, and all my
> 2nd level itemizations are 2nd level (and I have quite a lot of them).
> 
> Any ideas?  I know that the above is rather vague, but it's difficult to
> prepare a minimal example etc.

So, it took a while, but I got kind of a "minimal example":

\starttext
\startitemize[intro]
\dorecurse{12}{%
  \item \dorecurse{\recurselevel}{This is some intro. }Intro ends here.
  \startitemize[intro,columns,two]
  \dorecurse{4}{%
    \item \dorecurse{1}{This is a test. }End of the test.
  }%
  \stopitemize
}%
\stopitemize
\stoptext


(This shows the problem in the online ConTeXt.)

> Also, Hans, do I get it correctly that the itemization code will get
> rewritten in MkIV?  If yes, is there any chance of having unpacked
> itemizations in 2 and more columns?  And any chance of having an
> explicit column break (or a preference) in multicolumn itemizations?

And one more request (not really urgent, but would be nice): if there's
an \item followed directly by another \startitemize (possibly
two-column), a line break is enforced.  Does it have to be?

> 
> Thanks & greets
> 
> -- 
> Marcin Borkowski (http://mbork.pl)
> 
>  ####    ####    ####     _     __   __   __      _     __   __   __
> ##  ##  ##  ##  ##  ##   | \ | /  \ |  \ /  \    | \ | /  \ |  \ /  \  |
>  ####    ####    ####    |_/ | |  | |  | |  |    |_/ | |  | |  | |  |  |
> ##  ##  ##  ##  ##  ##   | \ | |--| |  | |--|    | \ | |--| |  | |--|  |
>  ####    ####    ####    |_/ | |  | |__/ |  | /  |_/ | |  | |__/ |  |  .
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

-- 
Marcin Borkowski (http://mbork.pl)

Stłumiony głos w końcu wypowie słowo prawdy - otworzą się usta!
Prawda - choćby zdeptana - zawsze pozostanie prawdą!
Żadna przemoc, chamstwo, kłamstwo nie uczynią z niej ofiary!
                        (Izaiash)
___________________________________________________________________________________
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
___________________________________________________________________________________


      reply	other threads:[~2008-10-27  8:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-25 13:42 Marcin Borkowski
2008-10-27  8:54 ` Marcin Borkowski [this message]

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=20081027085419.GB13542@atos.labs.wmid.amu.edu.pl \
    --to=mbork@atos.wmid.amu.edu.pl \
    --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).