From: Marcin Borkowski <mbork@atos.wmid.amu.edu.pl>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with itemization (again)
Date: Mon, 3 Nov 2008 01:19:58 +0100 [thread overview]
Message-ID: <20081103001958.GN31508@atos.labs.wmid.amu.edu.pl> (raw)
In-Reply-To: <20081102223946.GL31508@atos.labs.wmid.amu.edu.pl>
Dnia Sun, Nov 02, 2008 at 11:39:46PM +0100, Marcin Borkowski napisał(a):
> Hi,
>
> sorry to be a bit repetitive, but this still doesn't work as expected
> (in MkII, but see also below):
>
> \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
>
> (see page 2 and 3). I guess nothing wrt. itemizations changed in the
> new beta (I tested the above example in the online ConTeXt), so it's no
> surprise, but I still have no clue as to the reasons and any remedies.
> I use two-column itemizations *a lot*, so this is a serious problem for
> me... Any ideas how to prevent the unnecessary page break?
>
> PS. I have just noticed that this works correctly with luatex!!! And
> so do unpacked two-column itemizations!!! That's just great!!! So my
> question now becomes: does this mean that MkII is just obsolete for me
> and I should upgrade to MkIV?
>
> And two more things:
>
> 1. I have noticed that "unpacked" itemization in columns has the
> whitespace between items equal to one line. Is it possible to make it
> shorter, say half a line?
Answering myself: yes, ...[between={\blank[medium]}] works. Is this the
best way to do it?
> 2. I've also noticed that the second (last?) column of itemization seems
> *never* to be longer that the previous ones, which seems to be quite
> reasonable, but sometimes it would be better for it to be one line
> longer than two lines shorter. Is there a way of e.g. inserting a
> manual column-break within multi-column itemizations and/or letting the
> last column be longer?
And this remains unaswered - \column does not work...
> Sorry people for being such a nuisance, but - as I've said - I use
> itemizations a lot (mainly for different kinds of problem sets for
> my students or my wife's pupils;)) and these issues appear quite often.
> Also, I'd like to teach a bit of ConTeXt to my wife, who would like it
> to *simply work* (she's great, but no TeX hacker;)).
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
___________________________________________________________________________________
prev parent reply other threads:[~2008-11-03 0:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 22:39 Marcin Borkowski
2008-11-03 0:19 ` 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=20081103001958.GN31508@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).