ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: bug? gap appears in columnset
Date: Thu, 19 Sep 2013 17:19:16 +0200	[thread overview]
Message-ID: <523B15F4.5080009@wxs.nl> (raw)
In-Reply-To: <523B096D.70801@sil.org>

On 9/19/2013 4:25 PM, Lars Huttar wrote:
> Hans wrote,
>> Columnsets are rather special and mostly meant for magazine like
>> documents, where content can span columns, images are explicitly placed
>> on the grid, etc. For that reason columnset soperate on a rather strict
>> grid that gets setup based in the lineheight and although content can be
>> larger, the grid dictates what happens. Balancing is semi automatic and
>> nearly always demands some tweaks.
>
> In our use of columnsets, we do have content that can span columns (but
> we keep it outside of columnsets). We also have images within columns
> that are placed in the flow of text via hangarounds. We manually tweak
> our column lengths on each page (e.g.
> \setupcolumnsetlines[columnset10][1][1][42]), in order to avoid the
> worst of the widows and orphans. As you say, balancing requires manual
> tweaks too, but it's not that big a burden, since we're already doing
> \setupcolumnsetlines for many pages.
>
>> Using columnsets for a large document that has to flow automatically is
>> therefore debatable. Regular multi columns or in mkiv mixed-columns are
>> a better choice then.
>
> We have tried to port our code to mkiv, but have so far found been
> unsuccessful. (But are trying again now, having found new success with
> TL2013 mkii.)
> Also, we've been unable to find any statement that mkiv is out of beta
> status. Moreover, much of the documentation still seems to be oriented
> toward mkii. So it's hard to justify much of a time investment in
> porting production work to mkiv yet. Can you comment on the official
> status of mkiv?

just as we had betas for mkii, we have betas for mkiv .. mkii is already 
frozen for years (apart from very few fixes)

i'm pretty sure that most context users use mkiv and here i only run 
mkii in old workflows that already have been running for years (and will 
continue to do so as long as no fundamental update is needed)

most mkii functionality is present in mkiv (of course some old font 
stuff is obsolete) although there are a few mechanism that due to 
extensions are controlled with different keys (mostly keys like 
'alternative')

unless impossible (or messy) i try to keep mkii command compatibility 
but mkiv has already many more commands and mechanisms than mkii, so 
most in manuals still applies

official status: use mkiv as that's where it all happens

> Regarding mixed-columns: I understand it's a rewrite of the old
> "columns" model. My impression is that "columns" didn't support manual
> tweaking of column lengths (like \setupcolumnsetlines). Does
> mixed-columns support such a thing? That would be a critical question
> for us, as it wouldn't be an option for us to spend time porting to mkiv
> and using mixed-columns, if it doesn't allow us to tweak the height of
> each column on each page.

i can probably add some height-per-column option but it also depends on 
what height is supposed to do but it's unlikely to happen the next few 
weeks

a  mkiv columnsets implementation .. well, it depends on time and 
motivation (most of such mechanisms i don't use myself so i need good 
reasons to spend time on them, unless i'm looking for a challenge on a 
rainy day)

but ... \column works quite ok in mixed columns

> Thanks again for your help and advice.

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2013-09-19 15:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13 20:07 Lars Huttar
2013-09-13 20:20 ` Lars Huttar
2013-09-16 18:29   ` Lars Huttar
2013-09-16 21:29     ` Lars Huttar
2013-09-16 22:32       ` Aditya Mahajan
2013-09-17 14:47       ` Hans Hagen
2013-09-17 15:02       ` Lars Huttar
2013-09-17 15:31         ` Hans Hagen
2013-09-17 18:57         ` Lars Huttar
2013-09-17 20:02           ` Hans Hagen
2013-09-18 21:47           ` Lars Huttar
2013-09-18 23:22             ` Hans Hagen
2013-09-19 14:25             ` Lars Huttar
2013-09-19 15:19               ` Hans Hagen [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=523B15F4.5080009@wxs.nl \
    --to=pragma@wxs.nl \
    --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).