ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: itemize in two columns and pagebreaks
Date: Sat, 30 Jun 2012 07:05:36 +0200	[thread overview]
Message-ID: <2F67FC15-1B57-4D83-8BB4-79041A84FAD8@gmail.com> (raw)
In-Reply-To: <20120630065310.5330ae76@aga-netbook>

Hi,

The mechanisms of columns in itemize (which I think is the same as startcolumns) and in simplecolumns are indeed different, as Hans indicated once.
The issue you encountered is indeed a bug as you point out: once (a few months ago) I had an analogous problem and Wolfgang S. suggested me to use simplecolumns to avoid the strange page breaks.

Best regards: OK

On 30 juin 2012, at 06:53, Marcin Borkowski wrote:

> Dnia 2012-06-30, o godz. 05:05:31
> Otared Kavian <otared@gmail.com> napisał(a):
> 
>> Hi Marcin,
>> 
>> I tested your file and noticed the issue you are reporting. In your
>> case you can use \startsimplecolumns to get rid of the page break
>> (however there is a small problem with the distance between the text
>> and the items): 
> 
> I knew that - but as you probably have noticed, the columns done by
> \startsimplecolumns and by \startitemize[columns] do not align
> correctly.  So this is rather a workaround than a solution.  (Well,
> thanks anyway!)
> 
> Currently I changed the file a bit and the problem disappeared,
> but still I'd like to know what's going on, since this tends to happen
> from time to time.  (And this bug - because I guess it's a bug indeed -
> has been around for quite a few years: I noticed it for the first time
> something like 3 years ago...)
> 
> Best,
> 
> -- 
> 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  : http://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________

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

  reply	other threads:[~2012-06-30  5:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29 21:30 Marcin Borkowski
2012-06-29 22:16 ` Marcin Borkowski
2012-06-30  3:05   ` Otared Kavian
2012-06-30  4:53     ` Marcin Borkowski
2012-06-30  5:05       ` Otared Kavian [this message]
2012-06-30  9:47         ` Marcin Borkowski
2012-06-30 18:00 ` Wolfgang Schuster

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=2F67FC15-1B57-4D83-8BB4-79041A84FAD8@gmail.com \
    --to=otared@gmail.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).