ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Showing a cutting-frame
Date: Thu, 31 Jan 2013 17:21:59 +0100	[thread overview]
Message-ID: <A1CCB51C-0ABD-4E4E-B6BA-2C903C542506@gmail.com> (raw)
In-Reply-To: <510A36E7.2090308@mmnetz.de>


Am 31.01.2013 um 10:18 schrieb H. Özoguz <h.oezoguz@mmnetz.de>:

> Hi there,
> 
> to precize my question about the page-edges a few days ago, I know now what the perfect solution for me would be:
> 
> 1. Is it possible, that context prints on every page an frame/box, which has excactly X mm distance to each of the four borders, no matter how I change the papersize? (Too the the real layout after cutting.)

\setupbackgrounds[page][frame=on,frameoffset=10mm]

\setuppapersize[A4][A3]

\setuplayout[location=middle]

\starttext
\input knuth
\stoptext

> 2. And in addition to this, again my last question: Is there an command like "\addpapersize[x]" which increases the papersize x mm on all four directions of the page?
> (Useful, because with that I would not have to add always x mm cutting-space to topspace, bottomspace, cutspace and backspace manually, if I change the layout.)

Did you read my answer for your question in the other thread?

Wolfgang
___________________________________________________________________________________
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-01-31 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31  9:18 "H. Özoguz"
2013-01-31 16:21 ` Wolfgang Schuster [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=A1CCB51C-0ABD-4E4E-B6BA-2C903C542506@gmail.com \
    --to=wolfgang.schuster@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).