ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Floris van Manen <vm@klankschap.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: confusing columns balancing results
Date: Fri, 14 Jul 2017 18:03:09 +0200	[thread overview]
Message-ID: <EA9B8E2C-CA81-488F-900A-6A427C2D0C63@klankschap.nl> (raw)
In-Reply-To: <411ddb65-c395-ba5f-a760-e30886bdc6a7@rik.users.panix.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1540 bytes --]


> On 14 Jul 2017, at 17:28, Rik Kabel <context@rik.users.panix.com> wrote:
> 
> Henri’s example fails for me in the same way that Floris describes. However, when I remove either or both of the following lines from the first \setuplayout directive, all is well.
> header=0mm,
> footer=0mm,
> 
> In this example, the complete unnamed layout can simply be removed.
> 
> It is not clear why Floris has two layouts defined and active. One is stepping on the other. I do not know if the results of applying multiple layouts should be additive like this, or not, but I would think that they should not be.

but removing the

header=0mm,
footer=0mm,

will redefine the page surface.

What i tried was to specify a margin of 10mm around the text block which has 5 columns.
This works only if the column balance is set to no.
There is probably a good reason for, but i don’t understand it (yet)

What is the correct way to define it?


.F


\setupcolumns[
    n=5,
    distance=4mm,
    balance=yes,
    tolerance=tolerant]
\setupfootertexts[][]

\setuppagenumber[state=none]
\setuppagenumber[state=stop]
\definelayout[WithoutMarginnotes][
    location={duplex},
    grid=no,
    topspace=1cm,
    % height=19cm,
    height=fit,
    backspace=1cm,
    cutspace=0cm,
    leftmargin=0cm,
    leftmargindistance=0.4cm,
    width=fit,
    rightmargindistance=0cm,
    rightmargin=0cm,
    header=0mm,
    top=0mm,
    footer=0mm,
    bottom=0mm
    ]
 \setuplayout[WithoutMarginnotes]





[-- Attachment #1.1.2: Type: text/html, Size: 3124 bytes --]

[-- Attachment #1.2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]

[-- Attachment #2: Type: text/plain, Size: 492 bytes --]

___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2017-07-14 16:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8DC36222-459D-4562-9B89-8F9F079DFF6D@klankschap.nl>
2017-07-13 23:08 ` Floris van Manen
2017-07-14  0:05   ` Henri Menke
2017-07-14  7:12     ` Floris van Manen
2017-07-14 15:28     ` Rik Kabel
2017-07-14 16:03       ` Floris van Manen [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=EA9B8E2C-CA81-488F-900A-6A427C2D0C63@klankschap.nl \
    --to=vm@klankschap.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).